Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1590376
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 5/5] x86/intel_rdt: hotcpu updates for RDT |
| Date | 2017-03-01 16:10 +0100 |
| Message-ID | <tge37-4N8-1@gated-at.bofh.it> (permalink) |
| References | <tbWHv-8v1-5@gated-at.bofh.it> <tbWHw-8v1-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 17 Feb 2017, Vikas Shivappa wrote:
> For closid and rmid, change both the per cpu cache and PQR_MSR to be
> cleared only when offlining cpu at the respective handlers. The other
> places to clear them may not be required and is removed. This can be
> done at offlining so that the cache occupancy is not counted soon after
> the cpu goes down, rather than waiting to clear it during online cpu.
Yet another unstructured lump of blurb describing the WHAT and not the WHY.
> diff --git a/arch/x86/events/intel/cqm.c b/arch/x86/events/intel/cqm.c
> index 8c00dc0..681e32f 100644
> --- a/arch/x86/events/intel/cqm.c
> +++ b/arch/x86/events/intel/cqm.c
> @@ -1569,13 +1569,8 @@ static inline void cqm_pick_event_reader(int cpu)
>
> static int intel_cqm_cpu_starting(unsigned int cpu)
> {
> - struct intel_pqr_state *state = &per_cpu(pqr_state, cpu);
> struct cpuinfo_x86 *c = &cpu_data(cpu);
>
> - state->rmid = 0;
> - state->closid = 0;
> - state->rmid_usecnt = 0;
> -
> WARN_ON(c->x86_cache_max_rmid != cqm_max_rmid);
> WARN_ON(c->x86_cache_occ_scale != cqm_l3_scale);
>
> @@ -1585,12 +1580,17 @@ static int intel_cqm_cpu_starting(unsigned int cpu)
>
> static int intel_cqm_cpu_exit(unsigned int cpu)
> {
> + struct intel_pqr_state *state = &per_cpu(pqr_state, cpu);
Can be this_cpu_ptr() because the callback is guaranteed to run on the
outgoing CPU.
> int target;
>
> /* Is @cpu the current cqm reader for this package ? */
> if (!cpumask_test_and_clear_cpu(cpu, &cqm_cpumask))
> return 0;
So if the CPU is not the current cqm reader then the per cpu state of this
CPU is left stale. Great improvement.
> + state->rmid = 0;
> + state->rmid_usecnt = 0;
> + wrmsr(MSR_IA32_PQR_ASSOC, 0, state->closid);
What clears state->closid? And what guarantees that state->rmid is not
updated before the CPU has really gone away?
I doubt that this is correct, but if it is, then this lacks a big fat
comment explaining WHY.
Thanks,
tglx
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 0/5] x86/intel_rdt: Improvements/Fixes to RDT framework Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-02-17 20:50 +0100
[PATCH 1/5] x86/intel_rdt: Update control registers only when user really modifies it Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-02-17 20:50 +0100
Re: [PATCH 1/5] x86/intel_rdt: Update control registers only when user really modifies it Thomas Gleixner <tglx@linutronix.de> - 2017-03-01 16:10 +0100
Re: [PATCH 1/5] x86/intel_rdt: Update control registers only when user really modifies it Shivappa Vikas <vikas.shivappa@linux.intel.com> - 2017-03-10 01:00 +0100
[PATCH 5/5] x86/intel_rdt: hotcpu updates for RDT Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-02-17 20:50 +0100
Re: [PATCH 5/5] x86/intel_rdt: hotcpu updates for RDT Thomas Gleixner <tglx@linutronix.de> - 2017-03-01 16:10 +0100
[PATCH 3/5] x86/intel_rdt: Fail early on a resource with incorrect domains Vikas Shivappa <vikas.shivappa@linux.intel.com> - 2017-02-17 20:50 +0100
Re: [PATCH 3/5] x86/intel_rdt: Fail early on a resource with incorrect domains Thomas Gleixner <tglx@linutronix.de> - 2017-03-01 16:40 +0100
csiph-web