public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	kvm-devel@lists.sourceforge.net, Zachary Amsden <zach@vmware.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [PATCH 2/3] Refactor hypercall infrastructure (v3)
Date: Tue, 18 Sep 2007 08:31:04 -0500	[thread overview]
Message-ID: <46EFD318.3070401@codemonkey.ws> (raw)
In-Reply-To: <46EFD24C.2050701@qumranet.com>

Avi Kivity wrote:
> Avi Kivity wrote:
>   
>> Avi Kivity wrote:
>>     
>>> Anthony Liguori wrote:
>>>  
>>>       
>>>> This patch refactors the current hypercall infrastructure to better 
>>>> support live
>>>> migration and SMP.  It eliminates the hypercall page by trapping the UD
>>>> exception that would occur if you used the wrong hypercall 
>>>> instruction for the
>>>> underlying architecture and replacing it with the right one lazily.
>>>>
>>>> It also introduces the infrastructure to probe for hypercall 
>>>> available via
>>>> CPUID leaves 0x40000000.  CPUID leaf 0x40000001 should be filled out by
>>>> userspace.
>>>>
>>>> A fall-out of this patch is that the unhandled hypercalls no longer 
>>>> trap to
>>>> userspace.  There is very little reason though to use a hypercall to 
>>>> communicate
>>>> with userspace as PIO or MMIO can be used.  There is no code in tree 
>>>> that uses
>>>> userspace hypercalls.
>>>>
>>>>       
>>>>         
>>> Surprisingly, this patch kills Windows XP (ACPI HAL).  I'll try to 
>>> find out why.
>>>
>>>   
>>>       
>> Not trapping #UD brings things back to normal.  So, Windows likes to 
>> execute undefined instructions, and we don'd handle these well.
>>
>>     
> Okay, vmx_inject_ud() was broken.  Fixed now.
>   

Yeah, I was just about to send the patch for that.  Sorry about that, I 
didn't even think to test Windows...

Regards,

Anthony Liguori

  reply	other threads:[~2007-09-18 13:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 19:57 [PATCH 1/3] Add vmmcall/vmcall to x86_emulate (v3) Anthony Liguori
     [not found] ` <1190059071649-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-17 19:57   ` [PATCH 2/3] Refactor hypercall infrastructure (v3) Anthony Liguori
     [not found]     ` <11900590723438-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-17 19:57       ` [PATCH 3/3] Add the paravirtualization CPUID entry to QEMU (v3) Anthony Liguori
2007-09-17 21:56       ` [PATCH 2/3] Refactor hypercall infrastructure (v3) Nakajima, Jun
2007-09-18 13:10       ` Avi Kivity
     [not found]         ` <46EFCE2A.1020105-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-18 13:12           ` Avi Kivity
     [not found]             ` <46EFCED0.5050209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-18 13:27               ` Avi Kivity
2007-09-18 13:31                 ` Anthony Liguori [this message]
2007-09-18  9:18   ` [PATCH 1/3] Add vmmcall/vmcall to x86_emulate (v3) Avi Kivity

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=46EFD318.3070401@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=jeremy@goop.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zach@vmware.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