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

RE: [Xen-ia64-devel][PATCH] Enable SMP on VTI domain.


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Thu, 1 Jun 2006 11:46:05 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 31 May 2006 20:46:42 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcaFIPPQ7P8F2mPTSeGUOb6ZFkKD9wABo8dQ
  • Thread-topic: [Xen-ia64-devel][PATCH] Enable SMP on VTI domain.

>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>Sent: 2006?6?1? 10:12
>To: Xu, Anthony
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-ia64-devel][PATCH] Enable SMP on VTI domain.
>
>
>On Wed, May 31, 2006 at 03:32:06PM +0800, Xu, Anthony wrote:
>> This patch intends to enable SMP on VTI domain.
>>
>> This patch depends on previous three patches I sent out.
>> 1. fixed a bug which causes Oops
>> 2. fixed a small bug about VTLB
>> 3. Add sal emulation to VTI domain
>>
>> This patch uses IPI to implement global purge.
>
>I just took a quick look at your patch though.
>There is no protection to IPI.
>Is it O.K? Does the use of IPI cause race?
>
Do you mean below code?
#ifdef XEN
        spin_lock(&call_lock);
#else

Or you mean the protection of global purge.
When a vcpu get IPI to purge TLB,
What it does is to invalid the TLB entry in VHPT,
but not remove the TLB entry.
There is no race condition.

>--
>yamahata

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


 


Rackspace

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