Re: [RFC PATCH V2] kvm: arm64: export memory error recovery capability to user space

2019-05-13 Thread Peter Maydell
r space. > > Cc: Peter Maydell > Signed-off-by: Dongjiu Geng > --- > v1->v2: > 1. check whether host support memory failure instead of RAS capability >https://patchwork.kernel.org/patch/10730827/ > > v1: > 1. User space needs to check this capability of host i

Re: [RFC RESEND PATCH] kvm: arm64: export memory error recovery capability to user space

2019-01-10 Thread Peter Maydell
On Thu, 10 Jan 2019 at 12:09, gengdongjiu wrote: > Peter, I summarize James's main idea, James think QEMU does not needs > to check *something* if Qemu support firmware-first. > What do we do for your comments? Unless I'm missing something, the code in your most recent patchset attempts to update

Re: [RFC RESEND PATCH] kvm: arm64: export memory error recovery capability to user space

2018-12-19 Thread Peter Maydell
On Mon, 17 Dec 2018 at 15:56, James Morse wrote: > I think the root issue here is the name of the cpufeature 'RAS Extensions', > this > doesn't mean RAS is new, or even requires these features. It's just > standardised > records, classification and a barrier. > Not only is it possible to build a

Re: [RFC RESEND PATCH] kvm: arm64: export memory error recovery capability to user space

2018-12-14 Thread Peter Maydell
On Fri, 14 Dec 2018 at 13:56, James Morse wrote: > > Hi Dongjiu Geng, > > On 14/12/2018 10:15, Dongjiu Geng wrote: > > When user space do memory recovery, it will check whether KVM and > > guest support the error recovery, only when both of them support, > > user space will do the error recovery.