linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jinpu Wang <jinpu.wang@profitbricks.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable <stable@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	konrad.wilk@oracle.com, Peter Zijlstra <peterz@infradead.org>,
	David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [BUG]smt sysfs dir missing on 4.4.148 and 4.14.63
Date: Mon, 20 Aug 2018 16:52:41 +0200	[thread overview]
Message-ID: <CAMGffEnrFu3ve6CbqNX9cRKz_MwH-Ch_QU7zGbYiQ7Hpnv6Yrw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1808201646440.1551@nanos.tec.linutronix.de>

On Mon, Aug 20, 2018 at 4:47 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Mon, 20 Aug 2018, Jinpu Wang wrote:
> > On Mon, Aug 20, 2018 at 3:02 PM Thomas Gleixner <tglx@linutronix.de> wrote:
> > > That works, but we might as well force 'select HOTPLUG_CPU if SMP' so the
> > > L1TF mitigations are functional. Sigh....
> > >
> > > Thanks,
> > >
> > >         tglx
> > right, sth like?
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index b0312f8..5852948 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -188,7 +188,8 @@ config X86
> >         select HAVE_SYSCALL_TRACEPOINTS
> >         select HAVE_UNSTABLE_SCHED_CLOCK
> >         select HAVE_USER_RETURN_NOTIFIER
> > -       select HOTPLUG_SMT                      if SMP
> > +       select HOTPLUG_CPU                      if SMP
> > +       select HOTPLUG_SMT                      if SMP && HOTPLUG_CPU
>
> The && HOTPLUG is pretty pointless now.
Hmm, so this way?
+       select HOTPLUG_CPU                      if SMP
+       select HOTPLUG_SMT                      if HOTPLUG_CPU

thanks!
-- 
Jack Wang
Linux Kernel Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Tel:       +49 30 577 008  042
Fax:      +49 30 577 008 299
Email:    jinpu.wang@profitbricks.com
URL:      https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph Steffens

      reply	other threads:[~2018-08-20 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMGffEnzVo5VVSVBjCOBMhcoV1qXf0XXqJqr3C01xQn-aUiZFQ@mail.gmail.com>
     [not found] ` <20180816155126.GA18296@kroah.com>
2018-08-16 16:28   ` [BUG]smt sysfs dir missing on 4.4.148 and 4.14.63 Jinpu Wang
2018-08-16 16:39     ` Greg Kroah-Hartman
     [not found]       ` <CAMGffEk2FqRn0av7T-aF-TKvRAKeinm96NYjJju_T4CmUrYPkQ@mail.gmail.com>
2018-08-17 12:39         ` Jinpu Wang
2018-08-17 17:01           ` Greg Kroah-Hartman
2018-08-18 12:50             ` Thomas Gleixner
2018-08-20  8:05               ` Jinpu Wang
2018-08-20 13:02                 ` Thomas Gleixner
2018-08-20 13:20                   ` Jinpu Wang
2018-08-20 14:47                     ` Thomas Gleixner
2018-08-20 14:52                       ` Jinpu Wang [this message]

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=CAMGffEnrFu3ve6CbqNX9cRKz_MwH-Ch_QU7zGbYiQ7Hpnv6Yrw@mail.gmail.com \
    --to=jinpu.wang@profitbricks.com \
    --cc=dwmw@amazon.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).