All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: atishp@atishpatra.org,  anup@brainfault.org,  will@kernel.org,
	mark.rutland@arm.com,  paul.walmsley@sifive.com,
	 palmer@dabbelt.com, aou@eecs.berkeley.edu,
	 linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 Conor.Dooley@microchip.com
Subject: Re: [PATCH v3] drivers/perf: riscv_pmu_sbi: add support for PMU variant on T-Head C9xx cores
Date: Mon, 05 Sep 2022 16:30:48 +0200	[thread overview]
Message-ID: <mvm4jxlao6f.fsf@suse.de> (raw)
In-Reply-To: <20220905141644.2468891-1-heiko@sntech.de> (Heiko Stuebner's message of "Mon, 5 Sep 2022 16:16:44 +0200")

On Sep 05 2022, Heiko Stuebner wrote:

> To work properly, this requires a matching change in SBI, though the actual
> interface between kernel and SBI does not change.

What happens if you mix different kernel and SBI versions?

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
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: Andreas Schwab <schwab@suse.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: atishp@atishpatra.org, anup@brainfault.org, will@kernel.org,
	mark.rutland@arm.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Conor.Dooley@microchip.com
Subject: Re: [PATCH v3] drivers/perf: riscv_pmu_sbi: add support for PMU variant on T-Head C9xx cores
Date: Mon, 05 Sep 2022 16:30:48 +0200	[thread overview]
Message-ID: <mvm4jxlao6f.fsf@suse.de> (raw)
In-Reply-To: <20220905141644.2468891-1-heiko@sntech.de> (Heiko Stuebner's message of "Mon, 5 Sep 2022 16:16:44 +0200")

On Sep 05 2022, Heiko Stuebner wrote:

> To work properly, this requires a matching change in SBI, though the actual
> interface between kernel and SBI does not change.

What happens if you mix different kernel and SBI versions?

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2022-09-05 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 14:16 [PATCH v3] drivers/perf: riscv_pmu_sbi: add support for PMU variant on T-Head C9xx cores Heiko Stuebner
2022-09-05 14:16 ` Heiko Stuebner
2022-09-05 14:30 ` Andreas Schwab [this message]
2022-09-05 14:30   ` Andreas Schwab
2022-09-05 18:59   ` Heiko Stübner
2022-09-05 18:59     ` Heiko Stübner
2022-09-05 19:17 ` Conor.Dooley
2022-09-05 19:17   ` Conor.Dooley
2022-09-07 17:57 ` Heiko Stübner
2022-09-07 17:57   ` Heiko Stübner
     [not found] ` <CAOnJCU+SXQsho=t1vUQFiiDVU7-F0yaAH3ae4nUdYQWEyjmsjw@mail.gmail.com>
2022-09-07 23:15   ` Atish Patra
2022-09-07 23:15     ` 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=mvm4jxlao6f.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=Conor.Dooley@microchip.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.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 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.