From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Maydell Subject: Re: [PATCH v5 02/22] KVM: arm/arm64: Add GICV3 pending table save API documentation Date: Wed, 26 Apr 2017 14:01:55 +0100 Message-ID: References: <1492164934-988-1-git-send-email-eric.auger@redhat.com> <1492164934-988-3-git-send-email-eric.auger@redhat.com> <20170426084830.GB2098@work-vm> <4dc866a0-582c-af69-916f-eb435988b5ec@redhat.com> <20170426130020.GM4104@cbox> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "prasun.kapoor" , kvm-devel , Juan Quintela , Marc Zyngier , Andre Przywara , "Dr. David Alan Gilbert" , Vijaya Kumar K , "Kumar, Vijaya" , arm-mail-list , Paolo Bonzini , "kvmarm@lists.cs.columbia.edu" , eric.auger.pro@gmail.com To: Christoffer Dall Return-path: In-Reply-To: <20170426130020.GM4104@cbox> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu List-Id: kvm.vger.kernel.org On 26 April 2017 at 14:00, Christoffer Dall wrote: > Alternatively we should mark a pending error notification to the guest > in KVM, so that when the guest boots it gets something like an SError > instead, given that presumably the guest wrote the weird value. Except > of course if the problem is caused by QEMU fudging with the register > value for the PENDBASER. If we have scope for complaining at the guest we should do it at the point where the guest sets PENDBASER in the first place... thanks -- PMM From mboxrd@z Thu Jan 1 00:00:00 1970 From: peter.maydell@linaro.org (Peter Maydell) Date: Wed, 26 Apr 2017 14:01:55 +0100 Subject: [PATCH v5 02/22] KVM: arm/arm64: Add GICV3 pending table save API documentation In-Reply-To: <20170426130020.GM4104@cbox> References: <1492164934-988-1-git-send-email-eric.auger@redhat.com> <1492164934-988-3-git-send-email-eric.auger@redhat.com> <20170426084830.GB2098@work-vm> <4dc866a0-582c-af69-916f-eb435988b5ec@redhat.com> <20170426130020.GM4104@cbox> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 26 April 2017 at 14:00, Christoffer Dall wrote: > Alternatively we should mark a pending error notification to the guest > in KVM, so that when the guest boots it gets something like an SError > instead, given that presumably the guest wrote the weird value. Except > of course if the problem is caused by QEMU fudging with the register > value for the PENDBASER. If we have scope for complaining at the guest we should do it at the point where the guest sets PENDBASER in the first place... thanks -- PMM