qemu-arm
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v25 00/10] Add ARMv8 RAS virtualization support in QEMU


From: Michael S. Tsirkin
Subject: Re: [PATCH v25 00/10] Add ARMv8 RAS virtualization support in QEMU
Date: Wed, 6 May 2020 16:25:41 -0400

On Wed, May 06, 2020 at 07:42:19PM +0800, gengdongjiu wrote:
> On 2020/4/17 21:32, Peter Maydell wrote:
> > On Fri, 10 Apr 2020 at 12:46, Dongjiu Geng <address@hidden> wrote:
> >>
> >> In the ARMv8 platform, the CPU error types includes synchronous external 
> >> abort(SEA)
> >> and SError Interrupt (SEI). If exception happens in guest, host does not 
> >> know the detailed
> >> information of guest, so it is expected that guest can do the recovery. 
> >> For example, if an
> >> exception happens in a guest user-space application, host does not know 
> >> which application
> >> encounters errors, only guest knows it.
> >>
> >> For the ARMv8 SEA/SEI, KVM or host kernel delivers SIGBUS to notify 
> >> userspace.
> >> After user space gets the notification, it will record the CPER into guest 
> >> GHES
> >> buffer and inject an exception or IRQ to guest.
> >>
> >> In the current implementation, if the type of SIGBUS is BUS_MCEERR_AR, we 
> >> will
> >> treat it as a synchronous exception, and notify guest with ARMv8 SEA
> >> notification type after recording CPER into guest.
> > 
> > Hi. I left a comment on patch 1. The other 3 patches unreviewed
> > are 5, 6 and 8, which are all ACPI core code, so that's for
> > MST, Igor or Shannon to review.
> > 
> > Once those have been reviewed, please ping me if you want this
> > to go via target-arm.next.
> 
> Hi Peter,
>    Igor have reviewed all ACPI core code. whether you can apply this series 
> to target-arm.next I can make another patches to solve your comments on 
> patch1 and another APCI comment.
> Thanks very much in advance.

Given it all starts with patch 1, it's probably easier to address the
comment and repost.


> > 
> > thanks
> > -- PMM
> > 
> > .
> > 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]