From: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
To: Daniel Axtens <dja@axtens.net>
Cc: David Gibson <david@gibson.dropbear.id.au>,
kvm@vger.kernel.org, michaele@au1.ibm.com,
mahesh@linux.vnet.ibm.com, agraf@suse.de,
kvm-ppc@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] KVM: PPC: Exit guest upon fatal machine check exception
Date: Fri, 13 Nov 2015 10:28:52 +0530 [thread overview]
Message-ID: <56456E0C.1040909@linux.vnet.ibm.com> (raw)
In-Reply-To: <87pozezypm.fsf@gamma.ozlabs.ibm.com>
On Friday 13 November 2015 03:07 AM, Daniel Axtens wrote:
> Aravinda Prasad <aravinda@linux.vnet.ibm.com> writes:
>
>>> <puts on CAPI hat>Yeah, it would be good not to break this.</hat>
>>
>> I am not familiar with CAPI. Does this affect CAPI?
>
> When a CAPI card experiences an EEH event, any cache lines it holds are
> filled with SUEs (Special UEs, interpreted by the kernel the same as
> regular UEs). When these are read, we get an MCE. Currently CAPI does
> not support virtualisation, but that is actively being worked
> on. There's a _very_ good chance it will then be backported to various
> distros, which could have old qemu.
>
> Therefore, I'd ideally like to make sure UEs in KVM guests work properly
> and continue to do so in all combinations of kernel and qemu. I'm
> following up the email from Mahesh that you linked: I'm not sure I quite
> follow his logic so I'll try to make sense of that and then get back to
> you.
sure. Thanks.
Regards,
Aravinda
>
> Regards,
> Daniel
>
--
Regards,
Aravinda
next prev parent reply other threads:[~2015-11-13 4:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 16:58 [PATCH] KVM: PPC: Exit guest upon fatal machine check exception Aravinda Prasad
2015-11-12 2:24 ` Daniel Axtens
2015-11-12 3:38 ` David Gibson
2015-11-12 4:32 ` Aravinda Prasad
2015-11-12 4:43 ` David Gibson
2015-11-12 17:52 ` Aravinda Prasad
2015-11-13 1:50 ` David Gibson
2015-11-13 6:26 ` Aravinda Prasad
2015-11-13 7:38 ` Thomas Huth
2015-11-13 11:25 ` Aravinda Prasad
2015-11-12 4:58 ` Daniel Axtens
2015-11-12 17:22 ` Aravinda Prasad
2015-11-12 21:37 ` Daniel Axtens
2015-11-13 4:58 ` Aravinda Prasad [this message]
2015-11-12 3:34 ` David Gibson
2015-11-12 5:18 ` 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=56456E0C.1040909@linux.vnet.ibm.com \
--to=aravinda@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=dja@axtens.net \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=michaele@au1.ibm.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 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).