Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1471868 > unrolled thread
| Started by | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| First post | 2016-08-29 16:20 +0200 |
| Last post | 2016-08-29 16:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks Peter Zijlstra <peterz@infradead.org> - 2016-08-29 16:20 +0200
Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-29 16:50 +0200
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Date | 2016-08-29 16:20 +0200 |
| Subject | Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks |
| Message-ID | <sbvzP-8mr-1@gated-at.bofh.it> |
On Wed, Aug 24, 2016 at 05:15:54PM +0300, Alexander Shishkin wrote: > @@ -221,10 +245,13 @@ static void __bts_event_start(struct perf_event *event) > > /* > * local barrier to make sure that ds configuration made it > - * before we enable BTS > + * before we enable BTS and bts::state goes ACTIVE > */ > wmb(); > > + /* INACTIVE/STOPPED -> ACTIVE */ > + WRITE_ONCE(bts->state, BTS_STATE_ACTIVE); > + > intel_pmu_enable_bts(config); > > } Alexander, were you going to post a new version of this patch without the barrier confusion?
[toc] | [next] | [standalone]
| From | Alexander Shishkin <alexander.shishkin@linux.intel.com> |
|---|---|
| Date | 2016-08-29 16:50 +0200 |
| Subject | Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks |
| Message-ID | <sbw2S-62-27@gated-at.bofh.it> |
| In reply to | #1471868 |
Peter Zijlstra <peterz@infradead.org> writes: > On Wed, Aug 24, 2016 at 05:15:54PM +0300, Alexander Shishkin wrote: >> @@ -221,10 +245,13 @@ static void __bts_event_start(struct perf_event *event) >> >> /* >> * local barrier to make sure that ds configuration made it >> - * before we enable BTS >> + * before we enable BTS and bts::state goes ACTIVE >> */ >> wmb(); >> >> + /* INACTIVE/STOPPED -> ACTIVE */ >> + WRITE_ONCE(bts->state, BTS_STATE_ACTIVE); >> + >> intel_pmu_enable_bts(config); >> >> } > > Alexander, were you going to post a new version of this patch without > the barrier confusion? Yes, only the testcase exploded again over the weekend, looking at it again. Regards, -- Alex
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web