From: Matt Domsch <Matt_Domsch@dell.com>
To: Huang Ying <ying.huang@intel.com>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
Tom Long Nguyen <tom.l.nguyen@intel.com>,
Zhang Yanmin <yanmin.zhang@intel.com>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: Fwd: [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode
Date: Fri, 9 Oct 2009 09:31:33 -0500 [thread overview]
Message-ID: <20091009143133.GC19218@mock.linuxdev.us.dell.com> (raw)
In-Reply-To: <1255067727.5228.111.camel@yhuang-dev.sh.intel.com>
On Fri, Oct 09, 2009 at 01:55:27PM +0800, Huang Ying wrote:
> Can you tell me where can I find more about PECI? Or you mean APEI (ACPI
> Platform Error Interfaces)?
Yes, APEI. My mistake. Too many acronyms for my little mind.
> We are working on APEI supporting now too, mainly on the general part.
> We will release the code after it passes our internal testing.
Excellent. If you could post even the untested code, that would be
helpful. Do you have a timeline for publication?
My patch is fundamentally in response to the fact that your APEI code
is not present yet, and there is a problem seen at customer sites now
(particularly SLES 11, as that's the only "Enterprise"-class distro
version with the AER driver, but also any distro or kernel build that
includes the AER driver). But without knowing when the rest of the
APEI code will land in mainline, I feel it would be safe to do the
minimum amount of HEST parsing, just enough to know if AER should be
disabled or not. My patch can be considered "throw-away" code - to be
dropped when your APEI code lands in mainline and the distros.
> As H.Seto said, HEST table parsing code should go the general APEI
> supporting code. We have some HEST table parsing code, hope that can be
> used by your code too.
I agree completely. But I need a solution in the short-term, both for
mainline and which can be backported, until your code is available.
I'm reworking my patch based on Seto-san's comments, and will repost
soon as linux-next stops crashing on me. :-)
Thanks,
Matt
--
Matt Domsch
Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
next prev parent reply other threads:[~2009-10-09 14:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 17:33 [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode Matt Domsch
2009-10-08 0:59 ` Hidetoshi Seto
[not found] ` <851fc09e0910082221q7f832c22xfc0d01ab72a97c3f@mail.gmail.com>
2009-10-09 5:55 ` Fwd: " Huang Ying
2009-10-09 14:31 ` Matt Domsch [this message]
2009-10-09 7:11 ` Kenji Kaneshige
2009-10-09 18:28 ` Matt Domsch
2009-10-09 18:33 ` Matt Domsch
2009-10-29 14:15 ` Matt Domsch
2009-10-29 16:48 ` Jesse Barnes
2009-10-30 2:16 ` Hidetoshi Seto
2009-10-30 2:53 ` Matt Domsch
2009-10-30 3:24 ` Hidetoshi Seto
2009-11-02 17:51 ` Matt Domsch
2009-11-04 17:11 ` Jesse Barnes
2009-11-04 20:55 ` Yinghai Lu
2009-11-04 20:55 ` Yinghai Lu
2009-11-04 21:05 ` Jesse Barnes
2009-11-04 21:07 ` Jesse Barnes
2009-11-04 21:07 ` Jesse Barnes
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=20091009143133.GC19218@mock.linuxdev.us.dell.com \
--to=matt_domsch@dell.com \
--cc=andi@firstfloor.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tom.l.nguyen@intel.com \
--cc=yanmin.zhang@intel.com \
--cc=ying.huang@intel.com \
/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.