From: Thomas Gleixner <tglx@linutronix.de>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: "H. Peter Anvin" <h.peter.anvin@intel.com>,
Ingo Molnar <mingo@elte.hu>, Tony Luck <tony.luck@intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
Sai Prakhya <sai.praneeth.prakhya@intel.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH 3/3] x86/intel_rdt: Update closid in PQR_ASSOC registers in synchronous mode when changing "cpus"
Date: Tue, 15 Nov 2016 14:43:52 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1611151435550.3602@nanos> (raw)
In-Reply-To: <1478912558-55514-3-git-send-email-fenghua.yu@intel.com>
On Fri, 11 Nov 2016, Fenghua Yu wrote:
> x86/intel_rdt: Update closid in PQR_ASSOC registers in synchronous mode when changing "cpus"
Subject lines are supposed to be short and precise.
> When "cpus" is changed in a rdtgroup, the current code doesn't update
> PQR_ASSOC registers with new closid in the cpus write operation.
> The PQR_ASSOC registers are updated asynchronously later when new
> processes are scheduled in on the CPUs.
>
> A process may run on a CPU for long time without being switched to
> another process, e.g. high performance computing or real time cases.
> Then closid in the PQR_ASSOC register on the CPU is not updated for
> long time until a new process is switched in.
Can you please be a bit more careful about your changelogs? The above is
reads like a fairy tale.
> This patch updates closid in PQR_ASSOC synchronously when writing
'This patch' - Grrr! I told you more than once that 'This patch' is
crap. We all know that this is a PATCH. See
Documentation/SubmittingPatches.
> +/*
> + * MSR_IA32_PQR_ASSOC is scoped per logical CPU, so all updates
> + * are always in thread context.
> + */
> +static void rdt_update_pqr_assoc_closid(void *v)
> +{
> + struct intel_pqr_state *state = this_cpu_ptr(&pqr_state);
> +
> + state->closid = *(int *)v;
> + wrmsr(MSR_IA32_PQR_ASSOC, state->rmid, state->closid);
> +}
> +
> +static void rdt_update_pqr_assoc(const struct cpumask *cpu_mask, int closid)
> +{
> + int cpu = get_cpu();
> +
> + /* Update PQR_ASSOC MSR on this cpu if it's in cpu_mask. */
> + if (cpumask_test_cpu(cpu, cpu_mask))
> + rdt_update_pqr_assoc_closid(&closid);
> + /* Update PQR_ASSOC MSR on the rest of cpus. */
> + smp_call_function_many(cpu_mask, rdt_update_pqr_assoc_closid,
> + &closid, 1);
> + put_cpu();
> +}
> static void rmdir_all_sub(void)
> @@ -809,13 +828,9 @@ static void rmdir_all_sub(void)
> t->closid = 0;
> read_unlock(&tasklist_lock);
>
> - get_cpu();
> - /* Reset PQR_ASSOC MSR on this cpu. */
> - rdt_reset_pqr_assoc_closid(NULL);
> - /* Reset PQR_ASSOC MSR on the rest of cpus. */
> - smp_call_function_many(cpu_online_mask, rdt_reset_pqr_assoc_closid,
> - NULL, 1);
> - put_cpu();
> + /* Reset PQR_ASSOC MSR on all online cpus */
> + rdt_update_pqr_assoc(cpu_online_mask, 0);
cpu_online_mask is not protected against changing before you hit the
get_cpu() in rdt_update_pqr_assoc().
Thanks,
tglx
next prev parent reply other threads:[~2016-11-15 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 1:02 [PATCH 1/3] x86/intel_rdt: Fix kernfs_to_rdtgroup to know about "info/*" directories Fenghua Yu
2016-11-12 1:02 ` [PATCH 2/3] x86/intel_rdt: Return state to default on umount Fenghua Yu
2016-11-15 13:35 ` Thomas Gleixner
2016-11-15 17:28 ` Thomas Gleixner
2016-11-15 17:44 ` [tip:x86/cache] x86/intel_rdt: Reset per cpu closids on unmount tip-bot for Fenghua Yu
2016-11-12 1:02 ` [PATCH 3/3] x86/intel_rdt: Update closid in PQR_ASSOC registers in synchronous mode when changing "cpus" Fenghua Yu
2016-11-15 13:43 ` Thomas Gleixner [this message]
2016-11-15 14:00 ` Thomas Gleixner
2016-11-15 16:40 ` Thomas Gleixner
2016-11-15 17:44 ` [tip:x86/cache] x86/intel_rdt: Update percpu closid immeditately on CPUs affected by changee tip-bot for Fenghua Yu
2016-11-15 17:42 ` [tip:x86/cache] x86/intel_rdt: Protect info directory from removal tip-bot for Fenghua Yu
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=alpine.DEB.2.20.1611151435550.3602@nanos \
--to=tglx@linutronix.de \
--cc=fenghua.yu@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ravi.v.shankar@intel.com \
--cc=sai.praneeth.prakhya@intel.com \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@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