From: Scott Wood <scottwood@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Caraman Mihai Claudiu-B02008 <B02008@freescale.com>,
"agraf@suse.de" <agraf@suse.de>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"tiejun.chen" <tiejun.chen@windriver.com>,
Bhushan Bharat-R65777 <R65777@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC][KVM][PATCH 1/1] kvm:ppc:booke-64: soft-disable interrupts
Date: Thu, 9 May 2013 17:13:03 -0500 [thread overview]
Message-ID: <1368137583.654.15@snotra> (raw)
In-Reply-To: <1368137220.3715.14.camel@pasglop> (from benh@kernel.crashing.org on Thu May 9 17:07:00 2013)
On 05/09/2013 05:07:00 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-05-09 at 16:27 -0500, Scott Wood wrote:
> > On 05/09/2013 07:37:42 AM, Benjamin Herrenschmidt wrote:
> > > On Thu, 2013-05-09 at 17:44 +0800, tiejun.chen wrote:
> > > >
> > > > Actually in the case GS=1 even if EE=0, EXT/DEC/DBELL still
> occur
> > > as I
> > > > recall.
> > >
> > > Only if directed to the hypervisor.
> >
> > This is always the case with KVM, right? At least on booke...
>
> Hrm, on A2 we could choose iirc. Well not DEC but EXT at least, I
> don't
> remember about DBELL.
As for as the hardware goes we can choose on e500mc as well -- we just
don't support it in KVM, because we can't distinguish between guest and
host interrupts without routing the latter to critical, which is way
too much of a pain for Linux (we did it in our standalone hypervisor,
though).
-Scott
next prev parent reply other threads:[~2013-05-09 22:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 3:10 [RFC][KVM][PATCH 1/1] kvm:ppc:booke-64: soft-disable interrupts Tiejun Chen
2013-05-06 3:13 ` tiejun.chen
2013-05-06 23:50 ` Scott Wood
2013-05-07 1:56 ` tiejun.chen
2013-05-07 2:06 ` Scott Wood
2013-05-07 2:43 ` tiejun.chen
2013-05-07 3:04 ` Scott Wood
2013-05-08 13:14 ` Caraman Mihai Claudiu-B02008
2013-05-09 7:33 ` Bhushan Bharat-R65777
2013-05-09 7:47 ` tiejun.chen
2013-05-09 7:51 ` Bhushan Bharat-R65777
2013-05-09 8:04 ` tiejun.chen
2013-05-09 8:08 ` Kevin Hao
2013-05-09 8:12 ` Bhushan Bharat-R65777
2013-05-09 8:17 ` tiejun.chen
2013-05-09 8:26 ` Bhushan Bharat-R65777
2013-05-09 8:21 ` Kevin Hao
2013-05-09 12:26 ` Benjamin Herrenschmidt
2013-05-09 8:23 ` Bhushan Bharat-R65777
2013-05-09 9:44 ` tiejun.chen
2013-05-09 10:00 ` Bhushan Bharat-R65777
2013-05-09 10:18 ` [RFC][PATCH " tiejun.chen
2013-05-09 11:21 ` [RFC][KVM][PATCH " Bhushan Bharat-R65777
2013-05-09 11:35 ` tiejun.chen
2013-05-09 12:37 ` [RFC][PATCH " Benjamin Herrenschmidt
2013-05-09 13:28 ` [RFC][KVM][PATCH " David Laight
2013-05-09 22:01 ` Benjamin Herrenschmidt
2013-05-09 14:13 ` Chen, Tiejun
2013-05-09 21:27 ` Scott Wood
2013-05-09 22:07 ` [RFC][PATCH " Benjamin Herrenschmidt
2013-05-09 22:13 ` Scott Wood [this message]
2013-05-10 14:12 ` [RFC][KVM][PATCH " Kevin Hao
2013-05-10 21:49 ` Benjamin Herrenschmidt
2013-05-10 21:50 ` Benjamin Herrenschmidt
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=1368137583.654.15@snotra \
--to=scottwood@freescale.com \
--cc=B02008@freescale.com \
--cc=B07421@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tiejun.chen@windriver.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