All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
	Gianluca Guida <Gianluca.Guida@eu.citrix.com>,
	John Levon <levon@movementarian.org>
Subject: Re: save image file format? and [RFC] tmem	save/restore/migrate
Date: Thu, 18 Jun 2009 13:54:58 +0100	[thread overview]
Message-ID: <4A3A3922.7000005@eu.citrix.com> (raw)
In-Reply-To: <20090618124305.GK16056@york.uk.xensource.com>

Tim Deegan wrote:

> At 13:26 +0100 on 18 Jun (1245331580), John Levon wrote:
>>> just layering for its own sake.  (Also, using qemu to save a PV guests 
>>> would be pretty wierd).
>> Why? We already use qemu for PV guests and that's only going to become
>> more common.
> 
> Is it?  AIUI the only thing we use qemu for in PV guests is the pvfb
> backend, which is just because nobody's put in a proper library
> interface to that code.


We also use it for the console backend when a vfb is given to the guest.

 
>>>> The qemu people are also maintaing save record compatibility now, so we
>>>> are safe from that perspective.
>>> Yes, but their code-defines-format model is rubbish.
>> Maybe now is the time to help them fix that? It's really no worse than
>> Xen's code-defines-format model, headers or not.
> 
> Qemu's code-defines-format model is actually much better than the
> xend/libxc code-defines-format model. :)  But that's not to say it's the
> thing we should be copying.

It is more about reusing than copying.

  parent reply	other threads:[~2009-06-18 12:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 23:00 save image file format? and [RFC] tmem save/restore/migrate Dan Magenheimer
2009-06-18  0:17 ` John Levon
2009-06-18  8:51 ` Tim Deegan
2009-06-18 11:39   ` John Levon
2009-06-18 12:02     ` Stefano Stabellini
2009-06-18 12:05       ` Tim Deegan
2009-06-18 12:26         ` John Levon
2009-06-18 12:43           ` Tim Deegan
2009-06-18 12:47             ` John Levon
2009-06-18 14:18               ` Tim Deegan
2009-06-22 14:28                 ` Gianluca Guida
2009-06-18 12:54             ` Stefano Stabellini [this message]
2009-06-18 12:28         ` Stefano Stabellini
2009-06-18 23:25   ` Dan Magenheimer
2009-06-18 23:40     ` Keir Fraser
2009-06-18 10:30 ` 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=4A3A3922.7000005@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Gianluca.Guida@eu.citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=levon@movementarian.org \
    --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 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.