Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-23 Thread Greg KH
On Wed, May 23, 2018 at 10:19:41AM -0700, Reinette Chatre wrote: > Hi Greg, > > On 5/23/2018 1:05 AM, Greg KH wrote: > > On Tue, May 22, 2018 at 02:02:37PM -0700, Reinette Chatre wrote: > >> On 5/22/2018 12:43 PM, Greg KH wrote: > >>> On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-23 Thread Greg KH
On Wed, May 23, 2018 at 10:19:41AM -0700, Reinette Chatre wrote: > Hi Greg, > > On 5/23/2018 1:05 AM, Greg KH wrote: > > On Tue, May 22, 2018 at 02:02:37PM -0700, Reinette Chatre wrote: > >> On 5/22/2018 12:43 PM, Greg KH wrote: > >>> On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-23 Thread Reinette Chatre
Hi Greg, On 5/23/2018 1:05 AM, Greg KH wrote: > On Tue, May 22, 2018 at 02:02:37PM -0700, Reinette Chatre wrote: >> On 5/22/2018 12:43 PM, Greg KH wrote: >>> On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: + ret = strtobool(buf, ); + if (ret == 0 && bv) { +

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-23 Thread Reinette Chatre
Hi Greg, On 5/23/2018 1:05 AM, Greg KH wrote: > On Tue, May 22, 2018 at 02:02:37PM -0700, Reinette Chatre wrote: >> On 5/22/2018 12:43 PM, Greg KH wrote: >>> On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: + ret = strtobool(buf, ); + if (ret == 0 && bv) { +

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-23 Thread Greg KH
On Tue, May 22, 2018 at 02:02:37PM -0700, Reinette Chatre wrote: > Hi Greg, > > Thank you very much for taking a look. > > On 5/22/2018 12:43 PM, Greg KH wrote: > > On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: > >> @@ -149,6 +151,9 @@ struct pseudo_lock_region { > >>

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-23 Thread Greg KH
On Tue, May 22, 2018 at 02:02:37PM -0700, Reinette Chatre wrote: > Hi Greg, > > Thank you very much for taking a look. > > On 5/22/2018 12:43 PM, Greg KH wrote: > > On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: > >> @@ -149,6 +151,9 @@ struct pseudo_lock_region { > >>

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-22 Thread Reinette Chatre
Hi Greg, Thank you very much for taking a look. On 5/22/2018 12:43 PM, Greg KH wrote: > On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: >> @@ -149,6 +151,9 @@ struct pseudo_lock_region { >> unsigned intline_size; >> unsigned intsize; >>

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-22 Thread Reinette Chatre
Hi Greg, Thank you very much for taking a look. On 5/22/2018 12:43 PM, Greg KH wrote: > On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: >> @@ -149,6 +151,9 @@ struct pseudo_lock_region { >> unsigned intline_size; >> unsigned intsize; >>

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-22 Thread Greg KH
On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: > @@ -149,6 +151,9 @@ struct pseudo_lock_region { > unsigned intline_size; > unsigned intsize; > void*kmem; > +#ifdef CONFIG_INTEL_RDT_DEBUGFS > + struct dentry

Re: [PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-22 Thread Greg KH
On Tue, May 22, 2018 at 04:29:22AM -0700, Reinette Chatre wrote: > @@ -149,6 +151,9 @@ struct pseudo_lock_region { > unsigned intline_size; > unsigned intsize; > void*kmem; > +#ifdef CONFIG_INTEL_RDT_DEBUGFS > + struct dentry

[PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-22 Thread Reinette Chatre
There is no simple yes/no test to determine if pseudo-locking was successful. In order to test pseudo-locking we expose a debugfs file for each pseudo-locked region that will record the latency of reading the pseudo-locked memory at a stride of 32 bytes (hardcoded). These numbers will give us an

[PATCH V4 34/38] x86/intel_rdt: Create debugfs files for pseudo-locking testing

2018-05-22 Thread Reinette Chatre
There is no simple yes/no test to determine if pseudo-locking was successful. In order to test pseudo-locking we expose a debugfs file for each pseudo-locked region that will record the latency of reading the pseudo-locked memory at a stride of 32 bytes (hardcoded). These numbers will give us an