From: Paolo Bonzini <pbonzini@redhat.com>
To: Bruce Rogers <brogers@suse.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Kiszka <jan.kiszka@web.de>
Cc: namit@cs.technion.ac.il
Subject: Re: [PATCH 2/2] KVM: x86: allow BSP to handle INIT IPIs like APs do
Date: Mon, 8 Feb 2016 18:44:09 +0100 [thread overview]
Message-ID: <56B8D3E9.1020400@redhat.com> (raw)
In-Reply-To: <56B86D9B02000048001251EF@prv-mh.provo.novell.com>
On 08/02/2016 18:27, Bruce Rogers wrote:
> I had read that, but I though this was speaking from the perspective of the
> SMP aware BIOS code only.
It says "logical processor", so I cannot really see how it can be
interpreted that way. The BSP jumps to 0xFFFFFFF0, the APs go into
wait-for-SIPI state.
> I certainly could be wrong about my above interpretation, but with these
> changes I'm proposing, things work well for the test case of manually onlining
> the BSP after the crash kernel has been started (via kexec -e on a AP processor
> with maxcpus=1 on the crash kernel command line). From looking through the
> kernel git history it appears this sequence of events was explicitly supported
> quite a while ago, and we've got a customer who uses this for fast recovery from
> a guest kernel crash.
You need to comment on the output of trace-cmd for KVM events, or
provide a full reproducer, or at the very least point me to the kernel
code that you're referring to. Otherwise I just cannot understand what
you're talking about; sorry. :(
Paolo
next prev parent reply other threads:[~2016-02-08 17:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 22:51 [PATCH 1/2] KVM: x86: fix ordering of cr0 initialization code in vmx_cpu_reset Bruce Rogers
2016-02-03 22:51 ` [PATCH 2/2] KVM: x86: allow BSP to handle INIT IPIs like APs do Bruce Rogers
2016-02-08 15:12 ` Paolo Bonzini
2016-02-08 15:22 ` Jan Kiszka
2016-02-08 16:33 ` Bruce Rogers
2016-02-08 16:40 ` Paolo Bonzini
2016-02-08 17:27 ` Bruce Rogers
2016-02-08 17:44 ` Paolo Bonzini [this message]
2016-02-08 17:38 ` Bruce Rogers
2016-02-08 17:53 ` Jan Kiszka
2016-02-10 17:24 ` Bruce Rogers
2016-02-03 23:18 ` [PATCH 1/2] KVM: x86: fix ordering of cr0 initialization code in vmx_cpu_reset Nadav Amit
2016-02-03 23:38 ` Bruce Rogers
2016-04-22 18:55 ` Bruce Rogers
2016-02-08 15:09 ` Paolo Bonzini
2016-02-08 16:29 ` Bruce Rogers
2016-02-08 16:43 ` Paolo Bonzini
2016-04-27 2:54 ` Wanpeng Li
2016-04-28 22:18 ` Bruce Rogers
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=56B8D3E9.1020400@redhat.com \
--to=pbonzini@redhat.com \
--cc=brogers@suse.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@cs.technion.ac.il \
/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).