All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Mayuresh Chitale <mchitale@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, atishp@atishpatra.org,
	anup@brainfault.org, will@kernel.org, mark.rutland@arm.com,
	ajones@ventanamicro.com, conor.dooley@microchip.com,
	alexghiti@rivosinc.com, samuel.holland@sifive.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] perf/riscv-sbi: Add platform specific firmware event handling
Date: Tue, 24 Sep 2024 06:40:31 +0000	[thread overview]
Message-ID: <172716003175.3899939.6074882511014223752.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240812051109.6496-1-mchitale@ventanamicro.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Mon, 12 Aug 2024 05:11:09 +0000 you wrote:
> The SBI v2.0 specification pointed to by the link below reserves the
> event code 0xffff for platform specific firmware events. Update the driver
> to be able to parse and program such events. The platform specific
> firmware events must now be specified in the perf command as below:
> perf stat -e rCxxx ...
> where bits[63:62] = 0x3 of the event config indicate a platform specific
> firmware event and xxx indicate the actual event code which is passed
> as the event data.
> 
> [...]

Here is the summary with links:
  - [v1] perf/riscv-sbi: Add platform specific firmware event handling
    https://git.kernel.org/riscv/c/f0c9363db2dd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Mayuresh Chitale <mchitale@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, atishp@atishpatra.org,
	anup@brainfault.org, will@kernel.org, mark.rutland@arm.com,
	ajones@ventanamicro.com, conor.dooley@microchip.com,
	alexghiti@rivosinc.com, samuel.holland@sifive.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] perf/riscv-sbi: Add platform specific firmware event handling
Date: Tue, 24 Sep 2024 06:40:31 +0000	[thread overview]
Message-ID: <172716003175.3899939.6074882511014223752.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240812051109.6496-1-mchitale@ventanamicro.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Mon, 12 Aug 2024 05:11:09 +0000 you wrote:
> The SBI v2.0 specification pointed to by the link below reserves the
> event code 0xffff for platform specific firmware events. Update the driver
> to be able to parse and program such events. The platform specific
> firmware events must now be specified in the perf command as below:
> perf stat -e rCxxx ...
> where bits[63:62] = 0x3 of the event config indicate a platform specific
> firmware event and xxx indicate the actual event code which is passed
> as the event data.
> 
> [...]

Here is the summary with links:
  - [v1] perf/riscv-sbi: Add platform specific firmware event handling
    https://git.kernel.org/riscv/c/f0c9363db2dd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




  reply	other threads:[~2024-09-24  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12  5:11 [PATCH v1] perf/riscv-sbi: Add platform specific firmware event handling Mayuresh Chitale
2024-08-12  5:11 ` Mayuresh Chitale
2024-09-24  6:40 ` patchwork-bot+linux-riscv [this message]
2024-09-24  6:40   ` patchwork-bot+linux-riscv

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=172716003175.3899939.6074882511014223752.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alexghiti@rivosinc.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=conor.dooley@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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=samuel.holland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.