From: Jan Beulich <jbeulich@suse.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Juergen Gross <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Xen 4.12 panic on Thinkpad W540 with UEFI mutiboot2, efi=no-rs workarounds it
Date: Wed, 9 Oct 2019 14:24:31 +0200 [thread overview]
Message-ID: <bddff3b2-a0cc-1a7e-8702-86bea33c9e16@suse.com> (raw)
In-Reply-To: <20191009122109.GR8065@mail-itl>
On 09.10.2019 14:21, Marek Marczykowski-Górecki wrote:
> On Wed, Oct 09, 2019 at 02:07:05PM +0200, Jan Beulich wrote:
>> On 09.10.2019 13:52, Marek Marczykowski-Górecki wrote:
>>> I'm talking about Xen->Xen transition here. How system table pointer is
>>> passed from old Xen to new Xen instance? And how the new Xen instance
>>> deals with boot services being not available anymore?
>>
>> It doesn't. I should better have said "* -> Xen transitions" in
>> my earlier reply. I simply can't see how this can all work with
>> EFI underneath without some extra conveying of data from the old
>> to the new instance.
>
> Does it mean the whole discussion about SetVirtualAddressMap() being
> incompatible with kexec is moot, because runtime services (including
> SetVirtualAddressMap()) are not used by Xen after kexec anyway? If I
> understand correctly, you just said the Xen after kexec don't have
> runtime services pointer.
The concern is about kexec-ing to Linux (based on what I recall
from when I wrote this code; as said the situation may have
changed for modern Linux).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-09 12:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190807132657.GA2852@mail-itl>
2019-08-07 13:50 ` [Xen-devel] Xen 4.12 panic on Thinkpad W540 with UEFI mutiboot2, efi=no-rs workarounds it Andrew Cooper
2019-08-07 14:45 ` Jan Beulich
[not found] ` <20190807151703.GA2659@mail-itl>
2019-08-07 15:33 ` Jan Beulich
2019-08-07 15:51 ` Marek Marczykowski-Górecki
2019-08-07 15:58 ` Jan Beulich
2019-08-07 16:04 ` Marek Marczykowski-Górecki
2019-08-07 16:34 ` Jan Beulich
[not found] ` <20190807192557.GC3257@mail-itl>
2019-08-08 2:53 ` Marek Marczykowski-Górecki
2019-08-08 6:03 ` Jan Beulich
2019-10-08 11:50 ` Marek Marczykowski-Górecki
2019-10-08 13:08 ` Jan Beulich
2019-10-08 13:52 ` Marek Marczykowski-Górecki
2019-10-08 14:19 ` Jan Beulich
2019-10-08 16:29 ` Marek Marczykowski-Górecki
2019-10-09 0:40 ` Marek Marczykowski-Górecki
2019-10-09 8:56 ` Jan Beulich
2019-10-09 10:31 ` Marek Marczykowski-Górecki
2019-10-09 10:50 ` Jan Beulich
2019-10-09 11:00 ` Marek Marczykowski-Górecki
2019-10-09 11:48 ` Jan Beulich
2019-10-09 11:52 ` Marek Marczykowski-Górecki
2019-10-09 12:07 ` Jan Beulich
2019-10-09 12:21 ` Marek Marczykowski-Górecki
2019-10-09 12:24 ` Jan Beulich [this message]
2019-10-09 12:27 ` Marek Marczykowski-Górecki
2019-10-09 13:31 ` Jan Beulich
2019-10-09 23:57 ` Marek Marczykowski-Górecki
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=bddff3b2-a0cc-1a7e-8702-86bea33c9e16@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jgross@suse.com \
--cc=marmarek@invisiblethingslab.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).