From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] spapr: Define NMI interface
Date: Fri, 28 Mar 2014 00:14:22 +1100 [thread overview]
Message-ID: <5334242E.1010806@ozlabs.ru> (raw)
In-Reply-To: <53341281.8090907@redhat.com>
On 03/27/2014 10:58 PM, Paolo Bonzini wrote:
> Il 27/03/2014 03:21, Alexey Kardashevskiy ha scritto:
>> This defines and makes use of an NMI interface in order to support
>> the "nmi" command.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>> hw/ppc/spapr.c | 26 ++++++++++++++++++++++++++
>> 1 file changed, 26 insertions(+)
>>
>> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
>> index 62ddb4d..495fa88 100644
>> --- a/hw/ppc/spapr.c
>> +++ b/hw/ppc/spapr.c
>> @@ -48,6 +48,7 @@
>> #include "hw/pci/pci.h"
>> #include "hw/scsi/scsi.h"
>> #include "hw/virtio/virtio-scsi.h"
>> +#include "hw/nmi.h"
>>
>> #include "exec/address-spaces.h"
>> #include "hw/usb.h"
>> @@ -1539,13 +1540,36 @@ static char *spapr_get_fw_dev_path(FWPathProvider
>> *p, BusState *bus,
>> return NULL;
>> }
>>
>> +static void spapr_do_nmi(void *arg)
>> +{
>> + CPUState *cs = arg;
>> + PowerPCCPU *cpu = POWERPC_CPU(cs);
>> + CPUPPCState *env = &cpu->env;
>> +
>> + cpu_synchronize_state(cs);
>> + env->spr[SPR_SRR0] = env->nip;
>> + env->spr[SPR_SRR1] = env->msr;
>> + env->nip = 0x100;
>> + env->msr = (1ULL << MSR_SF) | (1 << MSR_ME);
>> + if (env->spr[SPR_LPCR] & LPCR_ILE) {
>> + env->msr |= 1 << MSR_LE;
>> + }
>> +}
>
>
> I think an interface isn't the right tool here. You want a method in
> CPUClass, and you also should move the existing code for x86 and s390 to
> target-i386 and target-s390.
I can do that, no big deal (bit afraid there will be some third approach
then :) ), but
1) how many x86 CPUs/families are there to support? On ppc I'll add it for
POWER7/7+/8 families and I am ok.
2) what should "nmi" really do - deliver NMI to the current CPU (as s390
does) or on all CPUs (as x86 does)?
--
Alexey
next prev parent reply other threads:[~2014-03-27 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 2:21 [Qemu-devel] [PATCH 0/2] nmi: add interface Alexey Kardashevskiy
2014-03-27 2:21 ` [Qemu-devel] [PATCH 1/2] spapr: Add NMI interface Alexey Kardashevskiy
2014-03-27 2:21 ` [Qemu-devel] [PATCH 2/2] spapr: Define " Alexey Kardashevskiy
2014-03-27 11:58 ` Paolo Bonzini
2014-03-27 13:14 ` Alexey Kardashevskiy [this message]
2014-03-27 14:06 ` Paolo Bonzini
2014-03-27 13:54 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
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=5334242E.1010806@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=pbonzini@redhat.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 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.