From: Thomas Gleixner <tglx@linutronix.de>
To: Bandan Das <bsd@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/apic: reset LDR in clear_local_APIC
Date: Mon, 19 Aug 2019 23:07:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908192259390.4008@nanos.tec.linutronix.de> (raw)
In-Reply-To: <jpga7ccl7la.fsf@linux.bootlegged.copy>
Bandan,
On Wed, 14 Aug 2019, Bandan Das wrote:
> On a 32 bit RHEL6 guest with greater than 8 cpus, the
> kdump kernel hangs when calibrating apic. This happens
> because when apic initializes bigsmp, it also initializes LDR
> even though it probably wouldn't be used.
'It probably wouldn't be used' is a not really a useful technical
statement.
Either it is used, then it needs to be handled. Or it is unused then why is
it written in the first place?
The bigsmp APIC uses physical destination mode because the logical flat
model only supports 8 APICs. So clearly bigsmp_init_apic_ldr() is bogus and
should be empty.
> When booting into kdump, KVM apic incorrectly reads the stale LDR
> values from the guest while building the logical destination map
> even for inactive vcpus. While KVM apic can be fixed to ignore apics
> that haven't been enabled, a simple guest only change can be to
> just clear out the LDR.
This does not make much sense either. What has KVM to do with logical
destination maps while booting the kdump kernel? The kdump kernel is not
going through the regular cold/warm boot process, so KVM does not even know
that the crashing kernel jumped into the kdump one.
What builds the logical destination maps and what has LDR and the KVM APIC
to do with that?
I'm not opposed to the change per se, but I'm not accepting change logs
which have the fairy tale smell.
Thanks,
tglx
next prev parent reply other threads:[~2019-08-19 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 4:00 Bandan Das
2019-08-19 21:07 ` Thomas Gleixner [this message]
2019-08-19 22:05 ` Bandan Das
2019-08-19 23:09 ` Thomas Gleixner
2019-08-21 15:47 ` Bandan Das
2019-08-21 18:22 ` Thomas Gleixner
2019-08-21 19:54 ` Bandan Das
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.21.1908192259390.4008@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=bsd@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®