From: Shivappa Vikas <firstname.lastname@example.org>
To: Thomas Gleixner <email@example.com>
Cc: "Luck, Tony" <firstname.lastname@example.org>,
Vikas Shivappa <email@example.com>,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
Subject: Re: [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed CLOSid
Date: Tue, 11 Apr 2017 11:51:16 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1704111149590.3728@vshiva-Udesk> (raw)
On Mon, 10 Apr 2017, Thomas Gleixner wrote:
> On Wed, 5 Apr 2017, Luck, Tony wrote:
>> On Wed, Apr 05, 2017 at 05:20:24PM +0200, Thomas Gleixner wrote:
>>> 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.
>> I don't see that as any more helpful. When you make a new
>> control group it is because none of the existing groups
>> provides the QoS that you want. So the first thing the
>> user will do is write the schemata file with the values
>> they do want.
>> So "all access", or "same as default group" are both the
>> same to the user ... not what they want.
>> We do need to make sure that the schemata matches what is
>> in the registers. We need to make sure that changes to the
>> schemata file result in the MSRs being written where needed.
> That's true today. The MSRs and the schemata file of a newly created group
> always match. So there's nothing to fix, right?
Yes. Upstream patch has the MSRs matching with what schemata shows. we can drop
this patch. I sent a new MBA version without this just on the tip which has the
other two patches.
next prev parent reply other threads:[~2017-04-11 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 21:44 [PATCH 0/3 V3] x86/intel_rdt: Improvements/Fixes to RDT framework Vikas Shivappa
2017-04-03 21:44 ` [PATCH 1/3] x86/intel_rdt: Fix issue when mkdir uses a freed CLOSid Vikas Shivappa
2017-04-05 15:20 ` Thomas Gleixner
2017-04-05 18:03 ` Shivappa Vikas
2017-04-05 18:07 ` Luck, Tony
2017-04-05 20:17 ` Fenghua Yu
2017-04-10 17:08 ` Thomas Gleixner
2017-04-11 18:51 ` Shivappa Vikas [this message]
2017-04-03 21:44 ` [PATCH 2/3] x86/intel_rdt: Implement "update" mode when writing schemata file Vikas Shivappa
2017-04-05 15:27 ` [tip:x86/cpu] " tip-bot for Tony Luck
2017-04-03 21:44 ` [PATCH 3/3] x86/intel_rdt: Update schemata read to show data in tabular format Vikas Shivappa
2017-04-05 15:28 ` [tip:x86/cpu] " tip-bot for Vikas Shivappa
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.