From: James Morse <james.morse@arm.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Babu Moger <Babu.Moger@amd.com>
Subject: Re: [PATCH v3] x86/resctrl: Preserve CDP enable over cpuhp
Date: Fri, 17 Apr 2020 16:33:10 +0100 [thread overview]
Message-ID: <2030b4e2-bf52-592c-ac67-ddc2aa5f918c@arm.com> (raw)
In-Reply-To: <e762a1c9-b13a-cc8c-e945-292218af418b@intel.com>
Hi guys,
On 17/04/2020 15:57, Reinette Chatre wrote:
> On 4/17/2020 7:18 AM, Borislav Petkov wrote:
>> On Wed, Apr 15, 2020 at 08:57:34AM -0700, Reinette Chatre wrote:
>>> Hi Thomas and Borislav,
>>>
>>> Could you please consider this patch for inclusion as a fix for v5.7?
>>
>> Do you mean by that that I should add
>>
>> Cc: <stable@vger.kernel.org>
>>
>> so that it goes to stable?
Is the CC-stable still required? I've seen a 'Fixes' tag on its own cause patches to get
picked up...
>> The commit in Fixes: is from 4.10-ish times...
>>
>
> Borislav: Sorry about that and thank you very much for catching this
> omission. Yes, this patch needs to go to stable.
> James: would you be able to do the backports to stable? Please note that
> support for L2 and L3 CDP was added across Linux versions and the
> resctrl files moved around since then so the backport would need some
> changes to address this issue in all versions.
Yes, certainly!
Thanks,
James
next prev parent reply other threads:[~2020-04-17 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 16:21 James Morse
2020-02-24 18:23 ` Reinette Chatre
2020-04-15 15:57 ` Reinette Chatre
2020-04-17 14:18 ` Borislav Petkov
2020-04-17 14:57 ` Reinette Chatre
2020-04-17 15:33 ` James Morse [this message]
2020-04-17 16:47 ` Borislav Petkov
2020-04-17 17:45 ` [tip: x86/urgent] x86/resctrl: Preserve CDP enable over CPU hotplug tip-bot2 for James Morse
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2030b4e2-bf52-592c-ac67-ddc2aa5f918c@arm.com \
--to=james.morse@arm.com \
--cc=Babu.Moger@amd.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®