From: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: gleb@kernel.org, agraf@suse.de, kvm-ppc@vger.kernel.org,
linuxppc-dev@ozlabs.org, pbonzini@redhat.com,
mahesh@linux.vnet.ibm.com, david@gibson.dropbear.id.au,
kvm@vger.kernel.org, mpe@ellerman.id.au
Subject: Re: [PATCH v3 2/2] KVM: PPC: Exit guest upon MCE when FWNMI capability is enabled
Date: Tue, 21 Jun 2016 21:13:27 +0000 [thread overview]
Message-ID: <5769AB27.7040604@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160620051853.GA29366@fergus.ozlabs.ibm.com>
On Monday 20 June 2016 10:48 AM, Paul Mackerras wrote:
> Hi Aravinda,
>
> On Wed, Jan 13, 2016 at 12:38:09PM +0530, Aravinda Prasad wrote:
>> Enhance KVM to cause a guest exit with KVM_EXIT_NMI
>> exit reasons upon a machine check exception (MCE) in
>> the guest address space if the KVM_CAP_PPC_FWNMI
>> capability is enabled (instead of delivering 0x200
>> interrupt to guest). This enables QEMU to build error
>> log and deliver machine check exception to guest via
>> guest registered machine check handler.
>>
>> This approach simplifies the delivering of machine
>> check exception to guest OS compared to the earlier
>> approach of KVM directly invoking 0x200 guest interrupt
>> vector. In the earlier approach QEMU was enhanced to
>> patch the 0x200 interrupt vector during boot. The
>> patched code at 0x200 issued a private hcall to pass
>> the control to QEMU to build the error log.
>>
>> This design/approach is based on the feedback for the
>> QEMU patches to handle machine check exception. Details
>> of earlier approach of handling machine check exception
>> in QEMU and related discussions can be found at:
>>
>> https://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg00813.html
>>
>> Signed-off-by: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
>
> Are you in the process of doing a new version of this patch with the
> requested changes?
Yes, I am working (intermittently) on the new version. But, not able to
finish off and post it. Will complete it and post the new version.
Regards,
Aravinda
>
> Paul.
>
--
Regards,
Aravinda
WARNING: multiple messages have this Message-ID (diff)
From: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: gleb@kernel.org, agraf@suse.de, kvm-ppc@vger.kernel.org,
linuxppc-dev@ozlabs.org, pbonzini@redhat.com,
mahesh@linux.vnet.ibm.com, david@gibson.dropbear.id.au,
kvm@vger.kernel.org, mpe@ellerman.id.au
Subject: Re: [PATCH v3 2/2] KVM: PPC: Exit guest upon MCE when FWNMI capability is enabled
Date: Wed, 22 Jun 2016 02:31:27 +0530 [thread overview]
Message-ID: <5769AB27.7040604@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160620051853.GA29366@fergus.ozlabs.ibm.com>
On Monday 20 June 2016 10:48 AM, Paul Mackerras wrote:
> Hi Aravinda,
>
> On Wed, Jan 13, 2016 at 12:38:09PM +0530, Aravinda Prasad wrote:
>> Enhance KVM to cause a guest exit with KVM_EXIT_NMI
>> exit reasons upon a machine check exception (MCE) in
>> the guest address space if the KVM_CAP_PPC_FWNMI
>> capability is enabled (instead of delivering 0x200
>> interrupt to guest). This enables QEMU to build error
>> log and deliver machine check exception to guest via
>> guest registered machine check handler.
>>
>> This approach simplifies the delivering of machine
>> check exception to guest OS compared to the earlier
>> approach of KVM directly invoking 0x200 guest interrupt
>> vector. In the earlier approach QEMU was enhanced to
>> patch the 0x200 interrupt vector during boot. The
>> patched code at 0x200 issued a private hcall to pass
>> the control to QEMU to build the error log.
>>
>> This design/approach is based on the feedback for the
>> QEMU patches to handle machine check exception. Details
>> of earlier approach of handling machine check exception
>> in QEMU and related discussions can be found at:
>>
>> https://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg00813.html
>>
>> Signed-off-by: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
>
> Are you in the process of doing a new version of this patch with the
> requested changes?
Yes, I am working (intermittently) on the new version. But, not able to
finish off and post it. Will complete it and post the new version.
Regards,
Aravinda
>
> Paul.
>
--
Regards,
Aravinda
next prev parent reply other threads:[~2016-06-21 21:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 7:07 [PATCH v3 1/2] KVM: PPC: New capability to control MCE behaviour Aravinda Prasad
2016-01-13 7:19 ` Aravinda Prasad
2016-01-13 7:08 ` [PATCH v3 2/2] KVM: PPC: Exit guest upon MCE when FWNMI capability is enabled Aravinda Prasad
2016-01-13 7:20 ` Aravinda Prasad
2016-01-14 0:06 ` David Gibson
2016-01-14 0:06 ` David Gibson
2016-01-23 10:28 ` Paul Mackerras
2016-01-23 10:28 ` Paul Mackerras
2016-01-23 12:53 ` Aravinda Prasad
2016-01-23 12:53 ` Aravinda Prasad
2016-01-23 21:24 ` Paul Mackerras
2016-01-23 21:24 ` Paul Mackerras
2016-01-23 21:24 ` Paul Mackerras
2016-01-25 8:39 ` Aravinda Prasad
2016-01-25 8:51 ` Aravinda Prasad
2016-01-27 5:02 ` Mahesh Jagannath Salgaonkar
2016-01-27 5:14 ` Mahesh Jagannath Salgaonkar
2016-01-27 5:02 ` Mahesh Jagannath Salgaonkar
2016-06-20 5:18 ` Paul Mackerras
2016-06-20 5:18 ` Paul Mackerras
2016-06-20 5:18 ` Paul Mackerras
2016-06-21 21:01 ` Aravinda Prasad [this message]
2016-06-21 21:13 ` Aravinda Prasad
2016-01-14 0:02 ` [PATCH v3 1/2] KVM: PPC: New capability to control MCE behaviour David Gibson
2016-01-14 0:02 ` David Gibson
2016-01-14 0:05 ` David Gibson
2016-01-14 0:05 ` David Gibson
2016-01-23 10:20 ` Paul Mackerras
2016-01-23 10:20 ` Paul Mackerras
2016-01-23 12:28 ` Aravinda Prasad
2016-01-23 12:40 ` 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=5769AB27.7040604@linux.vnet.ibm.com \
--to=aravinda@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=gleb@kernel.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.com \
/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.