From: Thomas Gleixner <tglx@linutronix.de>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: rjw@rjwysocki.net, mingo@redhat.com, bp@suse.de, x86@kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, peterz@infradead.org,
tim.c.chen@linux.intel.com, jolsa@redhat.com
Subject: Re: [PATCH v5 5/9] x86/sysctl: Add sysctl for ITMT scheduling feature
Date: Wed, 5 Oct 2016 16:35:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610051624590.8953@nanos> (raw)
In-Reply-To: <1475322326-160112-6-git-send-email-srinivas.pandruvada@linux.intel.com>
On Sat, 1 Oct 2016, Srinivas Pandruvada wrote:
> +static int sched_itmt_update_handler(struct ctl_table *table, int write,
> + void __user *buffer, size_t *lenp, loff_t *ppos)
> +{
> + int ret;
> + unsigned int old_sysctl;
> +
> + mutex_lock(&itmt_update_mutex);
> +
> + if (!sched_itmt_capable) {
> + mutex_unlock(&itmt_update_mutex);
> + return 0;
This should return a proper error code.
> void sched_set_itmt_support(bool itmt_supported)
> {
> mutex_lock(&itmt_update_mutex);
>
> - if (itmt_supported != sched_itmt_capable)
> - sched_itmt_capable = itmt_supported;
> + if (itmt_supported == sched_itmt_capable) {
> + mutex_unlock(&itmt_update_mutex);
> + return;
> + }
> + sched_itmt_capable = itmt_supported;
> +
> + if (itmt_supported) {
> + itmt_sysctl_header =
> + register_sysctl_table(itmt_root_table);
> + if (!itmt_sysctl_header) {
> + mutex_unlock(&itmt_update_mutex);
> + return;
So you now have a state of capable which cannot be enabled. Whats the
point?
> + }
> + /*
> + * ITMT capability automatically enables ITMT
> + * scheduling for small systems (single node).
> + */
> + if (topology_num_packages() == 1)
> + sysctl_sched_itmt_enabled = 1;
> + } else {
> + if (itmt_sysctl_header)
> + unregister_sysctl_table(itmt_sysctl_header);
> + }
> +
> + if (sysctl_sched_itmt_enabled) {
> + /* disable sched_itmt if we are no longer ITMT capable */
> + if (!itmt_supported)
How do you get here if itmt is not supported?
> + sysctl_sched_itmt_enabled = 0;
> + x86_topology_update = true;
> + rebuild_sched_domains();
> + }
>
> mutex_unlock(&itmt_update_mutex);
Thanks,
tglx
next prev parent reply other threads:[~2016-10-05 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 11:45 [PATCH v5 0/9] Support Intel® Turbo Boost Max Technology 3.0 Srinivas Pandruvada
2016-10-01 11:45 ` [PATCH v5 1/9] sched: Extend scheduler's asym packing Srinivas Pandruvada
2016-10-01 16:38 ` Nilay Vaish
2016-10-03 16:49 ` Tim Chen
2016-10-01 11:45 ` [PATCH v5 2/9] x86/topology: Provide topology_num_packages() Srinivas Pandruvada
2016-10-01 11:45 ` [PATCH v5 3/9] x86/topology: Define x86's arch_update_cpu_topology Srinivas Pandruvada
2016-10-01 11:45 ` [PATCH v5 4/9] x86: Enable Intel Turbo Boost Max Technology 3.0 Srinivas Pandruvada
2016-10-05 14:23 ` Thomas Gleixner
2016-10-05 16:05 ` Tim Chen
2016-10-01 11:45 ` [PATCH v5 5/9] x86/sysctl: Add sysctl for ITMT scheduling feature Srinivas Pandruvada
2016-10-05 14:35 ` Thomas Gleixner [this message]
2016-10-05 16:24 ` Tim Chen
2016-10-06 11:13 ` Thomas Gleixner
2016-10-06 17:37 ` Tim Chen
2016-10-12 16:50 ` Tim Chen
2016-10-01 11:45 ` [PATCH v5 6/9] x86/sched: Add SD_ASYM_PACKING flags to x86 ITMT CPU Srinivas Pandruvada
2016-10-01 11:45 ` [PATCH v5 7/9] acpi: bus: Enable HWP CPPC objects Srinivas Pandruvada
2016-10-01 11:45 ` [PATCH v5 8/9] acpi: bus: Set _OSC for diverse core support Srinivas Pandruvada
2016-10-01 11:45 ` [PATCH v5 9/9] cpufreq: intel_pstate: Use CPPC to get max performance Srinivas Pandruvada
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.1610051624590.8953@nanos \
--to=tglx@linutronix.de \
--cc=bp@suse.de \
--cc=jolsa@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tim.c.chen@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