From: Julien Grall <julien@xen.org>
To: David Woodhouse <dwmw2@infradead.org>,
Xen-devel <xen-devel@lists.xenproject.org>,
"Xia, Hongyan" <hongyxia@amazon.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wl@xen.org>,
paul@xen.org, "George Dunlap" <George.Dunlap@eu.citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [RFC PATCH 0/3] Live update boot memory management
Date: Wed, 15 Jan 2020 10:26:32 +0000 [thread overview]
Message-ID: <61d3344e-4c78-e134-2709-069eaae23c1c@xen.org> (raw)
In-Reply-To: <7f8fdfdf68daca5b156984412bdfc41c9970419b.camel@infradead.org>
On 15/01/2020 07:40, David Woodhouse wrote:
> On Tue, 2020-01-14 at 16:29 +0000, Julien Grall wrote:
>>> That's the point in appending an IND_WRITE64 operation to the kimage
>>> stream. The actual write is done in the last gasp of kexec_reloc()
>>> after Xen#1 is quiescent, on the way into purgatory.
>>
>> I was not sure what you meant by IND_WRITE64. Maybe I should have asked
>> it first :). Thank you for the explanation!
>
> Don't you often find an email is made easier to understand by the
> addition of a few lines of unified diff of assembler code...?
It definitely helps. I tend to prefer diff over a long paragraph trying
to explain the same :).
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2020-01-15 10:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 17:24 [Xen-devel] [RFC PATCH 0/3] Live update boot memory management David Woodhouse
2020-01-08 17:24 ` [Xen-devel] [RFC PATCH 1/3] x86/setup: Don't skip 2MiB underneath relocated Xen image David Woodhouse
2020-01-08 17:24 ` [Xen-devel] [RFC PATCH 2/3] x86/boot: Reserve live update boot memory David Woodhouse
2020-01-20 16:58 ` Jan Beulich
2020-01-20 17:24 ` David Woodhouse
2020-01-08 17:25 ` [Xen-devel] [RFC PATCH 3/3] Add KEXEC_RANGE_MA_LIVEUPDATE David Woodhouse
2020-01-10 11:15 ` [Xen-devel] [RFC PATCH 1/3] x86/setup: Don't skip 2MiB underneath relocated Xen image Durrant, Paul
2020-01-10 12:15 ` David Woodhouse
2020-01-13 11:54 ` [Xen-devel] [RFC PATCH 0/3] Live update boot memory management David Woodhouse
2020-01-14 14:15 ` Julien Grall
2020-01-14 14:48 ` David Woodhouse
2020-01-14 15:00 ` Julien Grall
2020-01-14 15:20 ` David Woodhouse
2020-01-14 16:29 ` Julien Grall
2020-01-15 7:40 ` David Woodhouse
2020-01-15 10:26 ` Julien Grall [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=61d3344e-4c78-e134-2709-069eaae23c1c@xen.org \
--to=julien@xen.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw2@infradead.org \
--cc=hongyxia@amazon.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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 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).