From: Greg Kurz <groug@kaod.org>
To: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
Cc: Aravinda Prasad <arawinda.p@gmail.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel@nongnu.org, Nicholas Piggin <npiggin@gmail.com>,
Ganesh Goudar <ganeshgr@linux.ibm.com>,
qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v2 7/8] ppc/spapr: Implement FWNMI System Reset delivery
Date: Mon, 16 Mar 2020 18:52:54 +0100 [thread overview]
Message-ID: <20200316185254.1aca6e20@bahia.lan> (raw)
In-Reply-To: <20200316173500.576hdvush3fzvvef@in.ibm.com>
On Mon, 16 Mar 2020 23:05:00 +0530
Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com> wrote:
> On 2020-03-17 00:26:12 Tue, Nicholas Piggin wrote:
> > PAPR requires that if "ibm,nmi-register" succeeds, then the hypervisor
> > delivers all system reset and machine check exceptions to the registered
> > addresses.
> >
> > System Resets are delivered with registers set to the architected state,
> > and with no interlock.
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> > hw/ppc/spapr.c | 46 ++++++++++++++++++++++++++++++++++++++++++++--
> > 1 file changed, 44 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> > index 25221d843c..78e649f47d 100644
> > --- a/hw/ppc/spapr.c
> > +++ b/hw/ppc/spapr.c
> > @@ -967,7 +967,29 @@ static void spapr_dt_rtas(SpaprMachineState *spapr, void *fdt)
> > _FDT(fdt_setprop(fdt, rtas, "ibm,max-associativity-domains",
> > maxdomains, sizeof(maxdomains)));
> >
> > - _FDT(fdt_setprop_cell(fdt, rtas, "rtas-size", RTAS_SIZE));
> > + /*
> > + * FWNMI reserves RTAS_ERROR_LOG_MAX for the machine check error log,
> > + * and 16 bytes per CPU for system reset error log plus an extra 8 bytes.
> > + *
> > + * The system reset requirements are driven by existing Linux and PowerVM
> > + * implementation which (contrary to PAPR) saves r3 in the error log
> > + * structure like machine check, so Linux expects to find the saved r3
> > + * value at the address in r3 upon FWNMI-enabled sreset interrupt (and
> > + * does not look at the error value).
> > + *
> > + * System reset interrupts are not subject to interlock like machine
> > + * check, so this memory area could be corrupted if the sreset is
> > + * interrupted by a machine check (or vice versa) if it was shared. To
> > + * prevent this, system reset uses per-CPU areas for the sreset save
> > + * area. A system reset that interrupts a system reset handler could
> > + * still overwrite this area, but Linux doesn't try to recover in that
> > + * case anyway.
> > + *
> > + * The extra 8 bytes is required because Linux's FWNMI error log check
> > + * is off-by-one.
> > + */
> > + _FDT(fdt_setprop_cell(fdt, rtas, "rtas-size", RTAS_ERROR_LOG_MAX +
> > + ms->smp.max_cpus * sizeof(uint64_t)*2 + sizeof(uint64_t)));
>
> Currently the rtas region is only of size 2048 (i.e RTAS_ERROR_LOG_MAX).
> Do we need SLOF change to increase rtas area as well ? Otherwise QEMU
> may corrupt guest memory area OR Am I wrong ?
>
A change is pending for SLOF to use the "rtas-size" property
provided by QEMU:
https://patchwork.ozlabs.org/patch/1255264/
> Thanks,
> -Mahesh/
>
> > _FDT(fdt_setprop_cell(fdt, rtas, "rtas-error-log-max",
> > RTAS_ERROR_LOG_MAX));
> > _FDT(fdt_setprop_cell(fdt, rtas, "rtas-event-scan-rate",
> > @@ -3399,8 +3421,28 @@ static void spapr_machine_finalizefn(Object *obj)
> >
> > void spapr_do_system_reset_on_cpu(CPUState *cs, run_on_cpu_data arg)
> > {
> > + SpaprMachineState *spapr = SPAPR_MACHINE(qdev_get_machine());
> > +
> > cpu_synchronize_state(cs);
> > - ppc_cpu_do_system_reset(cs, -1);
> > + /* If FWNMI is inactive, addr will be -1, which will deliver to 0x100 */
> > + if (spapr->fwnmi_system_reset_addr != -1) {
> > + uint64_t rtas_addr, addr;
> > + PowerPCCPU *cpu = POWERPC_CPU(cs);
> > + CPUPPCState *env = &cpu->env;
> > +
> > + /* get rtas addr from fdt */
> > + rtas_addr = spapr_get_rtas_addr();
> > + if (!rtas_addr) {
> > + qemu_system_guest_panicked(NULL);
> > + return;
> > + }
> > +
> > + addr = rtas_addr + RTAS_ERROR_LOG_MAX + cs->cpu_index * sizeof(uint64_t)*2;
> > + stq_be_phys(&address_space_memory, addr, env->gpr[3]);
> > + stq_be_phys(&address_space_memory, addr + sizeof(uint64_t), 0);
> > + env->gpr[3] = addr;
> > + }
> > + ppc_cpu_do_system_reset(cs, spapr->fwnmi_system_reset_addr);
> > }
> >
> > static void spapr_nmi(NMIState *n, int cpu_index, Error **errp)
> > --
> > 2.23.0
> >
> >
>
next prev parent reply other threads:[~2020-03-16 18:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 14:26 [PATCH v2 0/8] FWNMI fixes / changes Nicholas Piggin
2020-03-16 14:26 ` [PATCH v2 1/8] ppc/spapr: Fix FWNMI machine check failure handling Nicholas Piggin
2020-03-16 15:27 ` Greg Kurz
2020-03-16 22:46 ` David Gibson
2020-03-16 14:26 ` [PATCH v2 2/8] ppc/spapr: Change FWNMI names Nicholas Piggin
2020-03-16 17:15 ` Greg Kurz
2020-03-16 17:18 ` Mahesh J Salgaonkar
2020-03-16 17:25 ` Greg Kurz
2020-03-16 17:32 ` Cédric Le Goater
2020-03-16 22:46 ` David Gibson
2020-03-16 14:26 ` [PATCH v2 3/8] ppc/spapr: Add FWNMI System Reset state Nicholas Piggin
2020-03-16 17:17 ` Greg Kurz
2020-03-16 17:29 ` Mahesh J Salgaonkar
2020-03-16 17:46 ` Cédric Le Goater
2020-03-16 22:47 ` David Gibson
2020-03-16 14:26 ` [PATCH v2 4/8] ppc/spapr: Fix FWNMI machine check interrupt delivery Nicholas Piggin
2020-03-16 17:59 ` Cédric Le Goater
2020-03-16 23:19 ` Nicholas Piggin
2020-03-16 23:27 ` David Gibson
2020-03-16 14:26 ` [PATCH v2 5/8] ppc/spapr: Allow FWNMI on TCG Nicholas Piggin
2020-03-16 18:00 ` Cédric Le Goater
2020-03-16 18:01 ` Greg Kurz
2020-03-16 23:26 ` Nicholas Piggin
2020-03-17 3:56 ` David? Gibson
2020-03-16 14:26 ` [PATCH v2 6/8] target/ppc: allow ppc_cpu_do_system_reset to take an alternate vector Nicholas Piggin
2020-03-16 18:04 ` Greg Kurz
2020-03-16 18:15 ` Cédric Le Goater
2020-03-16 23:28 ` Nicholas Piggin
2020-03-16 23:34 ` David Gibson
2020-03-17 10:47 ` Cédric Le Goater
2020-03-16 23:28 ` David Gibson
2020-03-16 14:26 ` [PATCH v2 7/8] ppc/spapr: Implement FWNMI System Reset delivery Nicholas Piggin
2020-03-16 17:35 ` Mahesh J Salgaonkar
2020-03-16 17:52 ` Greg Kurz [this message]
2020-03-16 23:31 ` David Gibson
2020-03-16 23:30 ` David Gibson
2020-03-16 14:26 ` [PATCH v2 8/8] ppc/spapr: Ignore common "ibm, nmi-interlock" Linux bug Nicholas Piggin
2020-03-16 23:32 ` [PATCH v2 8/8] ppc/spapr: Ignore common "ibm,nmi-interlock" " 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=20200316185254.1aca6e20@bahia.lan \
--to=groug@kaod.org \
--cc=aik@ozlabs.ru \
--cc=arawinda.p@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=ganeshgr@linux.ibm.com \
--cc=mahesh@linux.vnet.ibm.com \
--cc=npiggin@gmail.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).