From: Borislav Petkov <[email protected]>
To: Andy Lutomirski <[email protected]>
Cc: Jonathan Corbet <[email protected]>, "H.J. Lu" <[email protected]>,
x86-ml <[email protected]>, GNU/Weeb Mailing List <[email protected]>,
Dave Hansen <[email protected]>,
lkml <[email protected]>,
Ingo Molnar <[email protected]>, "H. Peter Anvin" <[email protected]>,
Thomas Gleixner <[email protected]>, Willy Tarreau <[email protected]>,
Michael Matz <[email protected]>
Subject: Re: [PATCH v1 3/3] Documentation: x86-64: Document registers on entry and exit
Date: Fri, 21 Jan 2022 14:32:24 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, Jan 07, 2022 at 04:02:27PM -0800, Andy Lutomirski wrote:
> This is SYSCALL64 registers on entry, not general registers on entry. Also,
> this has little to do with the entry logic, so it probably doesn't belong in
> this file.
Right, except that syscall is also a kernel entry point so it kinda
belongs in a documentation file called "entry". :)
Srsly, I'd really like to keep the note about which registers glibc
considers clobbered and which not, documented somewhere as that is
practically an ABI which is not (yet) in the psABI doc.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
--
GWML mailing list
[email protected]
https://gwml.gnuweeb.org/listinfo/gwml
prev parent reply other threads:[~2022-01-21 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 23:52 [PATCH v1 0/3] x86-64 entry documentation and clean up Ammar Faizi
2022-01-07 23:52 ` [PATCH v1 1/3] x86/entry/64: Clean up spaces after the instruction Ammar Faizi
2022-01-07 23:52 ` [PATCH v1 2/3] x86/entry/64: Add info about registers on exit Ammar Faizi
2022-01-08 0:03 ` Andy Lutomirski
2022-01-08 0:34 ` Ammar Faizi
2022-01-07 23:52 ` [PATCH v1 3/3] Documentation: x86-64: Document registers on entry and exit Ammar Faizi
2022-01-08 0:02 ` Andy Lutomirski
2022-01-08 0:38 ` Ammar Faizi
2022-01-21 13:32 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox