linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul@pwsan.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: Ji Sheng Teoh <jisheng.teoh@starfivetech.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Locus Wei-Han Chen <locus84@andestech.com>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Yu Chien Peter Lin <peterlin@andestech.com>
Subject: linux-next: manual merge of the risc-v tree with the arm64 tree
Date: Fri, 15 Mar 2024 10:31:46 +1100	[thread overview]
Message-ID: <20240315103146.225b653b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]

Hi all,

Today's linux-next merge of the risc-v tree got a conflict in:

  drivers/perf/Kconfig

between commits:

  c2b24812f7bc ("perf: starfive: Add StarLink PMU support")
  f0dbc6d0de38 ("perf: starfive: Only allow COMPILE_TEST for 64-bit architectures")

from the arm64 tree and commit:

  bc969d6cc96a ("perf: RISC-V: Introduce Andes PMU to support perf event sampling")

from the risc-v tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/perf/Kconfig
index 004d86230aa6,564e813d8c69..000000000000
--- a/drivers/perf/Kconfig
+++ b/drivers/perf/Kconfig
@@@ -86,15 -86,20 +86,29 @@@ config RISCV_PMU_SB
  	  full perf feature support i.e. counter overflow, privilege mode
  	  filtering, counter configuration.
  
 +config STARFIVE_STARLINK_PMU
 +	depends on ARCH_STARFIVE || (COMPILE_TEST && 64BIT)
 +	bool "StarFive StarLink PMU"
 +	help
 +	   Provide support for StarLink Performance Monitor Unit.
 +	   StarLink Performance Monitor Unit integrates one or more cores with
 +	   an L3 memory system. The L3 cache events are added into perf event
 +	   subsystem, allowing monitoring of various L3 cache perf events.
 +
+ config ANDES_CUSTOM_PMU
+ 	bool "Andes custom PMU support"
+ 	depends on ARCH_RENESAS && RISCV_ALTERNATIVE && RISCV_PMU_SBI
+ 	default y
+ 	help
+ 	  The Andes cores implement the PMU overflow extension very
+ 	  similar to the standard Sscofpmf and Smcntrpmf extension.
+ 
+ 	  This will patch the overflow and pending CSRs and handle the
+ 	  non-standard behaviour via the regular SBI PMU driver and
+ 	  interface.
+ 
+ 	  If you don't know what to do here, say "Y".
+ 
  config ARM_PMU_ACPI
  	depends on ARM_PMU && ACPI
  	def_bool y

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-03-14 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 23:31 Stephen Rothwell [this message]
2024-03-15 17:21 ` linux-next: manual merge of the risc-v tree with the arm64 tree Palmer Dabbelt
2024-03-15 18:19   ` Catalin Marinas
  -- strict thread matches above, loose matches on Subject: below --
2021-01-27 23:27 Stephen Rothwell
2021-02-14 21:52 ` Stephen Rothwell
2019-08-12 23:34 Stephen Rothwell
2019-08-13  8:24 ` Will Deacon
2019-08-13  8:42   ` Stephen Rothwell
2019-08-13  8:53     ` Will Deacon
2019-08-13 22:24   ` Paul Walmsley
2019-08-14  9:00     ` Will Deacon

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=20240315103146.225b653b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=catalin.marinas@arm.com \
    --cc=jisheng.teoh@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=locus84@andestech.com \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul@pwsan.com \
    --cc=peterlin@andestech.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;
as well as URLs for NNTP newsgroup(s).