From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Orzel, Michal" <michal.orzel@amd.com>
Cc: xen-devel@lists.xenproject.org,
Anthony PERARD <anthony.perard@vates.tech>
Subject: Re: [PATCH] tests/vpci: Use $(CC) instead of $(HOSTCC)
Date: Tue, 3 Jun 2025 12:30:42 +0200 [thread overview]
Message-ID: <aD7O0nsfuKbKwlnD@macbook.local> (raw)
In-Reply-To: <6438a00b-a0fe-419d-b57e-5e1af48d43ce@amd.com>
On Tue, Jun 03, 2025 at 08:52:38AM +0200, Orzel, Michal wrote:
>
>
> On 03/06/2025 08:46, Roger Pau Monné wrote:
> > On Mon, Jun 02, 2025 at 05:09:29PM +0200, Michal Orzel wrote:
> >> These tests are supposed to run on target. HOSTCC can be different than
> >> CC (when cross-compiling). At the moment, tests installation would put
> >> a binary of a wrong format in the destdir.
> >>
> >> Fixes: e90580f25bd7 ("vpci: introduce basic handlers to trap accesses to the PCI config space")
Hm, it's unclear to me whether this is the correct fixes tag.
Previous to:
96a587a05736 tools/tests: Add install target for vPCI
The test was not installed on the host, and hence didn't need to use
CC instead of HOSTCC (or at least that's my understating).
> >> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
> >> ---
> >> tools/tests/vpci/Makefile | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/tools/tests/vpci/Makefile b/tools/tests/vpci/Makefile
> >> index 9450f7593a41..1101a669e118 100644
> >> --- a/tools/tests/vpci/Makefile
> >> +++ b/tools/tests/vpci/Makefile
> >> @@ -11,7 +11,7 @@ run: $(TARGET)
> >> ./$(TARGET)
> >>
> >> $(TARGET): vpci.c vpci.h list.h main.c emul.h
> >> - $(HOSTCC) $(CFLAGS_xeninclude) -g -o $@ vpci.c main.c
> >> + $(CC) $(CFLAGS_xeninclude) -g -o $@ vpci.c main.c
> >
> > This was already posted in:
> >
> > https://lore.kernel.org/xen-devel/20230313121226.86557-1-roger.pau@citrix.com/
> >
> > And got no feedback.
> >
> > I'm happy for your change to go in, but you might also consider
> > picking up the run target adjustment part of that previous patch.
> You're the maintainer of this file. You should tell me what I need to do
> unless you want to wait for Anthony feedback.
I would also add the chunk to adjust the run target if you use CC
instead of HOSTCC.
Thanks, Roger.
next prev parent reply other threads:[~2025-06-03 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 15:09 [PATCH] tests/vpci: Use $(CC) instead of $(HOSTCC) Michal Orzel
2025-06-02 15:36 ` Andrew Cooper
2025-06-02 15:40 ` Orzel, Michal
2025-06-02 15:50 ` Jan Beulich
2025-06-02 16:00 ` Andrew Cooper
2025-06-03 6:41 ` Orzel, Michal
2025-06-03 6:46 ` Roger Pau Monné
2025-06-03 6:52 ` Orzel, Michal
2025-06-03 10:30 ` Roger Pau Monné [this message]
2025-06-03 11:23 ` Orzel, Michal
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=aD7O0nsfuKbKwlnD@macbook.local \
--to=roger.pau@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=michal.orzel@amd.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.