From: Borislav Petkov <bp@alien8.de>
To: Wen Pu <puwen@hygon.cn>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"jgross@suse.com" <jgross@suse.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"Jason@zx2c4.com" <Jason@zx2c4.com>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 0/2] arch/x86: Set L2 Cache ID on AMD processors
Date: Tue, 11 Apr 2023 14:23:48 +0200 [thread overview]
Message-ID: <20230411122348.GAZDVRVNvbbS8F5NUB@fat_crate.local> (raw)
In-Reply-To: <7d5f81e3-0890-ae35-2e5c-59d1b0950297@hygon.cn>
On Tue, Apr 11, 2023 at 12:10:38PM +0000, Wen Pu wrote:
> I have tested the function cacheinfo_amd_init_l2c_id() on Hygon machine,
> it had the same result as yours above. So Hygon also should set the
> l2c_id. Could you please set it for Hygon, or should I send a separate
> patch?
Separate patch please.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-04-11 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 16:35 K Prateek Nayak
2023-04-10 16:35 ` [PATCH 1/2] " K Prateek Nayak
2023-04-10 16:35 ` [PATCH 2/2] x86/Documentation: Add documentation about cluster K Prateek Nayak
2023-04-11 3:58 ` Bagas Sanjaya
2023-04-11 10:57 ` K Prateek Nayak
2023-04-11 8:25 ` Peter Zijlstra
2023-04-11 10:55 ` K Prateek Nayak
[not found] ` <7d5f81e3-0890-ae35-2e5c-59d1b0950297@hygon.cn>
2023-04-11 12:23 ` Borislav Petkov [this message]
2023-04-13 13:17 ` [PATCH 0/2] arch/x86: Set L2 Cache ID on AMD processors Oleksandr Natalenko
2023-04-13 17:33 ` K Prateek Nayak
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=20230411122348.GAZDVRVNvbbS8F5NUB@fat_crate.local \
--to=bp@alien8.de \
--cc=Jason@zx2c4.com \
--cc=andrew.cooper3@citrix.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=puwen@hygon.cn \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.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®