From: Borislav Petkov <bp@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Babu Moger <babu.moger@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>
Subject: Re: [PATCH] x86: avoid confusion over the new RESCTRL config prompt
Date: Sat, 2 Feb 2019 01:06:15 +0100 [thread overview]
Message-ID: <20190202000615.GA15335@zn.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F7D4E216D@ORSMSX110.amr.corp.intel.com>
On Fri, Feb 01, 2019 at 07:18:35PM +0000, Luck, Tony wrote:
> For now. But very soon we will also have ARM_CPU_RESCTRL, and some of
> this code will become generic. Will we need an arch-independent name for the
> bits of code shared by arm and x86?
Yes. The idea still is to have the arch-specific stuff under
X86_CPU_RESCTRL and ARM_CPU_RESCTRL respectively, and the arch-agnostic
pieces under CPU_RESCTRL.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-02-02 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 22:52 [PATCH] x86: avoid confusion over the new RESCTRL config prompt Johannes Weiner
2019-01-29 23:08 ` Borislav Petkov
2019-01-29 23:46 ` Luck, Tony
2019-01-30 16:46 ` Johannes Weiner
2019-01-30 17:19 ` Borislav Petkov
2019-01-30 19:56 ` Johannes Weiner
2019-02-01 19:18 ` Luck, Tony
2019-02-02 0:06 ` Borislav Petkov [this message]
2019-02-02 9:45 ` [tip:x86/urgent] x86/resctrl: Avoid confusion over the new X86_RESCTRL config tip-bot for Johannes Weiner
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=20190202000615.GA15335@zn.tnic \
--to=bp@suse.de \
--cc=babu.moger@amd.com \
--cc=fenghua.yu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tony.luck@intel.com \
/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 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.