From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [RFC] xen/pvh: detect PVH after kexec
Date: Tue, 21 Mar 2017 10:21:52 +0100 [thread overview]
Message-ID: <87efxr9e8f.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <5ef043a0-2382-79b2-196a-af214fc68fd4@oracle.com> (Boris Ostrovsky's message of "Mon, 20 Mar 2017 16:21:18 -0400")
Boris Ostrovsky <boris.ostrovsky@oracle.com> writes:
> On 03/20/2017 02:20 PM, Vitaly Kuznetsov wrote:
>> PVH guests after kexec boot like normal HVM guests and we're not entering
>> xen_prepare_pvh()
>
> Is it not? Aren't we going via xen_hvm_shutdown() and then
> SHUTDOWN_soft_reset which would restart at the same entry point as
> regular boot?
No, we're not doing regular boot: from outside of the guest we don't
really know where the new kernel is placed (as guest does it on its
own). We do soft reset to clean things up and then guest jumps to the
new kernel starting point by itself.
We could (in theory, didn't try) make it jump to the PVH starting point
but we'll have to at least prepare the right boot params for
init_pvh_bootparams and this looks like additional
complication. PVHVM-style startup suits us well but we still need to be
PVH-aware.
[snip].
--
Vitaly
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-21 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 18:20 [RFC] xen/pvh: detect PVH after kexec Vitaly Kuznetsov
2017-03-20 20:21 ` Boris Ostrovsky
2017-03-21 9:21 ` Vitaly Kuznetsov [this message]
2017-03-21 10:01 ` Roger Pau Monne
2017-03-21 10:07 ` Roger Pau Monne
2017-03-21 10:07 ` Jan Beulich
2017-03-21 10:21 ` Roger Pau Monne
2017-03-21 10:42 ` Jan Beulich
2017-03-21 10:59 ` Roger Pau Monne
2017-03-21 11:00 ` Andrew Cooper
2017-03-21 11:53 ` Vitaly Kuznetsov
2017-03-21 12:13 ` Roger Pau Monne
2017-03-21 14:05 ` Boris Ostrovsky
2017-03-21 14:16 ` Roger Pau Monne
2017-03-21 15:01 ` Boris Ostrovsky
2017-03-21 14:35 ` Vitaly Kuznetsov
2017-03-21 14:44 ` Vitaly Kuznetsov
2017-03-21 15:14 ` Boris Ostrovsky
2017-03-21 17:10 ` Vitaly Kuznetsov
2017-03-21 17:28 ` Roger Pau Monne
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=87efxr9e8f.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.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 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).