qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 0/4] Updates based on feedback.


From: Justin Terry (VM)
Subject: Re: [Qemu-devel] [PATCH v2 0/4] Updates based on feedback.
Date: Thu, 25 Jan 2018 20:12:57 +0000

Hey Stefan,

Your welcome! Excited to help.

I have only tried Ubuntu and Windows guests. Is there a set you would recommend 
to try out?

As for limitations, this set of patches allows for both bios and efi based 
boots (we have been using TianoCore). We will continue to submit patches around 
performance tuning on the platform but basic functionality is up and running in 
this set. The VGA interrupt path can be improved and we are looking at options 
here to make this a smoother experience. And as mentioned in the update we 
don't have CPUID support fully implemented yet for migration scenarios. Was 
there a specific set of things you were wondering that I could investigate or 
provide clarity on?

Thanks,
Justin

> -----Original Message-----
> From: Stefan Hajnoczi [mailto:address@hidden
> Sent: Thursday, January 25, 2018 3:02 AM
> To: Justin Terry (VM) <address@hidden>
> Cc: address@hidden; address@hidden; address@hidden;
> address@hidden; address@hidden
> Subject: Re: [Qemu-devel] [PATCH v2 0/4] Updates based on feedback.
> 
> On Mon, Jan 22, 2018 at 01:07:45PM -0800, Justin Terry (VM) via Qemu-devel
> wrote:
> > Updates based on review feedback.
> >
> > 1. Fixes style issues and properly ran the scripts/checkpatch pre 
> > submission.
> > 2. Added migration blockers for CPUID, dirty memory tracking, and
> XSAVE/XRSTOR.
> > 3. Fixed some bugs around register states when using bios vs efi.
> >
> > Justin Terry (VM) (4):
> >   Add the Windows Hypervisor Platform accelerator.
> >   Add the WHPX vcpu API
> >   Introduce the WHPX impl
> >   Add the WHPX acceleration enlightenments
> 
> This could be huge for QEMU on Windows users.  Thanks for doing this!
> 
> Which guest OSes have you tested?
> 
> What are the known limitations (after all, the code is quite small and maybe 
> not
> everything is implemented yet in this patch series)?
> 
> Stefan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]