From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Subject: Re: [Qemu-devel] [PATCH 1/2] spapr/rtas: disable the decrementer interrupt when a CPU is unplugged
Date: Sat, 7 Oct 2017 16:16:50 +1100 [thread overview]
Message-ID: <20171007051650.GI10050@umbus.fritz.box> (raw)
In-Reply-To: <63250b25-6c88-17a1-df4b-6a1e385ae7dd@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
On Fri, Oct 06, 2017 at 11:15:31PM +0200, Cédric Le Goater wrote:
> On 10/06/2017 11:07 AM, David Gibson wrote:
> > On Thu, Oct 05, 2017 at 06:49:58PM +0200, Cédric Le Goater wrote:
> >> When a CPU is stopped with the 'stop-self' RTAS call, its state
> >> 'halted' is switched to 1 and, in this case, the MSR is not taken into
> >> account anymore in the cpu_has_work() routine. Only the pending
> >> hardware interrupts are checked with their LPCR:PECE* enablement bit.
> >>
> >> If the DECR timer fires after 'stop-self' is called and before the CPU
> >> 'stop' state is reached, the nearly-dead CPU will have some work to do
> >> and the guest will crash. This case happens very frequently with the
> >> not yet upstream P9 XIVE exploitation mode. In XICS mode, the DECR is
> >> occasionally fired but after 'stop' state, so no work is to be done
> >> and the guest survives.
> >>
> >> I suspect there is a race between the QEMU mainloop triggering the
> >> timers and the TCG CPU thread but I could not quite identify the root
> >> cause. To be safe, let's disable the decrementer interrupt in the LPCR
> >> when the CPU is halted and reenable it when the CPU is restarted.
> >>
> >> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> >> ---
> >> hw/ppc/spapr_rtas.c | 16 ++++++++++++++++
> >> 1 file changed, 16 insertions(+)
> >>
> >> diff --git a/hw/ppc/spapr_rtas.c b/hw/ppc/spapr_rtas.c
> >> index cdf0b607a0a0..2389220c9738 100644
> >> --- a/hw/ppc/spapr_rtas.c
> >> +++ b/hw/ppc/spapr_rtas.c
> >> @@ -174,6 +174,15 @@ static void rtas_start_cpu(PowerPCCPU *cpu_, sPAPRMachineState *spapr,
> >> kvm_cpu_synchronize_state(cs);
> >>
> >> env->msr = (1ULL << MSR_SF) | (1ULL << MSR_ME);
> >> +
> >> + /* Enable DECR interrupt */
> >> + if (env->mmu_model == POWERPC_MMU_3_00) {
> >
> > Hm. Checking mmu_model doesn't seem right to me. I mean, it'll get
> > the right answer in practice, but the LPCR programming has nothing
> > whatsoever to do with the MMU.
> >
> > I think explicitly checking if cpu_ is a POWER9 instance with
> > object_dynamic_cast would be a better option.
>
> OK. So I guess we should change the switch statement in cpu_ppc_set_papr()
> also.
Yeah, I guess so. No rush.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-07 5:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 16:49 [Qemu-devel] [PATCH 0/2] disable the decrementer interrupt when a CPU is unplugged Cédric Le Goater
2017-10-05 16:49 ` [Qemu-devel] [PATCH 1/2] spapr/rtas: " Cédric Le Goater
2017-10-06 9:07 ` David Gibson
2017-10-06 9:53 ` Benjamin Herrenschmidt
2017-10-06 10:10 ` David Gibson
2017-10-09 14:28 ` Cédric Le Goater
2017-10-06 21:15 ` Cédric Le Goater
2017-10-07 5:16 ` David Gibson [this message]
2017-10-05 16:49 ` [Qemu-devel] [PATCH 2/2] spapr/rtas: do not reset the MSR in stop-self command Cédric Le Goater
2017-10-06 9:08 ` David Gibson
2017-10-06 6:10 ` [Qemu-devel] [PATCH 0/2] disable the decrementer interrupt when a CPU is unplugged Nikunj A Dadhania
2017-10-06 6:14 ` Cédric Le Goater
2017-10-06 7:46 ` Benjamin Herrenschmidt
2017-10-06 7:53 ` Cédric Le Goater
2017-10-06 8:11 ` Nikunj A Dadhania
2017-10-06 9:09 ` David Gibson
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=20171007051650.GI10050@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).