All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Durrant, Paul" <pdurrant@amazon.co.uk>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"Gautam, Varad" <vrd@amazon.de>,
	Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH] libxc: migrate migration stream definitions into Xen public headers
Date: Sun, 02 Feb 2020 09:04:11 +0000	[thread overview]
Message-ID: <75F6EE03-B4E3-4B4D-89C2-C58931D12801@infradead.org> (raw)
In-Reply-To: <db1ff2aa4a0b4a4195eb374638becaf0@EX13D32EUC003.ant.amazon.com>



On 1 February 2020 11:45:42 GMT, "Durrant, Paul" <pdurrant@amazon.co.uk> wrote:
>> -----Original Message-----
>> From: David Woodhouse <dwmw2@infradead.org>
>> Sent: 01 February 2020 00:40
>> To: xen-devel <xen-devel@lists.xenproject.org>
>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>; Wei Liu <wl@xen.org>;
>Andrew
>> Cooper <andrew.cooper3@citrix.com>; George Dunlap
>> <George.Dunlap@eu.citrix.com>; Jan Beulich <jbeulich@suse.com>;
>Julien
>> Grall <julien@xen.org>; Konrad Rzeszutek Wilk
><konrad.wilk@oracle.com>;
>> Stefano Stabellini <sstabellini@kernel.org>; Gautam, Varad
>> <vrd@amazon.de>; Durrant, Paul <pdurrant@amazon.co.uk>
>> Subject: [PATCH] libxc: migrate migration stream definitions into Xen
>> public headers
>> 
>> From: David Woodhouse <dwmw@amazon.co.uk>
>> 
>> These data structures will be used for live update, which is
>basically
>> just live migration from one Xen to the next on the same machine via
>> in-memory data structures, instead of across the network.
>> 
>> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
>> Well-excellent-carry-on-then-by: Ian Jackson
><ian.jackson@eu.citrix.com>
>> Go-with-that-for-now-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
>This is probably fine but may need some re-structuring when we consider
>non-cooperative migration. I have not yet had time to post a design
>document but my thoughts are along the lines of generalising the idea
>of 'hvm_context' records into 'domain_context' (or some suitable name).
>Then we can add the necessary 'PV' save records, such as event channel
>state, grant table state, etc. We may then want to consider using the
>same mechanism for PV shared info and maybe some of the other records
>that are currently 'top level' in the XC migration stream.

Right. This is just the existing ABI; structures that exist on the wire and are in some cases exported by existing domctls.

As we build upon it for live update and GT migration, we need to carefully consider how we do that — and whether any of the new or indeed existing fields in the HVM_CONTEXT should actually be top-level migration records in their own right, which I think is what you're suggesting.

This patch is just the basis for that work, as it's precisely the structures we have already; just renamed and moved into scope for what comes next.

-- 
dwmw2

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2020-02-02  9:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01  0:40 [Xen-devel] [PATCH] libxc: migrate migration stream definitions into Xen public headers David Woodhouse
2020-02-01 11:45 ` Durrant, Paul
2020-02-02  9:04   ` David Woodhouse [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=75F6EE03-B4E3-4B4D-89C2-C58931D12801@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=pdurrant@amazon.co.uk \
    --cc=sstabellini@kernel.org \
    --cc=vrd@amazon.de \
    --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.