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

Re: [Xen-devel] [PATCH] an obvious fix to PIC IO intercept


  • To: "Li, Xin B" <xin.b.li@xxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Fri, 13 Oct 2006 22:45:43 +0100
  • Delivery-date: Fri, 13 Oct 2006 14:56:51 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbuMfZd+m00pUnBSgOFo1LNeBzEQQA1Z+fQAAI773AAABpAWg==
  • Thread-topic: [Xen-devel] [PATCH] an obvious fix to PIC IO intercept

No signed-off-by -- are you posting this just for info right now?

The other (PIC) patch is fine. I'll take it for 3.0.3.

 -- Keir


On 13/10/06 10:44 pm, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:

>  this patch is to fix INS/OUTS.
> Thanks
> -Xin
> 
>> -----Original Message-----
>> From: Li, Xin B 
>> Sent: 2006年10月14日 4:43
>> To: Li, Xin B; Xen Devel
>> Subject: RE: [Xen-devel] [PATCH] an obvious fix to PIC IO intercept
>> 
>> Hi Keir, this fix is critical to stability of HVM.
>> BTW, we are fixing MOVS and INS/OUTS for HVM, hopefully
>> sending the patch tomorrow, acturally the code is totally
>> messed up, althought they are nearly never used, but we
>> believe they do introduce stability issue.
>> thanks
>> -Xin 
>> 
>>> -----Original Message-----
>>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Li, Xin B
>>> Sent: 2006年10月13日 3:10
>>> To: Xen Devel
>>> Subject: [Xen-devel] [PATCH] an obvious fix to PIC IO intercept
>>> 
>>> an obvious fix to PIC IO intercept.
>>> In PIC IO, address from send_pio_req is physical address already.
>>> 
>>> Signed-off-by: Xiaohui Xin <xiaohui.xin@xxxxxxxxx>
>>> Signed-off-by: Xiaowei Yang <xiaowei.yang@xxxxxxxxx>
>>> Signed-off-by: Xin Li <xin.b.li@xxxxxxxxx>
>>> 
>> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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