From: Paolo Bonzini <pbonzini@redhat.com>
To: Yacine HEBBAL <y_hebbal@esi.dz>, kvm@vger.kernel.org
Subject: Re: Difference between vcpu_load and kvm_sched_in ?
Date: Thu, 22 Oct 2015 11:37:41 +0200 [thread overview]
Message-ID: <5628AE65.804@redhat.com> (raw)
In-Reply-To: <loom.20151021T185412-564@post.gmane.org>
On 21/10/2015 19:21, Yacine HEBBAL wrote:
> If I correctly understood you last paragraph, it is better to use vm_ioctl
> to do generic processing that doesn't rely on a given VCPU and hence I won't
> need to use "CPU_FOREACH, run_on_cpu and current_cpu".
Right. On the other hand, you definitely want a vcpu_ioctl if you need
to call vcpu_load.
Thanks,
Paolo
prev parent reply other threads:[~2015-10-22 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 9:57 Difference between vcpu_load and kvm_sched_in ? Yacine
2015-10-20 15:44 ` Paolo Bonzini
2015-10-20 22:57 ` Wanpeng Li
2015-10-21 6:46 ` Paolo Bonzini
2015-10-21 10:20 ` Yacine HEBBAL
2015-10-22 7:33 ` Wanpeng Li
[not found] ` <CACEoar52w8qU2bbSTGKJdq++jz3gppLQ0N-xqsS-pnYMNnaK3Q@mail.gmail.com>
2015-10-21 10:25 ` Paolo Bonzini
2015-10-21 17:21 ` Yacine HEBBAL
2015-10-22 9:37 ` Paolo Bonzini [this message]
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=5628AE65.804@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=y_hebbal@esi.dz \
/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).