From: Aravinda Prasad <aravinda@linux.vnet.ibm.com> To: Fabiano Rosas <farosas@linux.ibm.com> Cc: aik@au1.ibm.com, mahesh@linux.vnet.ibm.com, qemu-devel@nongnu.org, paulus@ozlabs.org, qemu-ppc@nongnu.org, david@gibson.dropbear.id.au Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v8 4/6] target/ppc: Build rtas error log upon an MCE Date: Wed, 24 Apr 2019 10:21:50 +0530 [thread overview] Message-ID: <a1e59aa3-f596-abbd-8365-3a12293d85e8@linux.vnet.ibm.com> (raw) In-Reply-To: <875zr43hxj.fsf@linux.ibm.com> On Tuesday 23 April 2019 08:08 PM, Fabiano Rosas wrote: > Aravinda Prasad <aravinda@linux.vnet.ibm.com> writes: > >> + /* >> + * Properly set bits in MSR before we invoke the handler. >> + * SRR0/1, DAR and DSISR are properly set by KVM >> + */ >> + if (!(*pcc->interrupts_big_endian)(cpu)) { >> + msr |= (1ULL << MSR_LE); >> + } >> + >> + if (env->msr && (1ULL << MSR_SF)) { > > Don't you mean & instead of &&? Ah.. yes.. Thanks for pointing out. > >> + msr |= (1ULL << MSR_SF); >> + } > > -- Regards, Aravinda
WARNING: multiple messages have this Message-ID (diff)
From: Aravinda Prasad <aravinda@linux.vnet.ibm.com> To: Fabiano Rosas <farosas@linux.ibm.com> Cc: aik@au1.ibm.com, qemu-devel@nongnu.org, paulus@ozlabs.org, qemu-ppc@nongnu.org, david@gibson.dropbear.id.au Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v8 4/6] target/ppc: Build rtas error log upon an MCE Date: Wed, 24 Apr 2019 10:21:50 +0530 [thread overview] Message-ID: <a1e59aa3-f596-abbd-8365-3a12293d85e8@linux.vnet.ibm.com> (raw) Message-ID: <20190424045150.YzgYwZ6ryrCCXKJCtY1-K4CAmfTqDb4Tp3jmVSPubPI@z> (raw) In-Reply-To: <875zr43hxj.fsf@linux.ibm.com> On Tuesday 23 April 2019 08:08 PM, Fabiano Rosas wrote: > Aravinda Prasad <aravinda@linux.vnet.ibm.com> writes: > >> + /* >> + * Properly set bits in MSR before we invoke the handler. >> + * SRR0/1, DAR and DSISR are properly set by KVM >> + */ >> + if (!(*pcc->interrupts_big_endian)(cpu)) { >> + msr |= (1ULL << MSR_LE); >> + } >> + >> + if (env->msr && (1ULL << MSR_SF)) { > > Don't you mean & instead of &&? Ah.. yes.. Thanks for pointing out. > >> + msr |= (1ULL << MSR_SF); >> + } > > -- Regards, Aravinda
next prev parent reply other threads:[~2019-04-24 4:56 UTC|newest] Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-22 7:02 [Qemu-devel] [PATCH v8 0/6] target-ppc/spapr: Add FWNMI support in QEMU for PowerKVM guests Aravinda Prasad 2019-04-22 7:02 ` Aravinda Prasad 2019-04-22 7:02 ` [Qemu-devel] [PATCH v8 1/6] ppc: spapr: Handle "ibm, nmi-register" and "ibm, nmi-interlock" RTAS calls Aravinda Prasad 2019-04-22 7:02 ` Aravinda Prasad 2019-04-23 6:45 ` David Gibson 2019-04-23 6:45 ` David Gibson 2019-04-25 4:56 ` Aravinda Prasad 2019-04-25 4:56 ` Aravinda Prasad 2019-05-10 9:06 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz 2019-05-10 9:54 ` David Gibson 2019-05-10 14:33 ` Greg Kurz 2019-05-13 4:57 ` Aravinda Prasad 2019-05-13 4:53 ` Aravinda Prasad 2019-04-22 7:03 ` [Qemu-devel] [PATCH v8 2/6] Wrapper function to wait on condition for the main loop mutex Aravinda Prasad 2019-04-22 7:03 ` Aravinda Prasad 2019-04-23 6:47 ` David Gibson 2019-04-23 6:47 ` David Gibson 2019-05-10 13:14 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz 2019-04-22 7:03 ` [Qemu-devel] [PATCH v8 3/6] target/ppc: Handle NMI guest exit Aravinda Prasad 2019-04-22 7:03 ` Aravinda Prasad 2019-04-23 6:53 ` David Gibson 2019-04-23 6:53 ` David Gibson 2019-04-24 4:50 ` [Qemu-devel] [Qemu-ppc] " Aravinda Prasad 2019-04-24 4:50 ` Aravinda Prasad 2019-05-10 6:37 ` David Gibson 2019-05-10 6:58 ` Aravinda Prasad 2019-05-10 16:25 ` Greg Kurz 2019-05-13 5:40 ` Aravinda Prasad 2019-05-13 5:56 ` David Gibson 2019-04-22 7:03 ` [Qemu-devel] [PATCH v8 4/6] target/ppc: Build rtas error log upon an MCE Aravinda Prasad 2019-04-22 7:03 ` Aravinda Prasad 2019-04-23 14:38 ` Fabiano Rosas 2019-04-23 14:38 ` Fabiano Rosas 2019-04-24 4:51 ` Aravinda Prasad [this message] 2019-04-24 4:51 ` [Qemu-devel] [Qemu-ppc] " Aravinda Prasad 2019-05-10 6:42 ` [Qemu-devel] " David Gibson 2019-05-10 7:05 ` Aravinda Prasad 2019-05-10 9:52 ` David Gibson 2019-05-13 5:00 ` Aravinda Prasad 2019-05-13 11:30 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz 2019-05-14 0:08 ` David Gibson 2019-05-14 4:26 ` Aravinda Prasad 2019-05-14 4:40 ` David Gibson 2019-05-14 5:06 ` Aravinda Prasad 2019-05-16 1:47 ` David Gibson 2019-05-16 4:54 ` Aravinda Prasad 2019-04-22 7:03 ` [Qemu-devel] [PATCH v8 5/6] ppc: spapr: Enable FWNMI capability Aravinda Prasad 2019-04-22 7:03 ` Aravinda Prasad 2019-05-10 6:46 ` David Gibson 2019-05-10 7:15 ` [Qemu-devel] [Qemu-ppc] " Aravinda Prasad 2019-05-10 9:53 ` David Gibson 2019-05-13 10:30 ` Aravinda Prasad 2019-05-14 4:47 ` David Gibson 2019-05-14 5:32 ` Aravinda Prasad 2019-05-16 1:45 ` David Gibson 2019-05-16 4:59 ` Aravinda Prasad 2019-04-22 7:03 ` [Qemu-devel] [PATCH v8 6/6] migration: Block migration while handling machine check Aravinda Prasad 2019-04-22 7:03 ` Aravinda Prasad 2019-05-10 6:51 ` David Gibson 2019-05-10 7:16 ` Aravinda Prasad 2019-05-29 5:46 ` [Qemu-devel] [Qemu-ppc] " Aravinda Prasad 2019-05-16 10:54 ` Greg Kurz 2019-05-16 10:59 ` Aravinda Prasad 2019-05-16 14:17 ` Dr. David Alan Gilbert 2019-05-20 5:57 ` Aravinda Prasad
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=a1e59aa3-f596-abbd-8365-3a12293d85e8@linux.vnet.ibm.com \ --to=aravinda@linux.vnet.ibm.com \ --cc=aik@au1.ibm.com \ --cc=david@gibson.dropbear.id.au \ --cc=farosas@linux.ibm.com \ --cc=mahesh@linux.vnet.ibm.com \ --cc=paulus@ozlabs.org \ --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: linkBe 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).