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

RE: [Xen-devel][RFC]degradation on IPF due to hypercall set irq


  • To: "Keir Fraser" <keir@xxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Thu, 23 Nov 2006 09:51:38 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 22 Nov 2006 17:51:52 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccN5wYmUmir46SdT8a+ptVHeNZ8fgAHbs2mAACOJaAAASp7iwAAG0VmAAB2zNAAAmxzrgAAEGDgAAAZWmIAAC5KoAAAk0fTAAD34HAAAGv3kgAgLWhQ
  • Thread-topic: [Xen-devel][RFC]degradation on IPF due to hypercall set irq

Keir Fraser write on 2006年11月22日 18:28:
> On 22/11/06 10:23, "Xu, Anthony" <anthony.xu@xxxxxxxxx> wrote:
> 
>> I prefer atomic access, we used it in shared PIC.
>> If each thread flush multicall seperately, There are some extra
>> hypercalls.
> 
> Since the threads run independently there seems little choice but for
> each to be able to flush. If the IDE DMA support had been properly
> integrated into the qemu select() event loop this would not be an
> issue.


Agree, we can use pipe to integrate IDE DMA support into select.
But we still need to use atomic access to shawdow line.

--Anthony
   
> 
>  -- Keir

_______________________________________________
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®.