From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Subject: Re: [Android-virt] [PATCH v3] KVM: Factor out kvm_vcpu_kick to arch-generic
 code
Date: Thu, 9 Feb 2012 17:43:40 -0600
Message-ID: <4F345A2C.6090504@freescale.com>
References: <20120209223331.28279.36149.stgit@ubuntu> <F8E26AB3-EDC8-402E-BF89-CA79D63EBBE5@suse.de> <CANM98qLT9=JupvHPtGCu_K8HrF7Mo-TPvmdVZDaQBk8e-FT6QA@mail.gmail.com> <0FEE585F-5E21-47F2-A3F0-AD0DE05EBB43@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Christoffer Dall <c.dall@virtualopensystems.com>,
	<kvm@vger.kernel.org>, <tech@virtualopensystems.com>,
	<kvm-ppc@vger.kernel.org>, <android-virt@lists.cs.columbia.edu>,
	<mtosatti@redhat.com>
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-ppc-owner@vger.kernel.org>
In-Reply-To: <0FEE585F-5E21-47F2-A3F0-AD0DE05EBB43@suse.de>
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 02/09/2012 05:23 PM, Alexander Graf wrote:
> How about we return 1 for kvm_arch_vcpu_in_guest_mode() on !x86
> always, just like it's done today basically? Then we can worry about
> needless IPIs later and don't regress from the respective current
> kick implementations.

And perhaps call the function kvm_arch_vcpu_maybe_in_guest_mode() to
avoid confusion.

-Scott