From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, KeirFraser <keir@xen.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Eddie Dong <eddie.dong@intel.com>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Jun Nakajima <jun.nakajima@intel.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v3] xen: fix reboot/shutdown with running HVM guests
Date: Thu, 5 Jun 2014 17:16:28 +0100 [thread overview]
Message-ID: <539097DC.4060007@citrix.com> (raw)
In-Reply-To: <5390B0A6020000780001861F@mail.emea.novell.com>
On 05/06/14 17:02, Jan Beulich wrote:
>>>> On 05.06.14 at 17:46, <andrew.cooper3@citrix.com> wrote:
>> On 05/06/14 16:01, Roger Pau Monne wrote:
>>> If there's a guest using VMX/SVM when the hypervisor shuts down, it
>>> can lead to the following crash due to VMX/SVM functions being called
>>> after hvm_cpu_down has been called. In order to prevent that, check in
>>> {svm/vmx}_ctxt_switch_from that the cpu virtualization extensions are
>>> still enabled.
>> I feel that this is still trying to fix the problem from the wrong end.
>> It is incorrect to be in a context switch at the point identified in the
>> stack trace.
>>
>> How about having the hvm_cpu_down functions look at current, and
>> optionally run sync_exec_state() ?
> I considered this too before suggesting the other alternative,
> but why would getting into the context switch path this way
> be any better than through map_domain_page()?
>
> Jan
>
It is a more controlled point on all shutdown/crash paths, but still not
perfect.
What we probably need on all shutdown paths is an early step of
"reschedule the idle vcpu back on all pcpus". This won't fix the issue
for crash paths however.
~Andrew
next prev parent reply other threads:[~2014-06-05 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 15:01 [PATCH v3] xen: fix reboot/shutdown with running HVM guests Roger Pau Monne
2014-06-05 15:42 ` Aravind Gopalakrishnan
2014-06-05 15:46 ` Andrew Cooper
2014-06-05 16:02 ` Jan Beulich
2014-06-05 16:16 ` Andrew Cooper [this message]
2014-06-05 19:11 ` Tian, Kevin
2014-06-05 19:12 ` Tian, Kevin
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=539097DC.4060007@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.