From: Jane Malalane <jane.malalane@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Jane Malalane <jane.malalane@citrix.com>
Subject: [PATCH 0/4] xen/x86: import linkage.h and clean up x86/kexec.S and x86/entry.S
Date: Thu, 4 Aug 2022 16:04:20 +0100 [thread overview]
Message-ID: <20220804150424.17584-1-jane.malalane@citrix.com> (raw)
Jane Malalane (4):
x86/kexec: Add the '.L_' prefix to is_* and call_* labels
xen: Port linkage.h from kernel code
x86/entry: move .init.text section higher up in the code for
readability
x86: Use linkage.h helpers to add tags to symbols
xen/arch/x86/x86_64/entry.S | 124 +++++++++++-------
xen/arch/x86/x86_64/kexec_reloc.S | 85 ++++++-------
xen/include/xen/linkage.h | 260 ++++++++++++++++++++++++++++++++++++++
3 files changed, 376 insertions(+), 93 deletions(-)
create mode 100644 xen/include/xen/linkage.h
--
2.11.0
next reply other threads:[~2022-08-04 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 15:04 Jane Malalane [this message]
2022-08-04 15:04 ` [PATCH 1/4] x86/kexec: Add the '.L_' prefix to is_* and call_* labels Jane Malalane
2022-08-05 6:26 ` Jan Beulich
2022-08-04 15:04 ` [PATCH 2/4] xen: Port linkage.h from kernel code Jane Malalane
2022-08-05 9:24 ` Jan Beulich
2022-08-16 10:16 ` Jane Malalane
2022-08-16 13:06 ` Jan Beulich
2022-08-17 8:56 ` Jane Malalane
2022-08-17 10:24 ` Jan Beulich
2022-08-04 15:04 ` [PATCH 3/4] x86/entry: move .init.text section higher up in the code for readability Jane Malalane
2022-08-04 19:36 ` Andrew Cooper
2022-08-05 9:29 ` Jan Beulich
2022-08-04 15:04 ` [RFC PATCH 4/4] x86: Use linkage.h helpers to add tags to symbols Jane Malalane
2022-08-04 19:46 ` Andrew Cooper
2022-08-05 9:40 ` Jan Beulich
2022-08-04 20:02 ` [PATCH 0/4] xen/x86: import linkage.h and clean up x86/kexec.S and x86/entry.S Andrew Cooper
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 \
--in-reply-to=20220804150424.17584-1-jane.malalane@citrix.com \
--to=jane.malalane@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.