Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

James, Thanks for this mail. On 2018/4/13 0:14, James Morse wrote: > Hi gengdongjiu, > > On 12/04/18 06:00, gengdongjiu wrote: >> 2018-02-16 1:55 GMT+08:00 James Morse : >>> On 05/02/18 11:24, gengdongjiu wrote: > Is the emulated SError routed following the routing

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

Hi gengdongjiu, On 12/04/18 06:00, gengdongjiu wrote: > 2018-02-16 1:55 GMT+08:00 James Morse : >> On 05/02/18 11:24, gengdongjiu wrote: Is the emulated SError routed following the routing rules for HCR_EL2.{AMO, TGE}? >>> >>> Yes, it is. >> >> ... and yet ... >> >>

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

Dear James, Thanks for this mail and sorry for my late response. 2018-02-16 1:55 GMT+08:00 James Morse : > Hi gengdongjiu, liu jun > > On 05/02/18 11:24, gengdongjiu wrote: [] >> >>> Is the emulated SError routed following the routing rules for HCR_EL2.{AMO, >>>

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

Hi gengdongjiu, liu jun On 05/02/18 11:24, gengdongjiu wrote: > James Morse wrote: >> I'd like to pick these patches onto the end of that series, but first I want >> to >> know what NOTIFY_SEI means for any OS. The ACPI spec doesn't say, and >> because its asynchronous, route-able and mask-able,

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

[...] > > > Yes, I know you are dong that. Your serial's patch will consider all above > things, right? > > Assuming I got it right, yes. It currently makes the race Xie XiuQi spotted > worse, > which I want to fix too. (details on the cover letter) Ok. > > > > If your patch can be consider

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

Hi gengdongjiu, On 23/01/18 09:23, gengdongjiu wrote: > On 2018/1/23 3:39, James Morse wrote: >> gengdongjiu wrote: >>> This error source parsing and handling method >>> is similar with the SEA. >> >> There are problems with doing this: >> >> Oct. 18, 2017, 10:26 a.m. James Morse wrote: >> | How

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

sorry fix a typo. On 2018/1/23 17:23, gengdongjiu wrote: >> There are problems with doing this: >> >> Oct. 18, 2017, 10:26 a.m. James Morse wrote: >> | How do SEA and SEI interact? >> | >> | As far as I can see they can both interrupt each other, which isn't >> something >> | the single in_nmi()

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

Hi James, On 2018/1/23 3:39, James Morse wrote: > Hi Dongjiu Geng, > > (versions of patches 1,2 and 4 have been queued by Catalin) > > (Nit 'ACPI / APEI:' is the normal subject prefix for ghes.c, this helps the > maintainers know which patches they need to pay attention to when you are >

Re: [PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

Hi Dongjiu Geng, (versions of patches 1,2 and 4 have been queued by Catalin) (Nit 'ACPI / APEI:' is the normal subject prefix for ghes.c, this helps the maintainers know which patches they need to pay attention to when you are touching multiple trees) On 06/01/18 16:02, Dongjiu Geng wrote: >

[PATCH v9 3/7] acpi: apei: Add SEI notification type support for ARMv8

ARMv8.2 requires implementation of the RAS extension. In this extension, it adds SEI(SError Interrupt) notification type, this patch adds new GHES error source SEI handling functions. This error source parsing and handling method is similar with the SEA. Expose API ghes_notify_sei() to external