All of lore.kernel.org
 help / color / mirror / Atom feed
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] x86/altcall: further refine clang workaround
Date: Thu, 25 Jul 2024 16:54:54 +0200	[thread overview]
Message-ID: <ZqJnPvL1ilDDzM9V@macbook> (raw)
In-Reply-To: <9ecd3a39-55bf-4a49-9f45-1e0abfad353a@suse.com>

On Thu, Jul 25, 2024 at 03:18:29PM +0200, Jan Beulich wrote:
> On 25.07.2024 12:56, Roger Pau Monne wrote:
> > --- a/xen/arch/x86/include/asm/alternative.h
> > +++ b/xen/arch/x86/include/asm/alternative.h
> > @@ -184,11 +184,11 @@ extern void alternative_branches(void);
> >   * 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;                                                \
> > +    register struct {                                                   \
> > +        typeof(arg) e;                                                  \
> > +        char pad[sizeof(void *) - sizeof(arg)];                         \
> 
> One thing that occurred to me only after our discussion, and I then forgot
> to mention this before you would send a patch: What if sizeof(void *) ==
> sizeof(arg)? Zero-sized arrays are explicitly something we're trying to
> get rid of.

I wondered about this, but I though it was only [] that we were trying
to get rid of, not [0].

> I was wondering whether we could get away resorting to bitfields, as those
> are well-defined when having a width of zero:
> 
>     register struct {                                                   \
>         typeof(arg) e;                                                  \
>         unsigned long pad:(sizeof(void *) - sizeof(arg)) * 8;           \
>     } ...
> 
> Yet when the width is zero, the field may not have name, whereas when the
> field uniformly doesn't have a name, Clang would, like also for
> 
>     register struct {                                                   \
>         typeof(arg) e;                                                  \
>         unsigned long :0;                                               \
>     } ...
> 
> regards that space as not needing any (re)init. Bottom line: For the
> moment I'm out of ideas.

Hm, I see.  I don't have any good ideas right now either.  Will put it
on the back burner and pick up later, already too much on my plate
right now to be playing clang games.  Thanks for your input.

Roger.


  reply	other threads:[~2024-07-25 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 10:56 [PATCH] x86/altcall: further refine clang workaround Roger Pau Monne
2024-07-25 13:18 ` Jan Beulich
2024-07-25 14:54   ` Roger Pau Monné [this message]
2024-07-25 15:00     ` Jan Beulich
2024-07-26  7:31       ` Roger Pau Monné
2024-07-26  7:36         ` Jan Beulich
2024-07-26  7:52           ` Roger Pau Monné
2024-07-26  8:05             ` Jan Beulich
2024-07-26 14:17               ` Alejandro Vallejo
2024-07-26 14:25                 ` Alejandro Vallejo
2024-07-26 15:18                   ` Roger Pau Monné
2024-07-26 16:25                     ` Alejandro Vallejo
2024-07-26 16:38                       ` Alejandro Vallejo
2024-07-29  8:14                         ` Roger Pau Monné

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=ZqJnPvL1ilDDzM9V@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.