On 09/15, James Morse wrote:
> On 15/09/17 02:19, Stephen Boyd wrote:
> > From what I can see there isn't anything about ACPI_APEI_SEA that
> > means the arm64 architecture can or cannot support NMI safe
> > cmpxchg, so the if condition here is not important.
>
> Yup, it was to match 'HAVE_NMI',
On 09/15, James Morse wrote:
> On 15/09/17 02:19, Stephen Boyd wrote:
> > From what I can see there isn't anything about ACPI_APEI_SEA that
> > means the arm64 architecture can or cannot support NMI safe
> > cmpxchg, so the if condition here is not important.
>
> Yup, it was to match 'HAVE_NMI',
Hi Stephen,
On 15/09/17 02:19, Stephen Boyd wrote:
> From what I can see there isn't anything about ACPI_APEI_SEA that
> means the arm64 architecture can or cannot support NMI safe
> cmpxchg, so the if condition here is not important.
Yup, it was to match 'HAVE_NMI', which was new with
Hi Stephen,
On 15/09/17 02:19, Stephen Boyd wrote:
> From what I can see there isn't anything about ACPI_APEI_SEA that
> means the arm64 architecture can or cannot support NMI safe
> cmpxchg, so the if condition here is not important.
Yup, it was to match 'HAVE_NMI', which was new with
>From what I can see there isn't anything about ACPI_APEI_SEA that
means the arm64 architecture can or cannot support NMI safe
cmpxchg, so the if condition here is not important. Let's remove
it. Doing that allows us to support ftrace histograms via
CONFIG_HIST_TRIGGERS that depends on the arch
>From what I can see there isn't anything about ACPI_APEI_SEA that
means the arm64 architecture can or cannot support NMI safe
cmpxchg, so the if condition here is not important. Let's remove
it. Doing that allows us to support ftrace histograms via
CONFIG_HIST_TRIGGERS that depends on the arch
6 matches
Mail list logo
