Re: [PATCH v2 2/2] x86/pat: Avoid contention on cpa_lock if possible

* Ido Yariv wrote: > Hi Ingo, > > On Wed, Aug 22, 2012 at 10:47:02AM +0200, Ingo Molnar wrote: > > > > * Ido Yariv wrote: > > > > > vSMP Foundation does not require to serialize CPA by guaranteeing that > > > the most recent TLB entry will always be used. > > > > > > To avoid needless conte

Re: [PATCH v2 2/2] x86/pat: Avoid contention on cpa_lock if possible

Hi Ingo, On Wed, Aug 22, 2012 at 10:47:02AM +0200, Ingo Molnar wrote: > > * Ido Yariv wrote: > > > vSMP Foundation does not require to serialize CPA by guaranteeing that > > the most recent TLB entry will always be used. > > > > To avoid needless contention on cpa_lock, do not lock/unlock it i

Re: [PATCH v2 2/2] x86/pat: Avoid contention on cpa_lock if possible

* Ido Yariv wrote: > vSMP Foundation does not require to serialize CPA by guaranteeing that > the most recent TLB entry will always be used. > > To avoid needless contention on cpa_lock, do not lock/unlock it if it > isn't necessary. > > Based on work by Shai Fultheim . > > Signed-off-by: Ido

[PATCH v2 2/2] x86/pat: Avoid contention on cpa_lock if possible

vSMP Foundation does not require to serialize CPA by guaranteeing that the most recent TLB entry will always be used. To avoid needless contention on cpa_lock, do not lock/unlock it if it isn't necessary. Based on work by Shai Fultheim . Signed-off-by: Ido Yariv Acked-by: Shai Fultheim --- Cha