From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>,
Anthony PERARD <anthony.perard@vates.tech>
Subject: Re: [PATCH v2] x86/boot: Fix include paths for 32bit objects
Date: Tue, 3 Sep 2024 14:43:29 +0200 [thread overview]
Message-ID: <ZtcEcT7E95sOi276@macbook.local> (raw)
In-Reply-To: <20240903115334.3526368-1-andrew.cooper3@citrix.com>
On Tue, Sep 03, 2024 at 12:53:34PM +0100, Andrew Cooper wrote:
> Most of Xen is build using -nostdinc and a fully specified include path.
> However, the makefile line:
>
> $(head-bin-objs): XEN_CFLAGS := $(CFLAGS_x86_32) -fpic
>
> discards XEN_CFLAGS and replaces them with CFLAGS_x86_32.
>
> Reinstate -nostdinc, and copy all -I (and -Wa,-I) arguments from XEN_CFLAGS.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
I wouldn't mind if you also open-coded the config.h -include addition
to CFLAGS_x86_32, regardless:
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
I do wonder however whether the explicit assembler includes parameters
(-Wa,-I) are actually required, seeing as we only provide include/ to
the assembler, but not the arch-specific include paths.
This is from XSA-254, which used the '.include' asm directive, but
that was ultimately removed by:
762c3890c89f x86: fold indirect_thunk_asm.h into asm-defns.h
So maybe the -Wa,-I is no longer needed?
Thanks, Roger.
next prev parent reply other threads:[~2024-09-03 12:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 10:49 [PATCH] x86/boot: Reinstate -nostdinc for CFLAGS_x86_32 Andrew Cooper
2024-09-03 10:54 ` Roger Pau Monné
2024-09-03 11:08 ` Andrew Cooper
2024-09-03 11:16 ` Andrew Cooper
2024-09-03 12:16 ` Roger Pau Monné
2024-09-03 11:20 ` Anthony PERARD
2024-09-03 11:51 ` Andrew Cooper
2024-09-03 12:19 ` Roger Pau Monné
2024-09-03 11:53 ` [PATCH v2] x86/boot: Fix include paths for 32bit objects Andrew Cooper
2024-09-03 12:43 ` Roger Pau Monné [this message]
2024-09-03 13:01 ` Andrew Cooper
2024-09-03 13:08 ` Roger Pau Monné
2024-09-03 14:32 ` Jan Beulich
2024-09-03 14:33 ` Andrew Cooper
2024-09-03 14:50 ` Andrew Cooper
2024-09-04 6:54 ` Jan Beulich
2024-09-04 8:05 ` 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=ZtcEcT7E95sOi276@macbook.local \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--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.