public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Joe Mario <jmario@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: cpu/hotplug: broken sibling thread hotplug
Date: Mon, 28 Jan 2019 11:13:04 +0100	[thread overview]
Message-ID: <20190128111304.0df37a8a@redhat.com> (raw)
In-Reply-To: <20190125170203.2o2l27d2sytw44nl@treble>

On Fri, 25 Jan 2019 11:02:03 -0600
Josh Poimboeuf <jpoimboe@redhat.com> wrote:

> On Fri, Jan 25, 2019 at 10:36:57AM -0600, Josh Poimboeuf wrote:
> > How about this patch?  It's just a revert of 73d5e2b47264 and
> > bc2d8d262cba, plus the 1-line vmx_vm_init() change.  If it looks ok to
> > you, I can clean it up and submit an official version.  
> 
> This one actually compiles...

Looks good to me,
(one small question below)

 
[...]
>  static inline bool cpu_smt_allowed(unsigned int cpu)
>  {
> -	if (topology_is_primary_thread(cpu))
> +	if (cpu_smt_control == CPU_SMT_ENABLED)
>  		return true;
>  
> -	/*
> -	 * If the CPU is not a 'primary' thread and the booted_once bit is
> -	 * set then the processor has SMT support. Store this information
> -	 * for the late check of SMT support in cpu_smt_check_topology().
> -	 */
> -	if (per_cpu(cpuhp_state, cpu).booted_once)
> -		cpu_smt_available = true;
> -
> -	if (cpu_smt_control == CPU_SMT_ENABLED)
> +	if (topology_is_primary_thread(cpu))
>  		return true;
why did you swap cpu_smt_control and topology_is_primary_thread checks?

>  
>  	/*


  reply	other threads:[~2019-01-28 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 15:57 cpu/hotplug: broken sibling thread hotplug Igor Mammedov
2019-01-25 16:36 ` Josh Poimboeuf
2019-01-25 17:02   ` Josh Poimboeuf
2019-01-28 10:13     ` Igor Mammedov [this message]
2019-01-28 12:52       ` Josh Poimboeuf
2019-01-28 13:35         ` Igor Mammedov

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=20190128111304.0df37a8a@redhat.com \
    --to=imammedo@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=jmario@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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