From: Chegu Vinod <chegu_vinod@hp.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: owasserm@redhat.com, qemu-devel@nongnu.org,
anthony@codemonkey.ws, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] Throttle-down guest when live migration does not converge.
Date: Wed, 01 May 2013 09:34:21 -0700 [thread overview]
Message-ID: <5181440D.7060006@hp.com> (raw)
In-Reply-To: <1062403018.4755871.1367422845697.JavaMail.root@redhat.com>
On 5/1/2013 8:40 AM, Paolo Bonzini wrote:
>> I shall make the suggested changes.
>> Appreciate your review feedback on this part of the change.
Hi Paolo.,
Thanks for taking a look (BTW, I accidentally left out the "RFC" in the
patch subject line...my bad!).
> Hi Vinod,
>
> I think unfortunately it is not acceptable to make this patch work only
> for KVM. (It cannot work for Xen, but that's not a problem since Xen
> uses a different migration mechanism; but it should work for TCG).
Ok. I hadn't yet looked at TCG aspects etc. Will follow up offline...
>
> Unfortunately, as you noted the run_on_cpu callbacks currently run
> under the big QEMU lock. We need to fix that first. We have time
> for that during 1.6.
Ok. Was under the impression that anytime a vcpu thread enters to do
anything in qemu the BQL had to be held. So choose to go with
run_on_cpu() . Will follow up offline on alternatives
"Holding" the vcpus in the host context (i.e. kvm module) itself is
perhaps another way. Would need some handshakes (i.e. new ioctls ) with
the kernel. Would that be acceptable way to proceed?
Thanks
Vinod
>
> Paolo
> .
>
next prev parent reply other threads:[~2013-05-01 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 12:22 [Qemu-devel] [PATCH v3] Throttle-down guest when live migration does not converge Chegu Vinod
2013-05-01 12:38 ` Eric Blake
2013-05-01 12:50 ` Chegu Vinod
2013-05-01 15:40 ` Paolo Bonzini
2013-05-01 16:34 ` Chegu Vinod [this message]
2013-05-01 17:03 ` Paolo Bonzini
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=5181440D.7060006@hp.com \
--to=chegu_vinod@hp.com \
--cc=anthony@codemonkey.ws \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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).