From: Borislav Petkov <bp@alien8.de>
To: silviazhaooc <silviazhao-oc@zhaoxin.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, namhyung@kernel.org, tglx@linutronix.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
cobechen@zhaoxin.com, louisqi@zhaoxin.com,
silviazhao@zhaoxin.com, tonywwang@zhaoxin.com,
kevinbrace@gmx.com, 8vvbbqzo567a@nospam.xutrox.com
Subject: Re: [PATCH] x86/perf/zhaoxin: Add stepping check for ZX-C
Date: Mon, 6 Feb 2023 10:48:32 +0100 [thread overview]
Message-ID: <Y+DM8BZUi6a10hXY@zn.tnic> (raw)
In-Reply-To: <51ab21ee-403b-f4ce-9a7e-2580ab7e8118@zhaoxin.com>
On Mon, Feb 06, 2023 at 04:26:25PM +0800, silviazhaooc wrote:
> Due to our company’s email policy, email address with oc suffix is used for
> sending email without confidentiality statement at the end of the mail body.
>
> I will remove –oc from my name later.
Yes, please. The email address is fine but the name doesn't have to have
that funky "-oc" thing.
> But due to some unknown historical reasons, the FMS of Nano and ZXC are only
> different in stepping.
>
> I have considered about using the “Model name string” to distinguish them,
> but it doesn't seem to be a common way in Linux kernel.
I don't mind you using steppings to differentiate the two as long as
this is not going to change all of a sudden and that differentiation is
unambiguous.
If not, you will have to use name strings as you don't have any other
choice.
Whatever you do, pls define a new X86_BUG_ flag, set it only on Nano and
then test it in the PMU init code.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-02-06 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:17 [PATCH] x86/perf/zhaoxin: Add stepping check for ZX-C silviazhao-oc
2023-02-02 23:53 ` Kevin Brace
2023-02-03 3:12 ` silviazhaooc
2023-02-04 13:44 ` Borislav Petkov
2023-02-06 8:26 ` silviazhaooc
2023-02-06 9:48 ` Borislav Petkov [this message]
2023-02-06 10:55 ` silviazhaooc
2023-02-06 11:13 ` Borislav Petkov
2023-02-07 8:42 ` silviazhaooc
2023-02-07 18:30 ` Borislav Petkov
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=Y+DM8BZUi6a10hXY@zn.tnic \
--to=bp@alien8.de \
--cc=8vvbbqzo567a@nospam.xutrox.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=cobechen@zhaoxin.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=kevinbrace@gmx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=louisqi@zhaoxin.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=silviazhao-oc@zhaoxin.com \
--cc=silviazhao@zhaoxin.com \
--cc=tglx@linutronix.de \
--cc=tonywwang@zhaoxin.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