From: Simon Horman <horms@verge.net.au>
To: kexec@lists.infradead.org
Subject: [PATCH v2] kexec-xen: Allow xen_kexec_exec() to return in case of Live Update
Date: Wed, 23 Mar 2022 15:59:25 +0100 [thread overview]
Message-ID: <Yjs1zcRAOWD5gwcP@vergenet.net> (raw)
In-Reply-To: <20220323144418.1658-1-raphning@gmail.com>
On Wed, Mar 23, 2022 at 02:44:18PM +0000, Raphael Ning wrote:
> From: Raphael Ning <raphning@amazon.com>
>
> Currently, my_exec() does not expect the Xen KEXEC_CMD_kexec hypercall
> to return on success, because it assumes that the hypercall always
> triggers an immediate reboot. However, for Live Update, the hypercall
> merely schedules the kexec operation and returns; the actual reboot
> happens asynchronously. [1]
>
> Therefore, rework the Xen code path of my_exec() such that it does not
> treat a successfully processed Live Update request as an error. Also,
> rephrase the comment above the function to remove ambiguity.
>
> [1] https://lists.xen.org/archives/html/xen-devel/2021-05/msg00286.html
>
> Signed-off-by: Raphael Ning <raphning@amazon.com>
Thanks, applied.
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Raphael Ning <raphning@gmail.com>
Cc: kexec@lists.infradead.org, Julien Grall <julien@xen.org>,
xen-devel@lists.xenproject.org,
Raphael Ning <raphning@amazon.com>
Subject: Re: [PATCH v2] kexec-xen: Allow xen_kexec_exec() to return in case of Live Update
Date: Wed, 23 Mar 2022 15:59:25 +0100 [thread overview]
Message-ID: <Yjs1zcRAOWD5gwcP@vergenet.net> (raw)
In-Reply-To: <20220323144418.1658-1-raphning@gmail.com>
On Wed, Mar 23, 2022 at 02:44:18PM +0000, Raphael Ning wrote:
> From: Raphael Ning <raphning@amazon.com>
>
> Currently, my_exec() does not expect the Xen KEXEC_CMD_kexec hypercall
> to return on success, because it assumes that the hypercall always
> triggers an immediate reboot. However, for Live Update, the hypercall
> merely schedules the kexec operation and returns; the actual reboot
> happens asynchronously. [1]
>
> Therefore, rework the Xen code path of my_exec() such that it does not
> treat a successfully processed Live Update request as an error. Also,
> rephrase the comment above the function to remove ambiguity.
>
> [1] https://lists.xen.org/archives/html/xen-devel/2021-05/msg00286.html
>
> Signed-off-by: Raphael Ning <raphning@amazon.com>
Thanks, applied.
next prev parent reply other threads:[~2022-03-23 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 14:44 [PATCH v2] kexec-xen: Allow xen_kexec_exec() to return in case of Live Update Raphael Ning
2022-03-23 14:44 ` Raphael Ning
2022-03-23 14:59 ` Simon Horman [this message]
2022-03-23 14:59 ` Simon Horman
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=Yjs1zcRAOWD5gwcP@vergenet.net \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.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.