From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <jbeulich@suse.com>,
Teddy Astie <teddy.astie@vates.tech>
Subject: Re: [PATCH] xen/kexec: Wire up kexec hypercalls for PVH hardware domains
Date: Tue, 21 Jul 2026 11:41:10 +0200 [thread overview]
Message-ID: <al8-tljQQFOZ_s9M@macbook.local> (raw)
In-Reply-To: <20260720185825.2204624-1-andrew.cooper3@citrix.com>
On Mon, Jul 20, 2026 at 07:58:25PM +0100, Andrew Cooper wrote:
> Nothing in do_kexec_op() is PV specific. Plumb in PVH guests too.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Jan Beulich <jbeulich@suse.com>
> CC: Roger Pau Monné <roger.pau@citrix.com>
> CC: Teddy Astie <teddy.astie@vates.tech>
>
> kexec-tools in userspace still has a PV check needing dropping before kexec is
> generally usable for PVH dom0's, but the Xen side should be all fine.
Yeah, I took a look into that but didn't attempt to remove the check.
However, a PVH dom0 would/could have two ways do to kexec: it could
do a guest-only kexec (like other HVM guests), or a full host kexec
(like PV dom0). Do we need a switch in kexec tools to signal whether
we want to perform a host vs guest kexec? Or should we just assume
that a PVH dom0 will exclusively do host kexec?
Thanks, Roger.
prev parent reply other threads:[~2026-07-21 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 18:58 [PATCH] xen/kexec: Wire up kexec hypercalls for PVH hardware domains Andrew Cooper
2026-07-21 7:42 ` Jan Beulich
2026-07-21 9:41 ` Roger Pau Monné [this message]
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=al8-tljQQFOZ_s9M@macbook.local \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=teddy.astie@vates.tech \
--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