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

Re: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback


  • To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 27 Mar 2007 01:33:58 +0100
  • Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 26 Mar 2007 17:34:53 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdwB5uK2iXXG9v6Edu/NgAWy6hiGQ==
  • Thread-topic: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback



On 26/3/07 22:08, "Herbert Xu" <herbert@xxxxxxxxxxxxxxxxxxx> wrote:

>> Can't we wrap the 'swap around' critical section in an irq-safe spinlock?
>> All we'd need to do from the page-fault handler then is a barrier on that
>> spinlock (i.e, wait for it to be released). Netback can simply copy the page
>> to new memory frame, unmap the grant, then relocate the new memory frame's
>> pseudophysical address.
> 
> That works fine for the x86 case.  But when it's auto-translated,
> you won't even get a page fault in the guest because the guest PTE
> is unchanged and completely valid.

How about you invalidate the PTE for the duration of the critical section.
It's a bit skanky, but would work around this issue quite nicely!

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