-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
完善Tty的RawMode #577
完善Tty的RawMode #577
Conversation
PR Description updated to latest commit (64e7639) |
PR Analysis
PR Feedback
✨ Usage guide:Overview:
With a configuration file, use the following template:
See the review usage page for a comprehensive guide on using this tool. |
syscall64那里的汇编需要改一下。目前这种写法导致系统调用过程中,中断是禁止的。 |
kernel/src/arch/x86_64/asm/entry.S
Outdated
@@ -376,6 +377,8 @@ ENTRY(syscall_64) | |||
|
|||
// 将原本要返回的栈帧的栈指针传入do_signal的第一个参数 | |||
movq %rsp, %rdi | |||
|
|||
sti |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -46,7 +46,7 @@ impl AppBackend { | |||
}) | |||
}; | |||
|
|||
*r.main_thread.write().unwrap() = Some(main_thread); | |||
*r.main_thread.write_irqsave().unwrap() = Some(main_thread); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这里改错了,它不应该有write_irqsave。因为这个应用程序是跑在Linux的
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
怪不得报黄
User description
Type
Bug fix, Enhancement
Description
此PR包含两个主要更改:
termios
模块中,修正了InputMode
和OutputMode
中的标志位定义,以及ControlMode
和LocalMode
中的波特率和字符大小掩码定义,以解决潜在的错误。vesafb
模块中,对fb_copyarea
函数进行了优化,以避免无效的内存访问,并改进了区域拷贝的逻辑,以提高效率和准确性。Changes walkthrough
termios.rs
Termios模块的标志位和波特率定义修正
kernel/src/driver/tty/termios.rs
InputMode
和OutputMode
中的标志位定义,以修正错误。ControlMode
和LocalMode
中的波特率和字符大小掩码定义。vesafb.rs
FBDev VesaFb的fb_copyarea函数优化
kernel/src/driver/video/fbdev/vesafb.rs
fb_copyarea
函数的实现,以避免无效的内存访问。✨ Usage guide:
Overview:
The
describe
tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.When commenting, to edit configurations related to the describe tool (
pr_description
section), use the following template:With a configuration file, use the following template:
Enabling\disabling automation
meaning the
describe
tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.the tool will replace every marker of the form
pr_agent:marker_name
in the PR description with the relevant content, wheremarker_name
is one of the following:type
: the PR type.summary
: the PR summary.walkthrough
: the PR walkthrough.Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.
Custom labels
The default labels of the
describe
tool are quite generic: [Bug fix
,Tests
,Enhancement
,Documentation
,Other
].If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:
Main topic:performance
- pr_agent:The main topic of this PR is performanceNew endpoint
- pr_agent:A new endpoint was added in this PRSQL query
- pr_agent:A new SQL query was added in this PRDockerfile changes
- pr_agent:The PR contains changes in the DockerfileThe list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.
Inline File Walkthrough 💎
For enhanced user experience, the
describe
tool can add file summaries directly to the "Files changed" tab in the PR page.This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).
To enable inline file summary, set
pr_description.inline_file_summary
in the configuration file, possible values are:'table'
: File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.true
: A collapsable file comment with changes title and a changes summary for each file in the PR.false
(default): File changes walkthrough will be added only to the "Conversation" tab.Utilizing extra instructions
The
describe
tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.
More PR-Agent commands
See the describe usage page for a comprehensive guide on using this tool.