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 16:27:36 -0500 [thread overview] Message-ID: <1368134856.654.11@snotra> (raw) In-Reply-To: <1368103062.25488.193.camel@pasglop> (from benh@kernel.crashing.org on Thu May 9 07:37:42 2013) 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... > > > Case 1) > > > -> Local_irq_disable() will set soft_enabled = 0 > > > -> Now Externel interrupt happens, there we set PACA_IRQ_EE in > > irq_happened, Also clears EE in SRR1 and rfi. So interrupts are hard > > disabled. No more other interrupt gated by MSR.EE can happen. Looks > > like the idea here is to not let a device keep on inserting > interrupt > > till the interrupt condition on device is cleared, right? > > The external interrupt line is level sensitive normally, so we have to > mask MSR:EE in that case or the interrupt would keep re-occurring > (note > that FSL has this concept of auto-acked interrupts via the on die MPIC > for which you can potentially use PACA_IRQ_EE_EDGE instead and avoid > having to mask MSR:EE). Note that if we do this, we can no longer leave the interrupt vector in EPR, and would have to track (potentially multiple different) pending external interrupts in software. -Scott
WARNING: multiple messages have this Message-ID (diff)
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 16:27:36 -0500 [thread overview] Message-ID: <1368134856.654.11@snotra> (raw) In-Reply-To: <1368103062.25488.193.camel@pasglop> (from benh@kernel.crashing.org on Thu May 9 07:37:42 2013) 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=3D1 even if EE=3D0, EXT/DEC/DBELL still occur =20 > as I > > recall. >=20 > Only if directed to the hypervisor. This is always the case with KVM, right? At least on booke... > > > Case 1) > > > -> Local_irq_disable() will set soft_enabled =3D 0 > > > -> Now Externel interrupt happens, there we set PACA_IRQ_EE in > > irq_happened, Also clears EE in SRR1 and rfi. So interrupts are hard > > disabled. No more other interrupt gated by MSR.EE can happen. Looks > > like the idea here is to not let a device keep on inserting =20 > interrupt > > till the interrupt condition on device is cleared, right? >=20 > The external interrupt line is level sensitive normally, so we have to > mask MSR:EE in that case or the interrupt would keep re-occurring =20 > (note > that FSL has this concept of auto-acked interrupts via the on die MPIC > for which you can potentially use PACA_IRQ_EE_EDGE instead and avoid > having to mask MSR:EE). Note that if we do this, we can no longer leave the interrupt vector in =20 EPR, and would have to track (potentially multiple different) pending =20 external interrupts in software. -Scott=
next prev parent reply other threads:[~2013-05-09 21:27 UTC|newest] Thread overview: 88+ 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:10 ` Tiejun Chen 2013-05-06 3:10 ` Tiejun Chen 2013-05-06 3:13 ` tiejun.chen 2013-05-06 3:13 ` tiejun.chen 2013-05-06 3:13 ` tiejun.chen 2013-05-06 23:50 ` Scott Wood 2013-05-06 23:50 ` Scott Wood 2013-05-07 1:56 ` tiejun.chen 2013-05-07 1:56 ` tiejun.chen 2013-05-07 1:56 ` tiejun.chen 2013-05-07 2:06 ` Scott Wood 2013-05-07 2:06 ` Scott Wood 2013-05-07 2:43 ` tiejun.chen 2013-05-07 2:43 ` tiejun.chen 2013-05-07 2:43 ` tiejun.chen 2013-05-07 3:04 ` Scott Wood 2013-05-07 3:04 ` Scott Wood 2013-05-08 13:14 ` Caraman Mihai Claudiu-B02008 2013-05-08 13:14 ` Caraman Mihai Claudiu-B02008 2013-05-09 7:33 ` Bhushan Bharat-R65777 2013-05-09 7:33 ` Bhushan Bharat-R65777 2013-05-09 7:47 ` tiejun.chen 2013-05-09 7:47 ` tiejun.chen 2013-05-09 7:47 ` tiejun.chen 2013-05-09 7:51 ` Bhushan Bharat-R65777 2013-05-09 7:51 ` Bhushan Bharat-R65777 2013-05-09 8:04 ` tiejun.chen 2013-05-09 8:04 ` tiejun.chen 2013-05-09 8:04 ` tiejun.chen 2013-05-09 8:08 ` Kevin Hao 2013-05-09 8:08 ` Kevin Hao 2013-05-09 8:08 ` Kevin Hao 2013-05-09 8:12 ` Bhushan Bharat-R65777 2013-05-09 8:12 ` Bhushan Bharat-R65777 2013-05-09 8:17 ` tiejun.chen 2013-05-09 8:17 ` tiejun.chen 2013-05-09 8:17 ` tiejun.chen 2013-05-09 8:26 ` Bhushan Bharat-R65777 2013-05-09 8:26 ` Bhushan Bharat-R65777 2013-05-09 8:21 ` Kevin Hao 2013-05-09 8:21 ` Kevin Hao 2013-05-09 8:21 ` Kevin Hao 2013-05-09 12:26 ` Benjamin Herrenschmidt 2013-05-09 12:26 ` Benjamin Herrenschmidt 2013-05-09 12:26 ` Benjamin Herrenschmidt 2013-05-09 8:23 ` Bhushan Bharat-R65777 2013-05-09 8:23 ` Bhushan Bharat-R65777 2013-05-09 9:44 ` tiejun.chen 2013-05-09 9:44 ` tiejun.chen 2013-05-09 9:44 ` tiejun.chen 2013-05-09 10:00 ` Bhushan Bharat-R65777 2013-05-09 10:00 ` Bhushan Bharat-R65777 2013-05-09 10:18 ` [RFC][PATCH " tiejun.chen 2013-05-09 10:18 ` [RFC][KVM][PATCH " tiejun.chen 2013-05-09 10:18 ` tiejun.chen 2013-05-09 11:21 ` Bhushan Bharat-R65777 2013-05-09 11:21 ` Bhushan Bharat-R65777 2013-05-09 11:35 ` tiejun.chen 2013-05-09 11:35 ` tiejun.chen 2013-05-09 11:35 ` tiejun.chen 2013-05-09 12:37 ` [RFC][PATCH " Benjamin Herrenschmidt 2013-05-09 12:37 ` [RFC][KVM][PATCH " Benjamin Herrenschmidt 2013-05-09 12:37 ` Benjamin Herrenschmidt 2013-05-09 13:28 ` David Laight 2013-05-09 13:28 ` David Laight 2013-05-09 13:28 ` David Laight 2013-05-09 22:01 ` Benjamin Herrenschmidt 2013-05-09 22:01 ` Benjamin Herrenschmidt 2013-05-09 22:01 ` Benjamin Herrenschmidt 2013-05-09 14:13 ` Chen, Tiejun 2013-05-09 14:13 ` Chen, Tiejun 2013-05-09 14:13 ` Chen, Tiejun 2013-05-09 21:27 ` Scott Wood [this message] 2013-05-09 21:27 ` Scott Wood 2013-05-09 22:07 ` [RFC][PATCH " Benjamin Herrenschmidt 2013-05-09 22:07 ` [RFC][KVM][PATCH " Benjamin Herrenschmidt 2013-05-09 22:07 ` Benjamin Herrenschmidt 2013-05-09 22:13 ` Scott Wood 2013-05-09 22:13 ` Scott Wood 2013-05-10 14:12 ` Kevin Hao 2013-05-10 14:12 ` Kevin Hao 2013-05-10 14:12 ` Kevin Hao 2013-05-10 21:49 ` Benjamin Herrenschmidt 2013-05-10 21:49 ` Benjamin Herrenschmidt 2013-05-10 21:49 ` Benjamin Herrenschmidt 2013-05-10 21:50 ` 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=1368134856.654.11@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: linkBe 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.