From: Jean Delvare <jdelvare@suse.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-acpi@vger.kernel.org
Subject: aer_inject vs. apei/einj
Date: Wed, 17 Feb 2016 14:33:06 +0100 [thread overview]
Message-ID: <20160217143306.6340c6cf@endymion> (raw)
Hi all,
I am looking for some guidance regarding AER testing. I see that we
have two different drivers for error injection in the kernel:
aer_inject and apei/einj. The user-space aer-inject tool seems to only
care about the former.
How does one know which driver should be used on a given system? I
suppose that only one of them will work on a given system?
My impression is that aer_inject is for "native" AER handling while
apei/einj is for ACPI-driven AER. Is it correct? If not I would
appreciate some pointers explaining when aer_inject should be used and
when apei/einj should be used.
Thanks,
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2016-02-17 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 13:33 Jean Delvare [this message]
2016-02-17 17:03 ` aer_inject vs. apei/einj Bjorn Helgaas
2016-02-19 10:09 ` Jean Delvare
2016-02-19 15:08 ` Bjorn Helgaas
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=20160217143306.6340c6cf@endymion \
--to=jdelvare@suse.de \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.