From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Sanidhya Kashyap <sanidhya.iiith@gmail.com>
Cc: Amit Shah <amit.shah@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/8] Obtain dirty bitmap via VM logging
Date: Fri, 18 Jul 2014 18:42:41 +0100 [thread overview]
Message-ID: <20140718174241.GG10517@work-vm> (raw)
In-Reply-To: <53C95945.8010402@gmail.com>
* Sanidhya Kashyap (sanidhya.iiith@gmail.com) wrote:
> >
> > 1) Do you have some examples of output?
> > Can you see hot areas in the kernel or something else?
> >
>
> I looked at it sometimes back. I will try to provide some images (as
> suggested by you earlier) to see any consistently used areas.
>
> > 2) 'frequency' is probably the wrong name for the parameter you have; since
> > the parameter is actually the delay between epochs, where as frequency
> > would imply the number of epochs/second.
> >
>
> will surely change it to period. It is pointed out by Eric too.
>
> > 3) The change to runstates is interesting; up until now 'runstate' is really
> > mostly about the state of the CPU, but by adding migration/dumping to the
> > states you're trying to convey more in that single state variable; I'm not
> > quite sure if this is the right thing to do or not.
> >
>
> Is there any alternative that can allow us to execute only one of the
> processes - either migration or bitmap dump. One very basic approach
> that I have thought is about using a global variable but don't know
> whether that is a good option or not.
>
> Any other alternative is welcomed.
I think a global variable is the right thing; something like 'dirty_bitmap_user'
being an enum between none, migration, dumping would make sense to me.
While adding global variables ia a bad thing, since the dirty bitmap already is
global all you're doing really is adding an extra bit of state to it.
If you have something like
char *dirty_bitmap_user_as_string()
then your test in your qml code would look something like:
if (dirty_bitmap_user != dbu_none) {
error_report("Can't do dirty dumping since %s is in use", dirty_bitmap_user_as_string());
}
and then if more things use it in the future the existing users don't
have to change.
Dave
>
> -----
>
> Sanidhya Kashyap
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-07-18 17:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 11:21 [Qemu-devel] [PATCH v4 0/8] Obtain dirty bitmap via VM logging Sanidhya Kashyap
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 1/8] enable sharing of the function between migration and bitmap dump Sanidhya Kashyap
2014-07-18 11:00 ` Dr. David Alan Gilbert
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 2/8] RunState: added two new flags for bitmap dump and migration process Sanidhya Kashyap
2014-07-18 11:02 ` Dr. David Alan Gilbert
2014-07-18 12:16 ` Eric Blake
2014-07-18 18:01 ` Sanidhya Kashyap
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 3/8] BitmapLog: bitmap dump code via QAPI framework with runstates Sanidhya Kashyap
2014-07-18 11:12 ` Dr. David Alan Gilbert
2014-07-18 18:18 ` Sanidhya Kashyap
2014-07-18 11:14 ` Dr. David Alan Gilbert
2014-07-18 18:09 ` Sanidhya Kashyap
2014-07-18 12:20 ` Eric Blake
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 4/8] BitmapLog: hmp interface for dirty bitmap dump Sanidhya Kashyap
2014-07-18 11:15 ` Dr. David Alan Gilbert
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 5/8] BitmapLog: cancel mechanism for an already running dump bitmap process Sanidhya Kashyap
2014-07-18 12:22 ` Eric Blake
2014-07-18 17:51 ` Sanidhya Kashyap
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 6/8] BitmapLog: set the frequency of the " Sanidhya Kashyap
2014-07-18 12:28 ` Eric Blake
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 7/8] BitmapLog: get the information about the parameters Sanidhya Kashyap
2014-07-18 12:35 ` Eric Blake
2014-07-18 17:41 ` Sanidhya Kashyap
2014-07-17 11:21 ` [Qemu-devel] [PATCH v4 8/8] BitmapLog: python script for extracting bitmap from a binary file Sanidhya Kashyap
2014-07-18 11:17 ` Dr. David Alan Gilbert
2014-07-18 10:56 ` [Qemu-devel] [PATCH v4 0/8] Obtain dirty bitmap via VM logging Dr. David Alan Gilbert
2014-07-18 13:42 ` Eric Blake
2014-07-18 17:28 ` Sanidhya Kashyap
2014-07-18 17:42 ` Dr. David Alan Gilbert [this message]
2014-07-18 12:39 ` Eric Blake
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=20140718174241.GG10517@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=sanidhya.iiith@gmail.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.