From: Borislav Petkov <bp@alien8.de>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: Babu Moger <babu.moger@amd.com>,
tony.luck@intel.com, x86@kernel.org, Dave.Martin@arm.com,
james.morse@arm.com, corbet@lwn.net, skhan@linuxfoundation.org,
rdunlap@infradead.org, tglx@kernel.org, mingo@redhat.com,
dave.hansen@linux.intel.com, hpa@zytor.com, kas@kernel.org,
rick.p.edgecombe@intel.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-coco@lists.linux.dev,
kvm@vger.kernel.org
Subject: Re: [PATCH v6 2/2] x86,fs/resctrl: Keep mbm_assign_mode in default mode at boot
Date: Fri, 30 Oct 2026 18:07:44 -0700 [thread overview]
Message-ID: <20261031010744.GFauU_YJdX2eV6GoHV@fat_crate.local> (raw)
In-Reply-To: <3ebc7028-c559-4add-800a-614b29d66ba3@intel.com>
On Fri, Oct 30, 2026 at 03:08:09PM -0700, Reinette Chatre wrote:
> To help future readers understand how we landed on this I think it may be useful
> to add a link to the decision that resulted in this fix. For example:
>
> ...
> Leave mbm_assign_mode in default mode during initialization as decided in [2].
> ...
> Link: https://lore.kernel.org/20260804191608.GDanI6eK2Q07w6pNcb@fat_crate.local # [2]
I can fix that up when applying, yes.
Any other Links I should add? I don't have a problem with leaving enough
breadcrumbs for the future...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2026-10-31 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 20:28 [PATCH v6 0/2] x86,fs/resctrl: Keep default MBM mode at boot and fix ABMC programming Babu Moger
2026-10-30 20:28 ` [PATCH v6 1/2] x86/resctrl: Fix ABMC counter programming Babu Moger
2026-10-30 20:28 ` [PATCH v6 2/2] x86,fs/resctrl: Keep mbm_assign_mode in default mode at boot Babu Moger
2026-10-30 22:08 ` Reinette Chatre
2026-10-31 1:07 ` Borislav Petkov [this message]
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=20261031010744.GFauU_YJdX2eV6GoHV@fat_crate.local \
--to=bp@alien8.de \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--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®