Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-20 Thread Thomas Gleixner
On Tue, 20 Feb 2018, Reinette Chatre wrote: > On 2/20/2018 2:00 AM, Thomas Gleixner wrote: > > On Mon, 19 Feb 2018, Reinette Chatre wrote: > >> In addition to the above research from my side I also followed up with > >> the CPU architects directly to question the usage of these instructions > >> in

Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-20 Thread Reinette Chatre
Hi Thomas, On 2/20/2018 2:00 AM, Thomas Gleixner wrote: > On Mon, 19 Feb 2018, Reinette Chatre wrote: >> On 2/19/2018 3:19 PM, Thomas Gleixner wrote: >>> On Mon, 19 Feb 2018, Reinette Chatre wrote: On 2/19/2018 1:19 PM, Thomas Gleixner wrote: > On Tue, 13 Feb 2018, Reinette Chatre wrote:

Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-20 Thread Thomas Gleixner
On Mon, 19 Feb 2018, Reinette Chatre wrote: > On 2/19/2018 3:19 PM, Thomas Gleixner wrote: > > On Mon, 19 Feb 2018, Reinette Chatre wrote: > >> On 2/19/2018 1:19 PM, Thomas Gleixner wrote: > >>> On Tue, 13 Feb 2018, Reinette Chatre wrote: > >>> > After a pseudo-locked region is locked it needs

Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-19 Thread Reinette Chatre
Hi Thomas, On 2/19/2018 3:19 PM, Thomas Gleixner wrote: > On Mon, 19 Feb 2018, Reinette Chatre wrote: >> On 2/19/2018 1:19 PM, Thomas Gleixner wrote: >>> On Tue, 13 Feb 2018, Reinette Chatre wrote: >>> After a pseudo-locked region is locked it needs to be associated with the RDT domain r

Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-19 Thread Thomas Gleixner
On Mon, 19 Feb 2018, Reinette Chatre wrote: > Hi Thomas, > > On 2/19/2018 1:19 PM, Thomas Gleixner wrote: > > On Tue, 13 Feb 2018, Reinette Chatre wrote: > > > >> After a pseudo-locked region is locked it needs to be associated with > >> the RDT domain representing the pseudo-locked cache so tha

Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-19 Thread Reinette Chatre
Hi Thomas, On 2/19/2018 1:19 PM, Thomas Gleixner wrote: > On Tue, 13 Feb 2018, Reinette Chatre wrote: > >> After a pseudo-locked region is locked it needs to be associated with >> the RDT domain representing the pseudo-locked cache so that its life >> cycle can be managed correctly. >> >> Only a

Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-19 Thread Thomas Gleixner
On Tue, 13 Feb 2018, Reinette Chatre wrote: > After a pseudo-locked region is locked it needs to be associated with > the RDT domain representing the pseudo-locked cache so that its life > cycle can be managed correctly. > > Only a single pseudo-locked region can exist on any cache instance so we

[RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain

2018-02-13 Thread Reinette Chatre
After a pseudo-locked region is locked it needs to be associated with the RDT domain representing the pseudo-locked cache so that its life cycle can be managed correctly. Only a single pseudo-locked region can exist on any cache instance so we maintain a single pointer to a pseudo-locked region fr