From: Stefan Hajnoczi <stefanha@gmail.com>
To: Wolfgang Richter <wolf@cs.cmu.edu>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding Disk-Level Introspection to QEMU
Date: Wed, 24 Apr 2013 10:39:40 +0200 [thread overview]
Message-ID: <20130424083940.GC20971@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CACO=3k7_nKTbvro3qcURDLxD1kQ+bWkGyHXE1kfbFtvpe2XWuA@mail.gmail.com>
On Tue, Apr 23, 2013 at 03:11:26PM -0400, Wolfgang Richter wrote:
> On Tue, Apr 23, 2013 at 2:31 PM, Wolfgang Richter <wolf@cs.cmu.edu> wrote:
>
> > On Tue, Apr 23, 2013 at 2:21 PM, Stefan Hajnoczi <stefanha@gmail.com>wrote:
> >
> >> Eric's suggestion to use NBD makes sense to me. The block-backup code
> >> can be extended fairly easier using sync mode=none (do not perform a
> >> background copy of the entire disk) and by disabling the bitmap
> >> (essentially "tap" mode).
> >
> >
> Also, as another thought, I think I can actually use the bitmap to implement
> an optimization. In my code, I already use a bitmap to determine which
> sectors I want to introspect (ignoring portions of the disk greatly reduces
> required bandwidth and overhead; swap space for example isn't generally
> interesting unless you can interpret memory as well). So I think I can
> adapt
> my code here as well.
Cool. By the way, do you actually care about the data being written or
just which sectors were touched?
Stefan
next prev parent reply other threads:[~2013-04-24 8:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 17:12 [Qemu-devel] Adding Disk-Level Introspection to QEMU Wolfgang Richter
2013-04-23 17:22 ` Eric Blake
2013-04-23 17:40 ` Wolfgang Richter
2013-04-24 8:37 ` Stefan Hajnoczi
2013-04-24 9:24 ` Paolo Bonzini
2013-04-24 16:14 ` Wolfgang Richter
2013-04-24 15:59 ` Wolfgang Richter
2013-04-24 19:20 ` Wolfgang Richter
2013-04-23 18:19 ` Stefan Hajnoczi
2013-04-23 18:21 ` Stefan Hajnoczi
2013-04-23 18:31 ` Wolfgang Richter
2013-04-23 19:11 ` Wolfgang Richter
2013-04-24 8:39 ` Stefan Hajnoczi [this message]
2013-04-24 16:05 ` Wolfgang Richter
2013-04-24 9:26 ` Paolo Bonzini
2013-04-24 16:14 ` Wolfgang Richter
[not found] ` <CACO=3k4eoT9KwPBgM2eN089=PzzOyBECWgD6MOHz=bzy5EcxAQ@mail.gmail.com>
[not found] ` <51780539.1010303@redhat.com>
2013-04-24 16:43 ` Wolfgang Richter
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=20130424083940.GC20971@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wolf@cs.cmu.edu \
/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).