From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH 0/3] x86/asm: macro improvements in <asm/asm.h>
Date: Mon, 10 May 2021 02:09:37 -0700 [thread overview]
Message-ID: <20210510090940.924953-1-hpa@zytor.com> (raw)
From: "H. Peter Anvin (Intel)" <hpa@zytor.com>
This patchset adds the following improvements to <asm/asm.h>:
1. Makes the __ASM_FORM() macros accept arguments with commas. This allows
the __ASM_FORM() macros to be used directly in header files for
macros that can be used from either C or assembly, even for
instructions that have multiple operands.
2. Add an _ASM_BYTES() macro for the delicate job of hand-crafting
instructions out of bytes.
3. Replace the _ASM_MK_NOPS() macro in <asm/nops.h> with _ASM_BYTES().
The change to the tools/ directory is mainly because <asm/nops.h> now
depends on <asm/asm.h>.
---
arch/x86/include/asm/asm.h | 23 ++---
arch/x86/include/asm/nops.h | 24 ++---
tools/arch/x86/include/asm/asm.h | 189 ++++++++++++++++++++++++++++++++++++++
tools/arch/x86/include/asm/nops.h | 24 ++---
4 files changed, 221 insertions(+), 39 deletions(-)
next reply other threads:[~2021-05-10 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 9:09 H. Peter Anvin [this message]
2021-05-10 9:09 ` [PATCH 1/3] x86/asm: have the __ASM_FORM macros handle commas in arguments H. Peter Anvin
2021-05-10 10:59 ` [tip: x86/asm] x86/asm: Have " tip-bot2 for H. Peter Anvin (Intel)
2021-05-10 9:09 ` [PATCH 2/3] x86/asm: add _ASM_BYTES() macro for a .byte ... opcode sequence H. Peter Anvin
2021-05-10 10:59 ` [tip: x86/asm] x86/asm: Add " tip-bot2 for H. Peter Anvin (Intel)
2021-05-10 9:09 ` [PATCH 3/3] x86/asm: use _ASM_BYTES() in <asm/nops.h> H. Peter Anvin
2021-05-10 10:59 ` [tip: x86/asm] x86/asm: Use " tip-bot2 for H. Peter Anvin (Intel)
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=20210510090940.924953-1-hpa@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).