[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH 04/13] ppc/spapr: Disable FWNMI capability if KVM does no
|
From: |
Nicholas Piggin |
|
Subject: |
Re: [RFC PATCH 04/13] ppc/spapr: Disable FWNMI capability if KVM does not support it |
|
Date: |
Thu, 05 Mar 2020 13:51:40 +1000 |
|
User-agent: |
astroid/0.15.0 (https://github.com/astroidmail/astroid) |
David Gibson's on March 4, 2020 3:57 pm:
> On Wed, Mar 04, 2020 at 03:28:41PM +1000, Nicholas Piggin wrote:
>> This is a fatal error if KVM does not support this capability, so try to
>> disable it if that's the case.
>
> Nack.
>
> Changing the guest visible environment based on host capabilities
> totally breaks the migration model. If the user has requested an
> environment the host can't provide, we have to outright fail instead.
Okay. How are these capabilities requested, do you tend to default on
and pass the cap-flag=off parameter?
Thanks,
Nick
- Re: [RFC PATCH 01/13] ppc/spapr: Change FWNMI names, (continued)
[RFC PATCH 05/13] ppc/spapr: Fix FWNMI machine check interrupt delivery, Nicholas Piggin, 2020/03/04
[RFC PATCH 06/13] ppc/spapr: Fix FWNMI machine check failure handling, Nicholas Piggin, 2020/03/04
[RFC PATCH 09/13] ppc/spapr: Don't kill the guest if a recovered FWNMI machine check delivery fails, Nicholas Piggin, 2020/03/04
[RFC PATCH 07/13] ppc/spapr: Improve FWNMI machine check delivery corner case comments, Nicholas Piggin, 2020/03/04
[RFC PATCH 08/13] ppc/spapr: Add FWNMI machine check delivery warnings, Nicholas Piggin, 2020/03/04