public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Will Deacon <will@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Christoffer Dall <cdall@cs.columbia.edu>,
	Marc Zyngier <maz@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	"Rob Herring (Arm)" <robh@kernel.org>
Subject: Re: linux-next: manual merge of the kvm-arm tree with the arm-perf tree
Date: Wed, 12 Mar 2025 10:07:52 -0700	[thread overview]
Message-ID: <Z9G_aKHzs4GFe4O5@linux.dev> (raw)
In-Reply-To: <20250312124501.GA6181@willie-the-truck>

On Wed, Mar 12, 2025 at 12:45:02PM +0000, Will Deacon wrote:
> On Wed, Mar 12, 2025 at 08:18:53PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the kvm-arm tree got a conflict in:
> > 
> >   drivers/perf/apple_m1_cpu_pmu.c
> > 
> > between commit:
> > 
> >   c2e793da59fc ("perf: apple_m1: Don't disable counter in m1_pmu_enable_event()")
> > 
> > from the arm-perf tree and commit:
> > 
> >   75ecffc361bb ("drivers/perf: apple_m1: Refactor event select/filter configuration")
> > 
> > from the kvm-arm 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/apple_m1_cpu_pmu.c
> > index 39349ecec3c1,6be703619a97..000000000000
> > --- a/drivers/perf/apple_m1_cpu_pmu.c
> > +++ b/drivers/perf/apple_m1_cpu_pmu.c
> > @@@ -396,7 -428,11 +428,7 @@@ static void m1_pmu_enable_event(struct 
> >   	user = event->hw.config_base & M1_PMU_CFG_COUNT_USER;
> >   	kernel = event->hw.config_base & M1_PMU_CFG_COUNT_KERNEL;
> >   
> > - 	m1_pmu_configure_counter(event->hw.idx, evt, user, kernel);
> >  -	m1_pmu_disable_counter_interrupt(event->hw.idx);
> >  -	m1_pmu_disable_counter(event->hw.idx);
> >  -	isb();
> >  -
> > + 	m1_pmu_configure_counter(event->hw.idx, event->hw.config_base);
> >   	m1_pmu_enable_counter(event->hw.idx);
> >   	m1_pmu_enable_counter_interrupt(event->hw.idx);
> >   	isb();
> 
> Looks fine to me but I'd also be happy to stick the first two patches
> on a shared branch to avoid this. Oliver?

Agreed!

  git://git.kernel.org/pub/scm/linux/kernel/git/oupton/linux.git perf/m1-guest-events

Thanks,
Oliver

  reply	other threads:[~2025-03-12 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  9:18 linux-next: manual merge of the kvm-arm tree with the arm-perf tree Stephen Rothwell
2025-03-12 12:45 ` Will Deacon
2025-03-12 17:07   ` Oliver Upton [this message]
2025-03-13 21:17     ` 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=Z9G_aKHzs4GFe4O5@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=cdall@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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