From: Ingo Molnar <mingo@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Babu Moger <babu.moger@amd.com>,
fenghua.yu@intel.com, reinette.chatre@intel.com,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
eranian@google.com, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 00/10] x86/resctrl: Support for AMD QoS new features and bug fix
Date: Tue, 2 Aug 2022 11:39:28 +0200 [thread overview]
Message-ID: <Yujw0FOMj3tS0f3k@gmail.com> (raw)
In-Reply-To: <13d16a59-0b13-8484-380c-21deb864f0f2@gmail.com>
* Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> On 8/2/22 03:55, Babu Moger wrote:
> > v2:
> > a. Rebased the patches to latest stable tree (v5.18.15). Resolved some conflicts.
> > b. Added the patch to fix CBM issue on AMD. This was originally discussed
> > https://lore.kernel.org/lkml/20220517001234.3137157-1-eranian@google.com/
> >
>
> Shouldn't this series be rebased on tip tree? I think it's odd to base
> new feature series on stable tree, since patches on the latter are mostly
> bugfixes backported from mainline.
Normally that's true, but AFAICS the patchset applies cleanly to latest
-tip as well, so 'stable == tip' in this regard.
Series looks good to me (without having tested it):
Reviewed-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2022-08-02 9:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 20:55 [PATCH v2 00/10] x86/resctrl: Support for AMD QoS new features and bug fix Babu Moger
2022-08-01 20:55 ` [PATCH v2 01/10] x86/resctrl: Fix min_cbm_bits for AMD Babu Moger
2022-08-01 20:55 ` [PATCH v2 02/10] x86/cpufeatures: Add Slow Memory Bandwidth Allocation feature flag Babu Moger
2022-08-01 20:55 ` [PATCH v2 03/10] x86/resctrl: Add a new resource type RDT_RESOURCE_SMBA Babu Moger
2022-08-01 20:56 ` [PATCH v2 04/10] x86/resctrl: Detect and configure Slow Memory Bandwidth allocation Babu Moger
2022-08-01 20:56 ` [PATCH v2 05/10] x86/cpufeatures: Add Bandwidth Monitoring Event Configuration feature flag Babu Moger
2022-08-01 20:56 ` [PATCH v2 06/10] x86/resctrl: Introduce mon_configurable to detect Bandwidth Monitoring Event Configuration Babu Moger
2022-08-01 20:56 ` [PATCH v2 07/10] x86/resctrl: Add sysfs interface files to read/write event configuration Babu Moger
2022-08-01 20:56 ` [PATCH v2 08/10] x86/resctrl: Add the sysfs interface to read the " Babu Moger
2022-08-01 20:56 ` [PATCH v2 09/10] x86/resctrl: Add sysfs interface to write " Babu Moger
2022-08-01 20:56 ` [PATCH v2 10/10] Documentation/x86: Update resctrl_ui.rst for new features Babu Moger
2022-08-03 3:50 ` Bagas Sanjaya
2022-08-03 15:59 ` Moger, Babu
2022-08-04 7:57 ` Bagas Sanjaya
2022-08-02 2:16 ` [PATCH v2 00/10] x86/resctrl: Support for AMD QoS new features and bug fix Bagas Sanjaya
2022-08-02 9:39 ` Ingo Molnar [this message]
2022-08-02 13:41 ` Moger, Babu
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=Yujw0FOMj3tS0f3k@gmail.com \
--to=mingo@kernel.org \
--cc=babu.moger@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).