linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC v2] apei: Add ACPI APEI event notification support
Date: Thu, 19 Nov 2015 16:51:58 +0100	[thread overview]
Message-ID: <20151119155158.GE6065@pd.tnic> (raw)
In-Reply-To: <F77E0D1A-FE01-4BA8-B72C-AA6CB7DAD61C@redhat.com>

On Thu, Nov 19, 2015 at 10:05:16AM -0500, Jon Masters wrote:
> Top post - quick reply - you are correct. This is a vendor specific
> implementation. APEI is generic, and in the general case there should
> not be a need to do anything with a special driver. Some will need
> their own special solution in the early days, but everyone else should
> be able to go generic. In particular I expect those implementing EL3
> to do firmware first handling and to signal the event independently of
> any OS specific hooks.

In the meantime, I got these two patches:

https://lkml.kernel.org/r/1446857519-5908-1-git-send-email-lho at apm.com

which makes the GHES IRQ shared and, apparently solves the issue for
APM.

I'd appreciate it if you guys took a look.

Thanks!

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

  reply	other threads:[~2015-11-19 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 20:14 [PATCH RFC v2] apei: Add ACPI APEI event notification support Loc Ho
2015-10-22  9:57 ` Borislav Petkov
2015-10-23  0:21   ` Loc Ho
2015-11-19 14:18   ` Will Deacon
2015-11-19 15:05     ` Jon Masters
2015-11-19 15:51       ` Borislav Petkov [this message]
2015-11-19 18:19         ` Loc Ho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151119155158.GE6065@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).