On 05/05/2013 04:03:08 PM, Benjamin Herrenschmidt wrote:
On Fri, 2013-05-03 at 18:45 -0500, Scott Wood wrote:
kvmppc_lazy_ee_enable() was causing interrupts to be soft-enabled
(albeit hard-disabled) in kvmppc_restart_interrupt(). This led to
warnings, and possibly breakage if the interrupt
On Mon, 2013-05-06 at 18:53 -0500, Scott Wood wrote:
Ie. The last stage of entry will hard enable, so they should be
soft-enabled too... if not, latency trackers will consider the whole
guest periods as interrupt disabled...
OK... I guess we already have that problem on 32-bit as well?
On 05/06/2013 07:03:14 PM, Benjamin Herrenschmidt wrote:
On Mon, 2013-05-06 at 18:53 -0500, Scott Wood wrote:
Ie. The last stage of entry will hard enable, so they should be
soft-enabled too... if not, latency trackers will consider the
whole
guest periods as interrupt disabled...
On Mon, 2013-05-06 at 22:05 -0500, Scott Wood wrote:
On 05/06/2013 07:03:14 PM, Benjamin Herrenschmidt wrote:
On Mon, 2013-05-06 at 18:53 -0500, Scott Wood wrote:
Ie. The last stage of entry will hard enable, so they should be
soft-enabled too... if not, latency trackers will
On Fri, 2013-05-03 at 18:45 -0500, Scott Wood wrote:
kvmppc_lazy_ee_enable() was causing interrupts to be soft-enabled
(albeit hard-disabled) in kvmppc_restart_interrupt(). This led to
warnings, and possibly breakage if the interrupt state was later saved
and then restored (leading to
-Original Message-
From: Wood Scott-B07421
Sent: Saturday, May 04, 2013 2:45 AM
To: Alexander Graf
Cc: kvm-...@vger.kernel.org; k...@vger.kernel.org; linuxppc-
d...@lists.ozlabs.org; Wood Scott-B07421; Caraman Mihai Claudiu-B02008
Subject: [PATCH] kvm/ppc/booke64: Hard disable
On 05/03/2013 06:45:23 PM, Scott Wood wrote:
While we could just set PACA_IRQ_HARD_DIS after an exit to compensate,
instead hard-disable interrupts before entering the guest. This way,
we won't have to worry about interactions if we take an interrupt
during the guest entry code. While I don't
