From: Jesse Barnes <jesse.barnes@intel.com>
To: Huang Ying <ying.huang@intel.com>
Cc: 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: Tue, 16 Jun 2009 10:17:42 -0700 [thread overview]
Message-ID: <20090616101742.64f3a0f7@jbarnes-g45> (raw)
In-Reply-To: <1245033777.5320.328.camel@yhuang-dev.sh.intel.com>
On Mon, 15 Jun 2009 10:42:57 +0800
Huang Ying <ying.huang@intel.com> wrote:
> On Fri, 2009-06-12 at 23:53 +0800, Barnes, Jesse wrote:
> > On Thu, 11 Jun 2009 18:54:01 -0700
> > "Huang, Ying" <ying.huang@intel.com> wrote:
> >
> > > On Fri, 2009-06-12 at 02:59 +0800, Barnes, Jesse wrote:
> > > > On Fri, 24 Apr 2009 10:45:27 +0800
> > > > Huang Ying <ying.huang@intel.com> 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>
> > > > >
> > > >
> > > > This patch got mangled, care to resend?
> > >
> > > Sorry. Resend patch follows.
> > >
> >
> > This one didn't apply either; can you pull down my linux-next branch
> > and diff against that? Also, cc my personal address,
> > jbarnes@virtuousgeek.org, so Exchange doesn't mess up the patch.
>
> Re-base on
> git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6.git
> branch linux-next.
>
> Sent as attachment, I think that works even for Exchange.
>
> Another patch to fix the user space tool URL is attached with the mail
> too. Please fold it into inject document patch if possible.
Ok, that one applied, thanks. It's queued up in linux-next now...
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-06-16 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 2:45 Huang Ying
2009-04-24 4:32 ` Kenji Kaneshige
2009-04-24 4:36 ` Huang Ying
2009-04-24 4:57 ` Kenji Kaneshige
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 [this message]
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=20090616101742.64f3a0f7@jbarnes-g45 \
--to=jesse.barnes@intel.com \
--cc=andi@firstfloor.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
all inboxes | Powered by JetHome®