Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1617250

Re: [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed CLOSid

From Shivappa Vikas <vikas.shivappa@intel.com>
Newsgroups linux.kernel
Subject Re: [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed CLOSid
Date 2017-04-05 20:10 +0200
Message-ID <tsXxv-63J-1@gated-at.bofh.it> (permalink)
References <tsi1j-40v-5@gated-at.bofh.it> <tsi1k-40v-21@gated-at.bofh.it> <tsV2G-4nq-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



On Wed, 5 Apr 2017, Thomas Gleixner wrote:

> On Mon, 3 Apr 2017, Vikas Shivappa wrote:
>
>> Subject: x86/intel_rdt: Fix issue when mkdir uses a freed CLOSid
>
> This subject line is useless again. It want's to be descriptive.
>
> "Fix issue" Which issue?
>
>> Each resctrl directory has one CLOSid allocated which is mapped to a
>> control register/QOS_MSR. During an rmdir this CLOSid is freed and can
>> be reused later when a new directory is created.  Currently we do not
>> reset the QOS_MSR to a default when the CLOSid is freed. So when the
>> next mkdir uses a freed CLOSid, the new directory is associated with a
>> stale QOS_MSR.
>
> That's not an issue. That's maybe something people are not expecting.
>
>> Fix this issue by writing a default value to the QOS_MSR when the
>> associated CLOSid is freed. The default value is all 1s for CBM which
>> means no control is enforced when a mkdir reuses this CLOSid.
>
> That's just wrong.
>
> The proper behaviour for a new control group is, that at the time when it
> is created it copies the CBM values of the default group and not claiming
> access to ALL of the cache by default.

The behaviour of the default/root group is having access to all cache. Because 
we set the value of all CBMs to all 1s and then root group takes CLOS 0. This is 
trying to set the same values for all newly created groups.

Thanks,
Vikas

>
> Thanks,
>
> 	tglx
>
>
>

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 0/3 V3] x86/intel_rdt: Improvements/Fixes to RDT framework Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-04-03 23:50 +0200
  [PATCH 3/3] x86/intel_rdt: Update schemata read to show data in tabular format Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-04-03 23:50 +0200
    [tip:x86/cpu] x86/intel_rdt: Update schemata read to show data in  tabular format tip-bot for Vikas Shivappa <tipbot@zytor.com> - 2017-04-05 17:40 +0200
  [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed CLOSid Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-04-03 23:50 +0200
    Re: [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed  CLOSid Thomas Gleixner <tglx@linutronix.de> - 2017-04-05 17:30 +0200
      Re: [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed  CLOSid Shivappa Vikas <vikas.shivappa@intel.com> - 2017-04-05 20:10 +0200
      Re: [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed  CLOSid "Luck, Tony" <tony.luck@intel.com> - 2017-04-05 20:10 +0200
        Re: [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed  CLOSid Fenghua Yu <fenghua.yu@intel.com> - 2017-04-05 22:20 +0200
  [PATCH 2/3] x86/intel_rdt: Implement "update" mode when writing schemata file Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-04-03 23:50 +0200
    [tip:x86/cpu] x86/intel_rdt: Implement "update" mode when writing  schemata file tip-bot for Tony Luck <tipbot@zytor.com> - 2017-04-05 17:40 +0200

csiph-web