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

Re: [Xen-devel] evtchn_do_upcall() barrier between upcall_pending and pending_sel


  • To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 08 May 2008 11:25:59 +0100
  • Delivery-date: Thu, 08 May 2008 03:26:35 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aciw9eg/JpRA4BzpEd28OwAX8io7RQ==
  • Thread-topic: [Xen-devel] evtchn_do_upcall() barrier between upcall_pending and pending_sel

Makes sense, yes.

 -- Keir

On 8/5/08 11:18, "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx> wrote:

> Hello,
> 
> In evtchn_do_upcall() there is a barrier between setting upcall_pending
> and pending_sel, which makes sense to avoid losing events, however I
> don't understand why it is a rmb(). memory-barriers.txt says that rmb()
> only provides ordering of reads, not stores.  Shouldn't that be a wmb()
> instead then?
> 
> Samuel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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