From: Andi Kleen <ak@muc.de>
To: long <tlnguyen@snoqualmie.dp.intel.com>
Cc: greg@kroah.com, tom.l.nguyen@intel.com,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org,
seto.hidetoshi@jp.fujitsu.com
Subject: Re: [PATCH 1/6] PCI Express Advanced Error Reporting Driver
Date: Sat, 12 Mar 2005 10:37:55 +0100 [thread overview]
Message-ID: <m1psy5xkzw.fsf@muc.de> (raw)
In-Reply-To: <200503120012.j2C0CIj4020297@snoqualmie.dp.intel.com> (tlnguyen@snoqualmie.dp.intel.com's message of "Fri, 11 Mar 2005 16:12:18 -0800")
long <tlnguyen@snoqualmie.dp.intel.com> writes:
I haven't read your code in detail, just a high level remark.
> +6. Enabling AER Aware Support in PCI Express Device Driver
> +
> +To enable AER aware support requires a software driver to configure
> +the AER capability structure within its device, to initialize its AER
> +aware callback handle and to call pcie_aer_register. Sections 6.1,
> +6.2, and 6.3 describe how to enable AER aware support in details.
[...]
There is currently discussion underway for a generic portable PCI
error reporting interface for drivers. This is already being worked
on by some PPC64 and IA64 people. I don't think it would be a good idea
to add another incompatible PCI-E specific interface.
So I would recommend to not apply pcie_aer_register() et.al.
and coordinate with the others working on this area on a common
interface.
This would only impact the device driver interface; having
a PCI Express specific interface in sysfs is probably ok.
Otherwise we would end up with tons of ifdefs in the drivers
supporting multiple error reporting interfaces for different platforms,
which would be bad.
Also in general I think the necessary callbacks should
be part of the basic device; not provided in a separate structure.
-Andi
next prev parent reply other threads:[~2005-03-12 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 0:12 [PATCH 1/6] PCI Express Advanced Error Reporting Driver long
2005-03-12 9:37 ` Andi Kleen [this message]
2005-03-14 11:00 ` David Vrabel
2005-03-15 22:51 ` Linas Vepstas
2005-03-15 23:12 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2005-03-14 16:54 Nguyen, Tom L
2005-03-14 17:00 ` Randy.Dunlap
2005-03-14 20:01 Nguyen, Tom L
2005-03-15 23:59 Nguyen, Tom L
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=m1psy5xkzw.fsf@muc.de \
--to=ak@muc.de \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tlnguyen@snoqualmie.dp.intel.com \
--cc=tom.l.nguyen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox