From: Wei Liu <wei.liu@kernel.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Wei Liu <wei.liu@kernel.org>,
qemu-devel@nongnu.org,
Pierrick Bouvier <pierrick.bouvier@linaro.org>
Subject: Re: [PULL 05/22] target/i386/hvf: Include missing 'exec/target_page.h' header
Date: Thu, 8 May 2025 01:09:24 +0000 [thread overview]
Message-ID: <aBwERHkcHPymjbk8@liuwe-devbox-ubuntu-v2.tail21d00.ts.net> (raw)
In-Reply-To: <36eee8b9-2ffe-461f-a1c6-2e19ad623a10@linaro.org>
On Wed, May 07, 2025 at 01:20:49PM +0200, Philippe Mathieu-Daudé wrote:
> Hi Wei,
>
> On 7/5/25 08:35, Wei Liu wrote:
> > On Tue, May 06, 2025 at 04:34:54PM +0200, Philippe Mathieu-Daudé wrote:
> > > Include "exec/target_page.h" to be able to compile HVF on x86_64:
> > >
> > > ../target/i386/hvf/hvf.c:139:49: error: use of undeclared identifier 'TARGET_PAGE_SIZE'
> > > uint64_t dirty_page_start = gpa & ~(TARGET_PAGE_SIZE - 1u);
> > > ^
> > > ../target/i386/hvf/hvf.c:141:45: error: use of undeclared identifier 'TARGET_PAGE_SIZE'
> > > hv_vm_protect(dirty_page_start, TARGET_PAGE_SIZE,
> > >
> > > Fixes: 9c2ff9cdc9b ("exec/cpu-all: remove exec/target_page include")
> > > Reported-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> > > Reported-by: Wei Liu <wei.liu@kernel.org>
> > > Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> > > Message-Id: <20250425174310.70890-1-philmd@linaro.org>
> > > Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> >
> > FYI Paolo merged a patch from me that does the same thing. My patch is
> > already in the master branch.
>
> Paolo said he'd replace your patch by this older one which mentions
> the problematic commit, which is why I didn't notice your patch,
> I was expecting this one to disappear on rebase. I don't plan to
> repost this PR except if there is a serious problem with it. In
> this case, we can still revert if we are picky. Duplicated includes
> aren't a problem, missing ones are.
>
Sure.
> BTW since you are testing / using HVF on x86, do you know if your
> employer could help extending our CI infrastructure coverage for
> your use cases?
>
No, we don't have a use case for HVF. I only tested it because I wanted
to refactor the instruction emulator out of the HVF code base.
Thanks,
Wei.
> Regards,
>
> Phil.
next prev parent reply other threads:[~2025-05-08 1:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 14:34 [PULL 00/22] Misc HW patches for 2025-05-06 Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 01/22] bsd-user: add option to enable plugins Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 02/22] qom: Factor qom_resolve_path() out Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 03/22] qom/object: Fix typo in comment Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 04/22] target/migration: Inline VMSTATE_CPU() Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 05/22] target/i386/hvf: Include missing 'exec/target_page.h' header Philippe Mathieu-Daudé
2025-05-07 6:35 ` Wei Liu
2025-05-07 11:20 ` Philippe Mathieu-Daudé
2025-05-08 1:09 ` Wei Liu [this message]
2025-05-06 14:34 ` [PULL 06/22] system/hvf: Avoid including 'cpu.h' Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 07/22] system/hvf: Expose hvf_enabled() to common code Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 08/22] hw/hyperv/hv-balloon-stub: common compilation unit Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 09/22] hw/hyperv/hyperv.h: header cleanup Philippe Mathieu-Daudé
2025-05-06 14:34 ` [PULL 10/22] hw/hyperv/vmbus: common compilation unit Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 11/22] hw/hyperv/syndbg: " Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 12/22] hw/hyperv/balloon: common balloon compilation units Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 13/22] hw/hyperv/hyperv_testdev: common compilation unit Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 14/22] hw/hyperv/hyperv: " Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 15/22] hw/core/machine: Fix indentation Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 16/22] hw/pci/pcie_port: Fix pcie_slot_is_hotpluggbale_bus typo Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 17/22] hw/acpi/ged: Fix wrong identation Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 18/22] hw/i386/acpi-build: Fix build_append_notfication_callback typo Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 19/22] hw/i386/acpi-build: Update document reference Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 20/22] hw/i386/acpi-build: Fix typo and grammar in comment Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 21/22] hw/acpi/pcihp: Fix typo in function name Philippe Mathieu-Daudé
2025-05-06 14:35 ` [PULL 22/22] hw/isa/ich9: Remove stray empty comment Philippe Mathieu-Daudé
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=aBwERHkcHPymjbk8@liuwe-devbox-ubuntu-v2.tail21d00.ts.net \
--to=wei.liu@kernel.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.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 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).