From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
Henry Wang <Henry.Wang@arm.com>
Subject: Re: [PATCH][4.17?] x86: also zap secondary time area handles during soft reset
Date: Tue, 25 Oct 2022 18:04:29 +0200 [thread overview]
Message-ID: <Y1gJDYEjARSD0F/s@Air-de-Roger> (raw)
In-Reply-To: <76d0ce3d-7c05-9f4c-921a-0c7e0f5d9348@suse.com>
On Tue, Oct 25, 2022 at 05:58:10PM +0200, Jan Beulich wrote:
> On 25.10.2022 17:23, Roger Pau Monné wrote:
> > On Thu, Oct 13, 2022 at 08:48:21AM +0200, Jan Beulich wrote:
> I wasn't sure about moving arch_domain_soft_reset() as a whole, but
> yes, if that wouldn't cause other interaction issues this might be
> an option.
>
> > In any case it's unlikely for a domain that was attempting a soft
> > reset to survive the hypervisor rejecting the operation, so it doesn't
> > matter much whether the domain is crashed by Xen or left as-is I would
> > think.
>
> I'm sorry, I don't think I understand what you're saying here. For
> PV I'd very much expect the guest to survive; it may of course then
> be crashed or destroyed by a further tool stack operation.
I was expecting a domain that goes to the length of preparing for a
soft reset operation to either perform such soft reset, or die as a
result (and perform a non-soft reset), as recovering into the previous
state won't be feasible. But maybe I'm wrong.
Thanks, Roger.
next prev parent reply other threads:[~2022-10-25 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 6:48 [PATCH][4.17?] x86: also zap secondary time area handles during soft reset Jan Beulich
2022-10-25 15:23 ` Roger Pau Monné
2022-10-25 15:58 ` Jan Beulich
2022-10-25 16:04 ` Roger Pau Monné [this message]
2022-10-27 9:44 ` Henry Wang
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=Y1gJDYEjARSD0F/s@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=Henry.Wang@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=wl@xen.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.