From: Avi Kivity <avi@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore
Date: Wed, 25 Jan 2012 14:00:49 +0200 [thread overview]
Message-ID: <4F1FEEF1.6060801@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1201251154000.3196@kaball-desktop>
On 01/25/2012 01:55 PM, Stefano Stabellini wrote:
> >
> > Match on just the MemoryRegion (and match on the object itself, not the
> > name; see xen_register_framebuffer()).
>
> I agree that would be ideal, but how can that work across save/restore?
> Unless we introduce some other kind of identifier for MemoryRegion, the
> best we have is the name right now, correct?
Right, you can't put the pointer in save/restore, the name is the only
option (and that's what qemu uses in its native save format). I thought
you were talking about internal matching, like in a previous version of
the patch/discussion.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-25 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 11:55 [Qemu-devel] [PATCH v3 0/6] save/restore on Xen Stefano Stabellini
2012-01-19 11:56 ` [Qemu-devel] [PATCH v3 1/6] vl.c: do not save the RAM state when Xen is enabled Stefano Stabellini
2012-01-19 11:56 ` [Qemu-devel] [PATCH v3 2/6] xen mapcache: check if memory region has moved Stefano Stabellini
2012-01-19 11:56 ` [Qemu-devel] [PATCH v3 3/6] Set runstate to INMIGRATE earlier Stefano Stabellini
2012-01-19 11:56 ` [Qemu-devel] [PATCH v3 4/6] cirrus_vga: do not reset videoram on resume Stefano Stabellini
2012-01-19 11:56 ` [Qemu-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore Stefano Stabellini
2012-01-19 12:24 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-01-19 13:08 ` Stefano Stabellini
2012-01-19 14:04 ` Ian Campbell
2012-01-19 14:16 ` Stefano Stabellini
2012-01-25 11:45 ` Avi Kivity
2012-01-25 11:55 ` Stefano Stabellini
2012-01-25 12:00 ` Avi Kivity [this message]
2012-01-19 11:56 ` [Qemu-devel] [PATCH v3 6/6] xen: change memory access behavior during migration Stefano Stabellini
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=4F1FEEF1.6060801@redhat.com \
--to=avi@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).