Re: [PATCH 3/4] PCI: PCIE AER: PCIE AER software error injection

[Jesse Barnes]

On Mon, 15 Jun 2009 10:42:57 +0800
Huang Ying <ying.huang@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxx>
> > > > >
> > > >
> > > > 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@xxxxxxxxxxxxxxxx, 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/