* ARM perf events spin locks
@ 2010-11-30 10:08 Jamie Iles
2010-11-30 10:41 ` Will Deacon
0 siblings, 1 reply; 8+ messages in thread
From: Jamie Iles @ 2010-11-30 10:08 UTC (permalink / raw)
To: linux-arm-kernel
Hi Will,
I think we should convert the spinlocks in the ARM perf events code to raw
spinlocks for realtime. Should we wait for your split set to get merged first
before doing this?
Jamie
^ permalink raw reply [flat|nested] 8+ messages in thread
* ARM perf events spin locks
2010-11-30 10:08 ARM perf events spin locks Jamie Iles
@ 2010-11-30 10:41 ` Will Deacon
2010-11-30 10:58 ` Jamie Iles
0 siblings, 1 reply; 8+ messages in thread
From: Will Deacon @ 2010-11-30 10:41 UTC (permalink / raw)
To: linux-arm-kernel
> Hi Will,
Hello,
> I think we should convert the spinlocks in the ARM perf events code to raw
> spinlocks for realtime. Should we wait for your split set to get merged first
> before doing this?
Since this is a logically separate change, I think we're better off waiting
until the split stuff has been merged. As for the raw spinlocks, by realtime
do you mean PREEMPT_RT? Also, do we actually *need* raw spinlocks in the perf
code?
Will
^ permalink raw reply [flat|nested] 8+ messages in thread
* ARM perf events spin locks
2010-11-30 10:41 ` Will Deacon
@ 2010-11-30 10:58 ` Jamie Iles
2010-11-30 13:49 ` Will Deacon
0 siblings, 1 reply; 8+ messages in thread
From: Jamie Iles @ 2010-11-30 10:58 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Nov 30, 2010 at 10:41:04AM -0000, Will Deacon wrote:
> > Hi Will,
>
> Hello,
>
> > I think we should convert the spinlocks in the ARM perf events code to raw
> > spinlocks for realtime. Should we wait for your split set to get merged first
> > before doing this?
>
> Since this is a logically separate change, I think we're better off waiting
> until the split stuff has been merged. As for the raw spinlocks, by realtime
> do you mean PREEMPT_RT? Also, do we actually *need* raw spinlocks in the perf
> code?
Yes, I meant PREEMPT_RT. It won't stop working without raw spinlocks but I'm
not convinced that we couldn't lose too much accuracy with normal spinlocks. I
am however willing to be convinced otherwise!
Jamie
^ permalink raw reply [flat|nested] 8+ messages in thread
* ARM perf events spin locks
2010-11-30 10:58 ` Jamie Iles
@ 2010-11-30 13:49 ` Will Deacon
2010-11-30 13:54 ` Jamie Iles
0 siblings, 1 reply; 8+ messages in thread
From: Will Deacon @ 2010-11-30 13:49 UTC (permalink / raw)
To: linux-arm-kernel
Jamie,
> On Tue, Nov 30, 2010 at 10:41:04AM -0000, Will Deacon wrote:
> > > Hi Will,
> >
> > Hello,
> >
> > > I think we should convert the spinlocks in the ARM perf events code to raw
> > > spinlocks for realtime. Should we wait for your split set to get merged first
> > > before doing this?
> >
> > Since this is a logically separate change, I think we're better off waiting
> > until the split stuff has been merged. As for the raw spinlocks, by realtime
> > do you mean PREEMPT_RT? Also, do we actually *need* raw spinlocks in the perf
> > code?
> Yes, I meant PREEMPT_RT. It won't stop working without raw spinlocks but I'm
> not convinced that we couldn't lose too much accuracy with normal spinlocks. I
> am however willing to be convinced otherwise!
Well struct perf_event_ctx has a lock field which is of type raw_spinlock_t.
I *think* this is always held by the core perf code before calling the backend,
however IRQs may still be enabled so we probably do need to change our pmu_lock.
Is that a sane analysis?
Will
^ permalink raw reply [flat|nested] 8+ messages in thread
* ARM perf events spin locks
2010-11-30 13:49 ` Will Deacon
@ 2010-11-30 13:54 ` Jamie Iles
2010-11-30 13:59 ` Will Deacon
0 siblings, 1 reply; 8+ messages in thread
From: Jamie Iles @ 2010-11-30 13:54 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Nov 30, 2010 at 01:49:32PM -0000, Will Deacon wrote:
> Jamie,
>
> > On Tue, Nov 30, 2010 at 10:41:04AM -0000, Will Deacon wrote:
> > > > Hi Will,
> > >
> > > Hello,
> > >
> > > > I think we should convert the spinlocks in the ARM perf events code to raw
> > > > spinlocks for realtime. Should we wait for your split set to get merged first
> > > > before doing this?
> > >
> > > Since this is a logically separate change, I think we're better off waiting
> > > until the split stuff has been merged. As for the raw spinlocks, by realtime
> > > do you mean PREEMPT_RT? Also, do we actually *need* raw spinlocks in the perf
> > > code?
> > Yes, I meant PREEMPT_RT. It won't stop working without raw spinlocks but I'm
> > not convinced that we couldn't lose too much accuracy with normal spinlocks. I
> > am however willing to be convinced otherwise!
>
> Well struct perf_event_ctx has a lock field which is of type raw_spinlock_t.
> I *think* this is always held by the core perf code before calling the backend,
> however IRQs may still be enabled so we probably do need to change our pmu_lock.
>
> Is that a sane analysis?
That sounds perfectly reasonable to me! We don't hold these locks for any
potentially long periods of time so it's probably better to be safe! Do you
want me to make this change after perf-split is merged or is that something
you're happy to do?
Jamie
^ permalink raw reply [flat|nested] 8+ messages in thread
* ARM perf events spin locks
2010-11-30 13:54 ` Jamie Iles
@ 2010-11-30 13:59 ` Will Deacon
2010-11-30 14:31 ` Russell King - ARM Linux
0 siblings, 1 reply; 8+ messages in thread
From: Will Deacon @ 2010-11-30 13:59 UTC (permalink / raw)
To: linux-arm-kernel
> > Well struct perf_event_ctx has a lock field which is of type raw_spinlock_t.
> > I *think* this is always held by the core perf code before calling the backend,
> > however IRQs may still be enabled so we probably do need to change our pmu_lock.
> >
> > Is that a sane analysis?
> That sounds perfectly reasonable to me! We don't hold these locks for any
> potentially long periods of time so it's probably better to be safe! Do you
> want me to make this change after perf-split is merged or is that something
> you're happy to do?
I don't mind doing it as a separate patch after Russell has pulled my
perf-split branch. I don't think it should form part of the pull though
because it's unrelated.
Will
^ permalink raw reply [flat|nested] 8+ messages in thread
* ARM perf events spin locks
2010-11-30 13:59 ` Will Deacon
@ 2010-11-30 14:31 ` Russell King - ARM Linux
2010-11-30 14:46 ` Will Deacon
0 siblings, 1 reply; 8+ messages in thread
From: Russell King - ARM Linux @ 2010-11-30 14:31 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Nov 30, 2010 at 01:59:10PM -0000, Will Deacon wrote:
> > > Well struct perf_event_ctx has a lock field which is of type raw_spinlock_t.
> > > I *think* this is always held by the core perf code before calling the backend,
> > > however IRQs may still be enabled so we probably do need to change our pmu_lock.
> > >
> > > Is that a sane analysis?
> > That sounds perfectly reasonable to me! We don't hold these locks for any
> > potentially long periods of time so it's probably better to be safe! Do you
> > want me to make this change after perf-split is merged or is that something
> > you're happy to do?
>
> I don't mind doing it as a separate patch after Russell has pulled my
> perf-split branch.
You mean this?
commit f1690d17d2c7afa2a2079e3c91eb2bca8c1c5ecd
Merge: 612275a 43eab87
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Fri Nov 26 10:26:43 2010 +0000
Merge branch 'perf-split' of git://linux-arm.org/linux-2.6-wd into devel-stable
Sorry, I didn't push the tree out for a week or so because I was busy with
other things (like the pgtable stuff.)
^ permalink raw reply [flat|nested] 8+ messages in thread* ARM perf events spin locks
2010-11-30 14:31 ` Russell King - ARM Linux
@ 2010-11-30 14:46 ` Will Deacon
0 siblings, 0 replies; 8+ messages in thread
From: Will Deacon @ 2010-11-30 14:46 UTC (permalink / raw)
To: linux-arm-kernel
> > I don't mind doing it as a separate patch after Russell has pulled my
> > perf-split branch.
>
> You mean this?
>
> commit f1690d17d2c7afa2a2079e3c91eb2bca8c1c5ecd
> Merge: 612275a 43eab87
> Author: Russell King <rmk+kernel@arm.linux.org.uk>
> Date: Fri Nov 26 10:26:43 2010 +0000
>
> Merge branch 'perf-split' of git://linux-arm.org/linux-2.6-wd into devel-stable
Aha, brilliant - thanks.
> Sorry, I didn't push the tree out for a week or so because I was busy with
> other things (like the pgtable stuff.)
There's no rest for the weary! I'll submit the patch to fix perf for sparse
to the patch system (I didn't realise you'd pulled my changes on Friday) and
tackle this spinlock thing at the same time.
Cheers,
Will
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-11-30 14:46 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-11-30 10:08 ARM perf events spin locks Jamie Iles
2010-11-30 10:41 ` Will Deacon
2010-11-30 10:58 ` Jamie Iles
2010-11-30 13:49 ` Will Deacon
2010-11-30 13:54 ` Jamie Iles
2010-11-30 13:59 ` Will Deacon
2010-11-30 14:31 ` Russell King - ARM Linux
2010-11-30 14:46 ` Will Deacon
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).