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

Re: [Xen-devel] [PATCH] Allow programatic iomem permissions


  • To: Kieran Mansley <kmansley@xxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Fri, 13 Jul 2007 15:12:17 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 13 Jul 2007 07:10:11 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfFV9FwD8fORjFLEdy48QAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] Allow programatic iomem permissions

On 13/7/07 14:03, "Kieran Mansley" <kmansley@xxxxxxxxxxxxxx> wrote:

>> The issue is that the granter is informed that the grant is released before
>> stale grantee TLB entries are flushed. If the grantee is multi-vcpu then he
>> could theoretically still access a granted page via a stale TLB entry after
>> the granter has recycled the page. The window is extremely tiny though! The
>> correct fix is to reorder the unmap operation to be unmap-list-of-grants
>> then TLB-flush then update-grant-entries-to-indicate-release. Then the whole
>> problem disappears.
> 
> OK, that makes sense, and doesn't at first impression look too hard to
> rectify.
> 
> Am I right in thinking that it's the shared grant table entry that is
> the critical one in this sense (as opposed to the "active" entry).

That's correct.

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