qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Wang, Wenchao" <wenchao.wang@intel.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: haxm-team <haxm-team@intel.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] target/i386/hax: Add XCR0 support
Date: Fri, 25 Nov 2022 14:37:11 +0100	[thread overview]
Message-ID: <4e35a2b6-12ca-e43c-6ee7-7090280c9341@linaro.org> (raw)
In-Reply-To: <DM6PR11MB40909B4A33D66A3100F6D219870E9@DM6PR11MB4090.namprd11.prod.outlook.com>

Hi,

On 25/11/22 13:18, Wang, Wenchao wrote:
> Hi, maintainers,
> 
> As HAXM v7.8.0 is released and it added XCR0 support, could you help to 
> merge this patch to add corresponding support into HAX user space of 
> QEMU? The patch has been included in the attachment. Thanks.

See 
https://www.qemu.org/docs/master/devel/submitting-a-patch.html#submitting-your-patches 
on how to send patches to a mailing list.

> 
> Best Regards,
> 
> Wenchao
> 
>  From b1789f2523d06798b8883664bfa9a9df797bfccf Mon Sep 17 00:00:00 2001
> 
> From: Wenchao Wang <wenchao.wang@intel.com>
> 
> Date: Fri, 25 Nov 2022 18:37:34 +0800
> 
> Subject: [PATCH] target/i386/hax: Add XCR0 support
> 
> Introduce extended control register XCR0 to support XSAVE feature set.
> 
> Note: This change requires at least HAXM v7.8.0 to support.
> 
> Reviewed-by: Hang Yuan <hang.yuan@intel.com>
> 
> Signed-off-by: Wenchao Wang <wenchao.wang@intel.com>
> 
> ---
> 
> target/i386/hax/hax-interface.h | 2 ++
> 
> 1 file changed, 2 insertions(+)
> 
> diff --git a/target/i386/hax/hax-interface.h 
> b/target/i386/hax/hax-interface.h
> 
> index 537ae084e9..1d13bb2380 100644
> 
> --- a/target/i386/hax/hax-interface.h
> 
> +++ b/target/i386/hax/hax-interface.h
> 
> @@ -201,6 +201,8 @@ struct vcpu_state_t {
> 
>       uint64_t _cr3;
> 
>       uint64_t _cr4;
> 
> +    uint64_t _xcr0;
> 
> +
> 
>       uint64_t _dr0;
> 
>       uint64_t _dr1;
> 
>       uint64_t _dr2;
> 
> -- 
> 
> 2.17.1
> 

Is that the full patch? It is missing the register use in 
hax_sync_vcpu_register()...

Regards,

Phil.


  reply	other threads:[~2022-11-25 13:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 12:18 [PATCH] target/i386/hax: Add XCR0 support Wang, Wenchao
2022-11-25 13:37 ` Philippe Mathieu-Daudé [this message]
2022-11-28  8:10   ` Wang, Wenchao
2022-12-27 15:13     ` Paolo Bonzini
2022-12-28  2:55       ` Wang, Wenchao
2022-12-28  8:23         ` Paolo Bonzini
2022-12-28  8:54           ` Wang, Wenchao
2023-01-10  9:30           ` Wang, Wenchao
2022-12-28  3:28       ` Wang, Wenchao
2022-12-05  8:35   ` Wang, Wenchao
2022-12-05  9:05     ` Philippe Mathieu-Daudé
2022-12-05  9:10       ` Wang, Wenchao
2022-12-08  8:22       ` Wang, Wenchao
2022-12-19  9:01       ` Wang, Wenchao
2022-12-19  9:09         ` Philippe Mathieu-Daudé
2022-12-19  9:19           ` Wang, Wenchao
2022-12-27  9:15           ` Wang, Wenchao
  -- strict thread matches above, loose matches on Subject: below --
2022-12-14  9:15 Wang, Wenchao
2022-12-14  9:39 ` Thomas Huth
2022-12-15  9:45   ` Wang, Wenchao
2022-12-15 10:26     ` Peter Maydell
2022-12-16  8:47       ` Wang, Wenchao

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=4e35a2b6-12ca-e43c-6ee7-7090280c9341@linaro.org \
    --to=philmd@linaro.org \
    --cc=haxm-team@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wenchao.wang@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).