From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Difference between vcpu_load and kvm_sched_in ? Date: Thu, 22 Oct 2015 11:37:41 +0200 Message-ID: <5628AE65.804@redhat.com> References: <56266175.4030409@redhat.com> <56276827.2040900@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit To: Yacine HEBBAL , kvm@vger.kernel.org Return-path: Received: from mail-lf0-f41.google.com ([209.85.215.41]:36408 "EHLO mail-lf0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756615AbbJVJhp (ORCPT ); Thu, 22 Oct 2015 05:37:45 -0400 Received: by lffz202 with SMTP id z202so41181229lff.3 for ; Thu, 22 Oct 2015 02:37:44 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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