From: Ammar Faizi <[email protected]>
To: Andy Lutomirski <[email protected]>,
Thomas Gleixner <[email protected]>,
Ingo Molnar <[email protected]>, Borislav Petkov <[email protected]>,
Dave Hansen <[email protected]>,
"H. Peter Anvin" <[email protected]>
Cc: x86-ml <[email protected]>, GNU/Weeb Mailing List <[email protected]>,
lkml <[email protected]>,
Ammar Faizi <[email protected]>
Subject: [PATCH v1 0/3] x86-64 entry documentation and clean up
Date: Sat, 8 Jan 2022 06:52:07 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
There are 3 patches in this series.
1) Trivial clean up in entry_64.S.
2) Add comment about registers on exit in entry_64.S.
3) Add documentation about registers on entry and exit.
(2) and (3) are based on the discussion we had at:
https://lore.kernel.org/lkml/[email protected]/
This series is based on commit:
24556728c305886b8bb05bf2ac7e20cf7db3e314 ("Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm")
Thanks!
Signed-off-by: Ammar Faizi <[email protected]>
---
Ammar Faizi (3):
x86/entry/64: Clean up spaces after instruction
x86/entry/64: Add info about registers on exit
Documentation: x86-64: Document registers on entry and exit
Documentation/x86/entry_64.rst | 47 ++++++++++++++++++++++++++++++++++
arch/x86/entry/entry_64.S | 27 ++++++++++++++-----
2 files changed, 67 insertions(+), 7 deletions(-)
base-commit: 24556728c305886b8bb05bf2ac7e20cf7db3e314
--
Ammar Faizi
--
GWML mailing list
[email protected]
https://gwml.gnuweeb.org/listinfo/gwml
next reply other threads:[~2022-01-07 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 23:52 Ammar Faizi [this message]
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
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] \
/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