From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Andi Kleen <andi@firstfloor.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 3/4] PCI: PCIE AER: PCIE AER software error injection
Date: Fri, 24 Apr 2009 13:57:21 +0900 [thread overview]
Message-ID: <49F146B1.5010500@jp.fujitsu.com> (raw)
In-Reply-To: <1240547769.6842.782.camel@yhuang-dev.sh.intel.com>
Huang Ying wrote:
> On Fri, 2009-04-24 at 12:32 +0800, Kenji Kaneshige wrote:
>> Huang Ying wrote:
>>> Debugging PCIE AER code can be very difficult because it is hard to
>>> trigger various real hardware errors. This patch provide a software
>>> based error injection tool, which can fake various PCIE errors with a
>>> user space helper tool named "aer-inject". Which can be gotten from:
>>>
>>> http://www.kernel.org/pub/linux/kernel/people/yhuang/
>>>
>>> The patch fakes AER error by faking some PCIE AER related registers
>>> and an AER interrupt for specified the PCIE device.
>>>
>>> Signed-off-by: Huang Ying <ying.huang@intel.com>
>>>
>>> ---
>>> drivers/pci/pcie/aer/Kconfig | 2
>>> drivers/pci/pcie/aer/Kconfig.debug | 18 +
>>> drivers/pci/pcie/aer/Makefile | 1
>>> drivers/pci/pcie/aer/aer_inject.c | 472 +++++++++++++++++++++++++++++++++++++
>>> 4 files changed, 493 insertions(+)
>>>
>>> --- /dev/null
>>> +++ b/drivers/pci/pcie/aer/aer_inject.c
>>> @@ -0,0 +1,472 @@
>>> +/*
>>> + * PCIE AER software error injection support.
>>> + *
>>> + * Debuging PCIE AER code is quite difficult because it is hard to
>>> + * trigger various real hardware errors. Software based error
>>> + * injection can fake almost all kinds of errors with the help of a
>>> + * user space helper tool aer-inject, which can be gotten from:
>>> + * http://www.kernel.org/pub/utils/pcie/aer-inject
>> Shouldn't it be
>>
>> http://www.kernel.org/pub/linux/kernel/people/yhuang/
>
> Yes. I forget to change this. But the directory to put aer-inject tar
> ball is subject to be changed. I am contacting with kernel.org ftp
> maintainer for appropriate place.
>
I see.
By the way, thank you for this very nice feature!
Thanks,
Kenji Kaneshige
next prev parent reply other threads:[~2009-04-24 4:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 2:45 [PATCH 3/4] PCI: PCIE AER: PCIE AER software error injection Huang Ying
2009-04-24 4:32 ` Kenji Kaneshige
2009-04-24 4:36 ` Huang Ying
2009-04-24 4:57 ` Kenji Kaneshige [this message]
2009-04-28 7:40 ` Huang Ying
2009-06-11 18:59 ` Jesse Barnes
2009-06-12 1:54 ` Huang Ying
2009-06-12 15:53 ` Jesse Barnes
2009-06-15 2:42 ` Huang Ying
2009-06-16 17:17 ` 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=49F146B1.5010500@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=andi@firstfloor.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox