On Thu, Apr 23, 2015 at 06:00:15PM +0000, Luck, Tony wrote:
> > I think we should apply this.
> >
> > Here's why: nothing in the ghes_notify_nmi() handler does CPU-specific
> > accesses
>
> This looks to be true.
>
> > Tony, objections?
>
> No objections.
Thanks, queued for 4.2, pending one last test I'm doing on a machine
which says
[ 24.332560] INFO: NMI handler (ghes_notify_nmi) took too long to run: 3.265
msecs
[ 24.332567] INFO: NMI handler (ghes_notify_nmi) took too long to run: 5.946
msecs
[ 24.332568] INFO: NMI handler (ghes_notify_nmi) took too long to run: 5.948
msecs
during boot.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
