qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Juan Quintela <quintela@trasno.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] monitor: Add port write command
Date: Tue, 14 Jul 2009 10:49:08 -0500	[thread overview]
Message-ID: <4A5CA8F4.8050908@codemonkey.ws> (raw)
In-Reply-To: <m31voj47ht.fsf@neno.mitica>

Juan Quintela wrote:
> We were thinking about that functionality some time ago.  We were
> looking at an apic bug during migration, and it was not trivial to dump
> apic state before and after migration.
>
> I took a look at it, and basically decided that I would have to
> replicate the savevm method.  Your apprearch mean that doing the command
> is trivial, and we have "meaningful" labels for it.
>
> Will take a look at using that in some driver.
>   

Great.  I think an incremental conversion is the right approach.  If we 
tie this into qdev correctly, then we could also do some nice things 
with migration.  We could dump out a file that describes any given 
migration protocol version.  We could then use this to automatically 
check whether we broke the migration format between versions but just 
doing a diff.

I think there's also an opportunity to adjust the migration protocol.  
One change I had to make to the savevm format was removing all of the 
size parameters.  This is because the nature of QEMUFile makes it such 
that you don't know what the size was until you actually wrote data.  
The old savevm format used to rely on seeking to update the size 
parameter.  If we know the size of the section (based on the 
description), we can reintroduce this to the protocol.

What's more, we can probably get rid of QEMUFile all together and 
introduce a more useful abstraction that doesn't have such complex 
buffering.

This refactoring is definitely high on my 0.12 wish list :-)

Regards,

Anthony Liguori

  parent reply	other threads:[~2009-07-14 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  8:20 [Qemu-devel] [PATCH] monitor: Add port write command Jan Kiszka
2009-07-14 15:06 ` Anthony Liguori
     [not found]   ` <m31voj47ht.fsf@neno.mitica>
2009-07-14 15:49     ` Anthony Liguori [this message]
2009-07-14 18:57   ` Blue Swirl
2009-07-14 19:30   ` Paul Brook
2009-07-14 20:03     ` Anthony Liguori
2009-07-14 20:37       ` [Qemu-devel] " Jan Kiszka
2009-07-15  7:34     ` [Qemu-devel] " Gleb Natapov
2009-07-15 10:14       ` Paul Brook
2009-07-15 10:40         ` Jan Kiszka
2009-07-15 11:14           ` Gleb Natapov
2009-07-15 11:12         ` Gleb Natapov
2009-07-15 12:36         ` Anthony Liguori
2009-07-15 14:38           ` Paul Brook

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=4A5CA8F4.8050908@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@trasno.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).