Re: [RFC PATCH V2 13/22] x86/intel_rdt: Support schemata write - pseudo-locking core

[Thomas Gleixner]

On Wed, 28 Feb 2018, Reinette Chatre wrote:
> On 2/28/2018 10:39 AM, Thomas Gleixner wrote:
> > I came up with this under the assumptions:
> > 
> >   1) One locked region per resource group
> >   2) Drop closid after locking
> 
> I am also now working under these assumptions ...
> 
> > Then the restrict file makes a lot of sense because it would give a clear
> > selection of the possible resource to lock.
> 
> ... but I am still stuck on why this restrict file is needed at this
> time. Surely it would be needed if later we add the more flexible
> exclusive mode, but I do not understand how it helps the locked mode.

You're right. Brainfart on my side. With that scheme it's really only
useful for a flexible exclusive mode, which would be nice to have but is
not a prerequisite for now.

Thanks,

	tglx