From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
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
Subject: Re: [Android-virt] [PATCH v3] KVM: Factor out kvm_vcpu_kick to arch-generic code
Date: Thu, 09 Feb 2012 23:43:40 +0000 [thread overview]
Message-ID: <4F345A2C.6090504@freescale.com> (raw)
In-Reply-To: <0FEE585F-5E21-47F2-A3F0-AD0DE05EBB43@suse.de>
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
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
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>
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 [thread overview]
Message-ID: <4F345A2C.6090504@freescale.com> (raw)
In-Reply-To: <0FEE585F-5E21-47F2-A3F0-AD0DE05EBB43@suse.de>
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
next prev parent reply other threads:[~2012-02-09 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 22:33 [PATCH v3] KVM: Factor out kvm_vcpu_kick to arch-generic code Christoffer Dall
2012-02-09 22:33 ` Christoffer Dall
2012-02-09 23:02 ` [Android-virt] " Alexander Graf
2012-02-09 23:02 ` Alexander Graf
2012-02-09 23:18 ` Christoffer Dall
2012-02-09 23:18 ` Christoffer Dall
2012-02-09 23:23 ` Alexander Graf
2012-02-09 23:23 ` Alexander Graf
2012-02-09 23:43 ` Scott Wood [this message]
2012-02-09 23:43 ` Scott Wood
2012-02-09 23:47 ` Alexander Graf
2012-02-09 23:47 ` Alexander Graf
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=4F345A2C.6090504@freescale.com \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=android-virt@lists.cs.columbia.edu \
--cc=c.dall@virtualopensystems.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=tech@virtualopensystems.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.