From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Alejandro Vallejo <alejandro.vallejo@cloud.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] x86/altcall: further refine clang workaround
Date: Mon, 29 Jul 2024 14:47:59 +0200 [thread overview]
Message-ID: <ZqePfxLIrTjqdxWp@macbook> (raw)
In-Reply-To: <2a6efb82-bde4-490b-9c72-413009e756bd@suse.com>
On Mon, Jul 29, 2024 at 02:41:23PM +0200, Jan Beulich wrote:
> On 29.07.2024 14:00, Roger Pau Monné wrote:
> > On Mon, Jul 29, 2024 at 12:47:09PM +0200, Jan Beulich wrote:
> >> On 29.07.2024 12:30, Roger Pau Monne wrote:
> >>> --- a/xen/arch/x86/include/asm/alternative.h
> >>> +++ b/xen/arch/x86/include/asm/alternative.h
> >>> @@ -183,13 +183,13 @@ extern void alternative_branches(void);
> >>> * https://github.com/llvm/llvm-project/issues/12579
> >>> * https://github.com/llvm/llvm-project/issues/82598
> >>> */
> >>> -#define ALT_CALL_ARG(arg, n) \
> >>> - register union { \
> >>> - typeof(arg) e[sizeof(long) / sizeof(arg)]; \
> >>> - unsigned long r; \
> >>> - } a ## n ## _ asm ( ALT_CALL_arg ## n ) = { \
> >>> - .e[0] = ({ BUILD_BUG_ON(sizeof(arg) > sizeof(void *)); (arg); })\
> >>> - }
> >>> +#define ALT_CALL_ARG(arg, n) \
> >>> + register unsigned long a ## n ## _ asm ( ALT_CALL_arg ## n ) = ({ \
> >>> + unsigned long tmp = 0; \
> >>> + *(typeof(arg) *)&tmp = (arg); \
> >>> + BUILD_BUG_ON(sizeof(arg) > sizeof(void *)); \
> >>
> >> With this, even more so than before, I think the type of tmp would better
> >> be void * (or the BUILD_BUG_ON() be made use unsigned long, yet I consider
> >> that less desirable).
> >
> > Won't using void * be uglier, as we then need to cast the last tmp
> > statement to unsigned long?
>
> Only if we stick to using unsigned long for a ## n ## _. Afaics there's
> nothing wrong with making that void *, too.
Right, but then for consistency I would also like to make r{10,11}_
void *, and ALT_CALL_NO_ARG(), which might be too much.
My preference is likely to keep it at unsigned long, and adjust the
BUILD_BUG_ON(), unless you have a strong opinion to change it to void
* (and possibly the rest of the register variables).
Thanks, Roger.
next prev parent reply other threads:[~2024-07-29 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 10:30 [PATCH v2] x86/altcall: further refine clang workaround Roger Pau Monne
2024-07-29 10:47 ` Jan Beulich
2024-07-29 11:12 ` Alejandro Vallejo
2024-07-29 12:00 ` Roger Pau Monné
2024-07-29 12:41 ` Jan Beulich
2024-07-29 12:47 ` Roger Pau Monné [this message]
2024-07-29 13:03 ` Jan Beulich
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=ZqePfxLIrTjqdxWp@macbook \
--to=roger.pau@citrix.com \
--cc=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.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.