From: Daniel Axtens <dja@axtens•net>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: Aravinda Prasad <aravinda@linux•vnet.ibm.com>,
paulus@ozlabs•org, linuxppc-dev@ozlabs•org,
kvm-ppc@vger•kernel.org, mahesh@linux•vnet.ibm.com,
agraf@suse•de, michaele@au1•ibm.com, kvm@vger•kernel.org
Subject: Re: [PATCH] KVM: PPC: Exit guest upon fatal machine check exception
Date: Thu, 12 Nov 2015 15:58:14 +1100 [thread overview]
Message-ID: <87bnazizkp.fsf@gamma.ozlabs.ibm.com> (raw)
In-Reply-To: <20151112033816.GJ5852@voom.redhat.com>
> So, IIUC. Once the qemu pieces are in place as well it shouldn't
> change this behaviour: KVM will exit to qemu, qemu will log the error
> information (new), then reinject the MC to the guest which can still
> handle it as you describe above.
Ah, that makes *much* more sense now! Thanks for the explanation: I
don't really follow qemu development.
>
> But, there could be a problem if you have a new kernel with an old
> qemu, in that case qemu might not understand the new exit type and
> treat it as a fatal error, even though the guest could actually cope
> with it.
>
> Aravinda, do we need to change this so that qemu has to explicitly
> enable the new NMI behaviour? Or have I missed something that will
> make that case work already.
<puts on CAPI hat>Yeah, it would be good not to break this.</hat>
Regards,
Daniel
> --
> David Gibson | I'll have my music baroque, and my code
> david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
> | _way_ _around_!
> http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2015-11-12 4:58 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 [this message]
2015-11-12 17:22 ` Aravinda Prasad
2015-11-12 21:37 ` Daniel Axtens
2015-11-13 4:58 ` Aravinda Prasad
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=87bnazizkp.fsf@gamma.ozlabs.ibm.com \
--to=dja@axtens$(echo .)net \
--cc=agraf@suse$(echo .)de \
--cc=aravinda@linux$(echo .)vnet.ibm.com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=kvm-ppc@vger$(echo .)kernel.org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mahesh@linux$(echo .)vnet.ibm.com \
--cc=michaele@au1$(echo .)ibm.com \
--cc=paulus@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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