All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] savevm/loadvm
Date: Wed, 09 Oct 2013 09:47:06 +0200	[thread overview]
Message-ID: <525509FA.1070105@redhat.com> (raw)
In-Reply-To: <52550275.7000007@ozlabs.ru>

Il 09/10/2013 09:15, Alexey Kardashevskiy ha scritto:
> Sorry for my ignorance (I never ever touched this part of qemu) but how can
> you possibly avoid block.c while doing savevm? The qcow2 driver must not
> use posix read()/write(), right? So no matter how, all writes end up in
> bdrv_co_do_writev() which changes blocks number. Or use
> raw_aio_readv()/raw_aio_writev() API directly? Please give some more hints.
> Thanks.

I think Kevin was suggesting using qcow_aio_writev directly, or
something like that.  But it is not trivial, especially because
save_vm_state takes byte offsets instead of sectors.  So for now I'd
still go for the more hacky solution.

Paolo

  reply	other threads:[~2013-10-09  7:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  8:40 [Qemu-devel] savevm/loadvm Alexey Kardashevskiy
2013-10-08  9:04 ` Paolo Bonzini
2013-10-08  9:23   ` Kevin Wolf
2013-10-08  9:33     ` Paolo Bonzini
2013-10-09  7:15       ` Alexey Kardashevskiy
2013-10-09  7:47         ` Paolo Bonzini [this message]
2013-10-10  3:50           ` Alexey Kardashevskiy
2013-10-16  6:51             ` Alexey Kardashevskiy
2013-11-01 13:22               ` Alexey Kardashevskiy
2013-11-01 14:16 ` Max Reitz
2013-11-03  0:34   ` Alexey Kardashevskiy

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=525509FA.1070105@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.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.