From: Conor Dooley <conor@kernel.org>
To: Mayuresh Chitale <mchitale@ventanamicro.com>
Cc: Atish Patra <atishp@atishpatra.org>,
Anup Patel <anup@brainfault.org>,
Andrew Jones <ajones@ventanamicro.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] drivers/perf: Risc-V: Update platform specific firmware event handling
Date: Tue, 15 Aug 2023 14:19:53 +0100 [thread overview]
Message-ID: <20230815-myself-disk-61b0a5535624@spud> (raw)
In-Reply-To: <20230814043134.367280-1-mchitale@ventanamicro.com>
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
On Mon, Aug 14, 2023 at 10:01:34AM +0530, Mayuresh Chitale wrote:
> SBI specification [1] reserves an event code for platform specific
> firmware events. Update the driver to use the new reserved event code
> for platform specific firmware events. Also update the raw event parsing
> to use bits 63:62 instead of only bit 63 to distinguish between the raw
> event types. The platform specific firmware events must be specified in
> the perf command as in the below example:
> perf stat -e rc000000000000001 <command>
> where [63:62] = 0x3 indicates a platform specific firmware event
>
> Link: https://github.com/riscv-non-isa/riscv-sbi-doc/commit/c4bfdf9 [1]
> Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
Hmm, another question - is this actually in a frozen version of the SBI
spec? I might've got distracted during the last PRS meeting and be
unaware, but I had it in my head that it was not frozen.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-08-15 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 4:31 [PATCH] drivers/perf: Risc-V: Update platform specific firmware event handling Mayuresh Chitale
2023-08-15 13:14 ` Conor Dooley
2023-08-15 13:19 ` Conor Dooley [this message]
2023-08-16 6:58 ` Atish Patra
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=20230815-myself-disk-61b0a5535624@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=heiko@sntech.de \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchitale@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=will@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