From: Peter Zijlstra <peterz@infradead.org>
To: Arjan <8vvbbqzo567a@nospam.xutrox.com>
Cc: Cody Yao-oc <CodyYao-oc@zhaoxin.com>,
mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, tglx@linutronix.de, bp@alien8.de,
hpa@zytor.com, x86@kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, shyaololo@163.com
Subject: Re: [PATCH] x86/perf: Fixed kernel panic during boot on Nano processor.
Date: Sun, 16 Oct 2022 11:59:49 +0200 [thread overview]
Message-ID: <Y0vWFXQ2vLBaM3Ki@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <b38ecb38-2709-0c75-fe08-375dd4a87d5f@nospam.xutrox.com>
On Sun, Oct 16, 2022 at 11:53:14AM +0200, Arjan wrote:
> On 13-10-2022 17:07, Peter Zijlstra wrote:
> > On Mon, Jun 07, 2021 at 09:31:09AM +0800, Cody Yao-oc wrote:
> > > From: CodyYao-oc <CodyYao-oc@zhaoxin.com>
> > >
> > > Nano processor may not fully support rdpmc instruction, it works well
> > > for reading general pmc counter, but will lead to GP(general protection)
> > > when accessing fixed pmc counter. Futhermore, family/model information
> > > is same between Nano processor and ZX-C processor, it leads to zhaoxin
> > > pmu driver is wrongly loaded for Nano processor, which resulting boot
> > > kernal fail.
> > >
> > > To solve this problem, stepping information will be checked to distinguish
> > > between Nano processor and ZX-C processor.
> > >
> > > [https://bugzilla.kernel.org/show_bug.cgi?id=212389]
> > >
> > > Reported-by: Arjan <8vvbbqzo567a@nospam.xutrox.com>
> > > Signed-off-by: CodyYao-oc <CodyYao-oc@zhaoxin.com>
> >
> > *sigh*.. so this email address doesn't exist, as such I can't apply this
> > patch. Consider it dropped.
>
> If it's about my email address: The address exists and works.
> If the nospam part bothers you, that part can be left out. You may leave the reported-by line out if you want to.
The SoB address (CodyYao-oc@zhaoxin.com) bounced for me -- since that's
the patch author that is somewhat important.
next prev parent reply other threads:[~2022-10-16 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 1:31 [PATCH] x86/perf: Fixed kernel panic during boot on Nano processor Cody Yao-oc
2021-06-30 4:38 ` Codyyao-oc
2022-10-13 13:49 ` Thorsten Leemhuis
2022-10-13 13:59 ` Peter Zijlstra
2022-10-13 15:07 ` Peter Zijlstra
2022-10-16 9:53 ` Arjan
2022-10-16 9:59 ` Peter Zijlstra [this message]
2022-10-16 10:56 ` 8vvbbqzo567a
2022-11-03 3:23 silviazhao-oc
2022-11-03 10:07 ` 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=Y0vWFXQ2vLBaM3Ki@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=8vvbbqzo567a@nospam.xutrox.com \
--cc=CodyYao-oc@zhaoxin.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=shyaololo@163.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).