From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: xen-devel@lists.xenproject.org, x86@kernel.org,
David Vrabel <david.vrabel@citrix.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/pvhvm: add soft reset on kexec/kdump support
Date: Fri, 25 Sep 2015 11:54:05 -0400 [thread overview]
Message-ID: <56056E1D.80307@oracle.com> (raw)
In-Reply-To: <20150925135937.GJ20966@l.oracle.com>
On 09/25/2015 09:59 AM, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 25, 2015 at 11:59:52AM +0200, Vitaly Kuznetsov wrote:
>> Currently there is a number of issues preventing PVHVM Xen guests from
>> doing successful kexec/kdump:
>> - Bound event channels.
>> - Registered vcpu_info.
>> - PIRQ/emuirq mappings.
>> - shared_info frame after XENMAPSPACE_shared_info operation.
>> - Active grant mappings.
>> Basically, newly booted kernel stumbles upon already set up Xen interfaces
>> and there is no way to reestablish them. In Xen-4.7 a new feature called
>> 'soft reset' is coming. A guest performing kexec/kdump operation is
>> supposed to call SCHEDOP_shutdown hypercall with SHUTDOWN_soft_reset reason
>> before jumping to new kernel. Hypervisor (with some help from toolstack)
>> will do full domain cleanup (but keeping its memory and vCPU contexts
>> intact) returning the guest to the state it had when it was first booted
>> and thus allowing it to start over.
>>
>> Doing SHUTDOWN_soft_reset on Xen hypervisors which don't support it is
>> probably OK as by default all unknown shutdown reasons cause domain destroy
>> with a message in toolstack log:
>> 'Unknown shutdown reason code 5. Destroying domain.'
>> which gives a clue to what the problem is and eliminates false
>> expectations.
>>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> with s/pvhvm/hvm/
>
> to match with the rest of the file.
>
> Thanks.
>>
>> +#ifdef CONFIG_KEXEC_CORE
>> +static void xen_pvhvm_kexec_shutdown(void)
>> +{
>> + native_machine_shutdown();
>> + if (kexec_in_progress)
>> + xen_reboot(SHUTDOWN_soft_reset);
>> +}
This routine is not kexec-specific so "kexec_" should be dropped from
the name.
Also, I am not sure I see how this new op will be used in the hypervisor
--- currently AFAICS it is only processed under is_hardware_domain().
Are there other patches that will support HVM guests?
-boris
next prev parent reply other threads:[~2015-09-25 15:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 9:59 [PATCH] xen/pvhvm: add soft reset on kexec/kdump support Vitaly Kuznetsov
2015-09-25 13:59 ` Konrad Rzeszutek Wilk
2015-09-25 15:54 ` Boris Ostrovsky
2015-09-25 15:54 ` Boris Ostrovsky [this message]
2015-09-25 16:07 ` Vitaly Kuznetsov
2015-09-25 16:07 ` Vitaly Kuznetsov
2015-09-25 17:17 ` Boris Ostrovsky
2015-09-25 17:17 ` Boris Ostrovsky
2015-09-25 19:01 ` Konrad Rzeszutek Wilk
2015-09-25 19:19 ` Boris Ostrovsky
2015-09-25 19:35 ` Konrad Rzeszutek Wilk
2015-09-25 19:35 ` Konrad Rzeszutek Wilk
2015-09-25 21:00 ` Boris Ostrovsky
2015-09-29 11:39 ` Vitaly Kuznetsov
2015-09-29 13:08 ` Boris Ostrovsky
2015-09-29 13:08 ` Boris Ostrovsky
2015-09-29 11:39 ` Vitaly Kuznetsov
2015-09-25 21:00 ` Boris Ostrovsky
2015-09-25 19:19 ` Boris Ostrovsky
2015-09-25 19:01 ` Konrad Rzeszutek Wilk
2015-09-25 13:59 ` Konrad Rzeszutek Wilk
2015-09-28 14:16 ` [Xen-devel] " David Vrabel
2015-09-28 14:16 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2015-09-25 9:59 Vitaly Kuznetsov
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=56056E1D.80307@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
--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.