From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Wei Liu <liuwe@linux.microsoft.com>,
Roman Bolshakov <rbolshakov@ddn.com>,
Phil Dennis-Jordan <phil@philjordan.eu>,
Zhao Liu <zhao1.liu@intel.com>,
Sergio Andres Gomez Del Real <Sergio.G.DelReal@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [RFC PATCH] target/i386: Report TPR accesses to HVF
Date: Tue, 1 Jul 2025 18:35:52 +0200 [thread overview]
Message-ID: <c9a161db-1220-452e-88bb-7887bafb6986@linaro.org> (raw)
In-Reply-To: <20250616090632.55214-1-philmd@linaro.org>
Ping?
On 16/6/25 11:06, Philippe Mathieu-Daudé wrote:
> HVF should be able to handle task priority register accesses.
>
> Cc: Sergio Andres Gomez Del Real <Sergio.G.DelReal@gmail.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> RFC: Untested as I don't have access to such setup, noticed
> during code review.
> ---
> target/i386/helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/i386/helper.c b/target/i386/helper.c
> index e0aaed3c4c4..a0555e74cc6 100644
> --- a/target/i386/helper.c
> +++ b/target/i386/helper.c
> @@ -549,7 +549,7 @@ void cpu_report_tpr_access(CPUX86State *env, TPRAccess access)
> X86CPU *cpu = env_archcpu(env);
> CPUState *cs = env_cpu(env);
>
> - if (kvm_enabled() || whpx_enabled() || nvmm_enabled()) {
> + if (kvm_enabled() || whpx_enabled() || nvmm_enabled() || hvf_enabled()) {
> env->tpr_access_type = access;
>
> cpu_interrupt(cs, CPU_INTERRUPT_TPR);
next prev parent reply other threads:[~2025-07-01 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 9:06 [RFC PATCH] target/i386: Report TPR accesses to HVF Philippe Mathieu-Daudé
2025-07-01 16:35 ` Philippe Mathieu-Daudé [this message]
2025-07-02 2:29 ` Zhao Liu
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=c9a161db-1220-452e-88bb-7887bafb6986@linaro.org \
--to=philmd@linaro.org \
--cc=Sergio.G.DelReal@gmail.com \
--cc=liuwe@linux.microsoft.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=phil@philjordan.eu \
--cc=qemu-devel@nongnu.org \
--cc=rbolshakov@ddn.com \
--cc=zhao1.liu@intel.com \
/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).