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

Re: [Xen-devel] [PATCH v2] xen: handle paged gfn in wrmsr_hypervisor_regs


  • To: Olaf Hering <olaf@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Fri, 03 May 2013 16:55:15 +0100
  • Cc: xen-devel@xxxxxxxxxxxxx
  • Delivery-date: Fri, 03 May 2013 15:55:41 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac5IFpn4aqmDszQzDECorJNutY4t5g==
  • Thread-topic: [Xen-devel] [PATCH v2] xen: handle paged gfn in wrmsr_hypervisor_regs

On 03/05/2013 16:19, "Olaf Hering" <olaf@xxxxxxxxx> wrote:

> On Fri, May 03, Jan Beulich wrote:
> 
>>>>> On 03.05.13 at 16:26, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>>> I suggest the following return codes:
>>>  0: not handled
>>>  1: handled
>>>  -EINVAL: error during handling
>>>  -EAGAIN: retry
>>> 
>>> The HVM callers should then handle as follows:
>>>  -EAGAIN: rc = X86EMUL_RETRY
>>>  -EINVAL: goto gp_fault
>>>  0: try other msr handlers (if any)
>>>  1: we're done, return X86EMUL_OKAY
>>> 
>>> Does that make sense?
>> 
>> Sure - you may have seen my later reply where I also notide
>> this mistake in my first response to Olaf.
> 
> I sent v3 of the patch. I had to guess which 'return 0' is supposed to
> be an error.

You guessed correctly ;)

> Olaf



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.