From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pu Wen <puwen@hygon.cn>, Thomas Gleixner <tglx@linutronix.de>,
Tom Lendacky <thomas.lendacky@amd.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] x86/urgent for 5.3-rc5
Date: Sun, 25 Aug 2019 21:32:18 +0200 [thread overview]
Message-ID: <20190825193218.GD20639@zn.tnic> (raw)
In-Reply-To: <CAHk-=wjhyg-MndXHZGRD+ZKMK1UrcghyLH32rqQA=YmcxV7Z0Q@mail.gmail.com>
On Sun, Aug 25, 2019 at 11:38:50AM -0700, Linus Torvalds wrote:
> On Sun, Aug 25, 2019 at 11:29 AM Borislav Petkov <bp@suse.de> wrote:
> >
> > My lazy, sticky Sunday brain could come up only with this:
>
> Looks reasonable, except I think this only runs at boot, right?
>
> I _think_ the boot CPU is magical during suspend/resume, and doesn't
> do the full CPU bringup.
>
> Although I guess this would still report it for the other CPU's? I
> didn't check if this gets done during CPU bringup of secondary CPU's.
So after adding a dump_stack() at the beginning of this function (yap,
I'm lazy) I see during boot:
[ 0.230044] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.3.0-rc5+ #9
[ 0.230759] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1 04/01/2014
[ 0.231690] Call Trace:
[ 0.232097] dump_stack+0x46/0x60
[ 0.232496] x86_init_rdrand+0xf/0xa1
[ 0.232496] identify_cpu+0x352/0x540
[ 0.232496] identify_boot_cpu+0xc/0x8f
[ 0.232496] check_bugs+0x28/0x8e4
[ 0.232496] ? __get_locked_pte+0x13e/0x1f0
[ 0.232496] start_kernel+0x4ae/0x4ca
and also on all the remaining 15 CPUs of the guest. Then, suspending to
RAM and resuming right afterwards says:
[ 51.620230] Disabling non-boot CPUs ...
[ 51.622745] smpboot: CPU 1 is now offline
[ 51.627264] smpboot: CPU 2 is now offline
[ 51.630581] smpboot: CPU 3 is now offline
[ 51.634533] smpboot: CPU 4 is now offline
[ 51.638715] smpboot: CPU 5 is now offline
[ 51.642590] smpboot: CPU 6 is now offline
[ 51.645890] smpboot: CPU 7 is now offline
[ 51.649076] smpboot: CPU 8 is now offline
[ 51.652362] smpboot: CPU 9 is now offline
[ 51.655647] smpboot: CPU 10 is now offline
[ 51.659061] smpboot: CPU 11 is now offline
[ 51.662772] smpboot: CPU 12 is now offline
[ 51.665863] smpboot: CPU 13 is now offline
[ 51.667980] smpboot: CPU 14 is now offline
[ 51.671644] smpboot: CPU 15 is now offline
[ 51.675640] ACPI: Low-level resume complete
[ 51.675640] PM: Restoring platform NVS memory
[ 51.675640] Enabling non-boot CPUs ...
[ 51.728674] x86: Booting SMP configuration:
[ 51.729015] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 51.625362] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.3.0-rc5+ #9
[ 51.625362] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1 04/01/2014
[ 51.625362] Call Trace:
[ 51.625362] dump_stack+0x46/0x60
[ 51.625362] x86_init_rdrand+0xf/0xa1
[ 51.625362] identify_cpu+0x352/0x540
[ 51.625362] identify_secondary_cpu+0x13/0x80
[ 51.625362] smp_store_cpu_info+0x45/0x50
[ 51.625362] start_secondary+0x4f/0x180
[ 51.625362] secondary_startup_64+0xa4/0xb0
[ 51.740833] CPU1 is up
...
and the remaining 14(!). Yes, this doesn't run on the BSP during resume.
I think the better thing to do would be to stick this in a CPUHP
notifier...
Btw:
Subject: Undelivered Mail Returned to Sender
...
<puwen@hygon.cn>: Host or domain name not found. Name service error for
name=spam01.hygon.cn type=AAAA: Host found but no data record of requested
type
hygon.cn domain doesn't even resolve from here. Oh boy.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 247165, AG München
next prev parent reply other threads:[~2019-08-25 19:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 9:43 [GIT pull] irq/urgent for 5.3-rc5 Thomas Gleixner
2019-08-25 9:43 ` [GIT pull] perf/urgent " Thomas Gleixner
2019-08-25 17:40 ` pr-tracker-bot
2019-08-25 9:43 ` [GIT pull] timers/urgent " Thomas Gleixner
2019-08-25 17:40 ` pr-tracker-bot
2019-08-25 9:43 ` [GIT pull] sched/urgent " Thomas Gleixner
2019-08-25 17:40 ` pr-tracker-bot
2019-08-25 9:43 ` [GIT pull] x86/urgent " Thomas Gleixner
2019-08-25 17:18 ` Linus Torvalds
2019-08-25 17:30 ` Borislav Petkov
2019-08-25 17:37 ` Linus Torvalds
2019-08-25 18:29 ` Borislav Petkov
2019-08-25 18:38 ` Linus Torvalds
2019-08-25 19:32 ` Borislav Petkov [this message]
2019-08-25 19:35 ` Linus Torvalds
2019-08-25 19:49 ` Borislav Petkov
2019-08-25 19:59 ` Linus Torvalds
2019-08-25 20:17 ` Borislav Petkov
2019-08-26 12:53 ` Borislav Petkov
2019-08-27 16:55 ` Linus Torvalds
2019-08-27 17:39 ` Borislav Petkov
2019-08-27 17:46 ` Linus Torvalds
2019-08-27 17:59 ` Borislav Petkov
2019-08-28 15:20 ` David Sterba
2019-08-28 15:53 ` David Sterba
2019-10-02 19:09 ` [tip: x86/cpu] x86/rdrand: Sanity-check RDRAND output tip-bot2 for Borislav Petkov
2019-08-25 17:40 ` [GIT pull] x86/urgent for 5.3-rc5 pr-tracker-bot
2019-08-25 17:40 ` [GIT pull] irq/urgent " pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-08-18 11:34 [GIT pull] efi/urgent " Thomas Gleixner
2019-08-18 11:34 ` [GIT pull] x86/urgent " Thomas Gleixner
2019-08-18 16:55 ` pr-tracker-bot
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=20190825193218.GD20639@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.org \
--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