public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
	"Charles (Chas) Williams" <ciwillia@brocade.com>,
	"M. Vefa Bicakci" <m.v.b@runbox.com>,
	Alok Kataria <akataria@vmware.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] x86/smpboot: Make logical package management more robust
Date: Thu, 8 Dec 2016 10:13:47 +0100	[thread overview]
Message-ID: <20161208091346.uzz3ix4hfpvx2bfu@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.20.1612081001230.3400@nanos>

On Thu, Dec 08, 2016 at 10:04:25AM +0100, Thomas Gleixner wrote:
> The logical package management has several issues:
> 
>  - The APIC ids provided by ACPI are not required to be the same as the
>    initial APIC id which can be retrieved by CPUID. The APIC ids provided
>    by ACPI are those which are written by the BIOS into the APIC. The
>    initial id is set by hardware and can not be changed. The hardware
>    provided ids contain the real hardware package information.
> 
>    Especially AMD sets the effective APIC id different from the hardware id
>    as they need to reserve space for the IOAPIC ids starting at id 0.
> 
>    As a consequence those machines trigger the currently active firmware
>    bug printouts in dmesg, These are obviously wrong.
> 
>  - Virtual machines have their own interesting way of enumerating APICs and
>    packages which are not reliably covered by the current implementation.
> 
> The sizing of the mapping array has been tweaked to be generously large to
> handle systems which provide a wrong core count when HT is disabled so the
> whole magic which checks for space in the physical hotplug case is not
> needed anymore.
> 
> Simplify the whole machinery and do the mapping when the CPU starts and the
> CPUID derived physical package information is available. This solves the
> observed problems on AMD machines and works for the virtualization issues
> as well.
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Already

Tested-by: Borislav Petkov <bp@suse.de>

Thanks!

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2016-12-08  9:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  9:04 [PATCH] x86/smpboot: Make logical package management more robust Thomas Gleixner
2016-12-08  9:13 ` Borislav Petkov [this message]
2016-12-08 11:03 ` Peter Zijlstra
2016-12-08 12:49   ` Thomas Gleixner
2016-12-08 13:04     ` Peter Zijlstra
2016-12-08 13:09       ` Thomas Gleixner
2016-12-09 22:06 ` Thomas Gleixner
2016-12-09 23:02   ` Boris Ostrovsky
2016-12-09 23:00     ` Thomas Gleixner
2016-12-10  3:37       ` Boris Ostrovsky
2016-12-10 19:03         ` Thomas Gleixner
2016-12-10  3:27     ` Boris Ostrovsky
2016-12-10 19:09       ` Thomas Gleixner
2016-12-10 19:13         ` Thomas Gleixner
2016-12-11  3:23           ` Boris Ostrovsky
2016-12-12 10:04             ` [PATCH v2] " Thomas Gleixner
2016-12-12 19:07               ` Boris Ostrovsky
2016-12-13 11:16               ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
2017-06-06 13:39               ` [PATCH v2] " Max Vozeler
2017-06-07  1:48                 ` Boris Ostrovsky
2017-06-07 12:19                   ` Max Vozeler

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=20161208091346.uzz3ix4hfpvx2bfu@pd.tnic \
    --to=bp@alien8.de \
    --cc=akataria@vmware.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ciwillia@brocade.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.v.b@runbox.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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