From: Yu-Chien Peter Lin <peterlin@andestech.com>
To: Conor Dooley <conor@kernel.org>
Cc: <paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <linux-riscv@lists.infradead.org>,
<prabhakar.mahadev-lad.rj@bp.renesas.com>, <tim609@andestech.com>,
<dylan@andestech.com>, <locus84@andestech.com>,
<dminus@andestech.com>
Subject: Re: [PATCH v2 00/10] Support Andes PMU extension
Date: Fri, 20 Oct 2023 16:05:45 +0800 [thread overview]
Message-ID: <ZTI02VmswE5eR-_0@APC323> (raw)
In-Reply-To: <20231019-cargo-outright-1c0a34431626@spud>
On Thu, Oct 19, 2023 at 03:51:00PM +0100, Conor Dooley wrote:
> On Thu, Oct 19, 2023 at 09:52:38PM +0800, Yu Chien Peter Lin wrote:
> > Hi All,
> >
> > This patch series introduces the Andes PMU extension, which serves
> > the same purpose as Sscofpmf. In this version we use FDT-based
> > probing and the CONFIG_ANDES_CUSTOM_PMU to enable perf sampling
> > and filtering support.
> >
> > Its non-standard local interrupt is assigned to bit 18 in the
> > custom S-mode local interrupt pending CSR (slip), while the
> > interrupt cause is (256 + 18).
>
> Chief, you gotta thread your patchsets. It seems like every mail in this
> series has been sent individually, which is going to break tools like
> b4 and the automated testing on patchwork.
Hi Conor,
Sure, thanks for taking care of this!
Regards,
Peter Lin
> Cheers,
> Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-10-20 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 13:52 [PATCH v2 00/10] Support Andes PMU extension Yu Chien Peter Lin
2023-10-19 14:51 ` Conor Dooley
2023-10-20 8:05 ` Yu-Chien Peter Lin [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=ZTI02VmswE5eR-_0@APC323 \
--to=peterlin@andestech.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=dminus@andestech.com \
--cc=dylan@andestech.com \
--cc=linux-riscv@lists.infradead.org \
--cc=locus84@andestech.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tim609@andestech.com \
/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