Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Ludwig Petrosyan <ludwig.petrosyan@desy.de>
Cc: linux-pci@vger.kernel.org
Subject: Re: PCIe endpoint crosstalk
Date: Tue, 27 Aug 2013 10:27:02 -0600	[thread overview]
Message-ID: <20130827162702.GB21180@google.com> (raw)
In-Reply-To: <521C5AFF.90209@desy.de>

On Tue, Aug 27, 2013 at 09:53:35AM +0200, Ludwig Petrosyan wrote:
> So: I use microTCA system with PCIe bus, there are two AMC cards (PCIe
> endpoints), lets call card A and card B.
> as well there are two device drivers for A and B. Card B has bug, after
> PCIe memory write  operation (MWr) the card sends back Completion
> packet without data (Cpl) (I now it is wrong, but card designed in this
> way and has to be changed).
> User process Ua reads data from Card A in loop, everything is OK , but
> then I start second user process Ub which writes in loop data to card B
> (bugged card) the Ua gets wrong data. After improving card B the problem
> was solved, but could be it has to be checked on the PCIe driver level
> as well.

PCIe transactions (MWr, MRd, Cpl, etc.) are not directly visible
to the OS or the driver.

The only thing I can think of that we could do is add a quirk to
blacklist the broken version of card B.  You can look at existing
quirks in drivers/pci/quirks.c.  Most of them workaround issues
that aren't quite as severe as this one, but we could probably
figure out a way to make the device completely unusable.

Or do you have something else in mind?

Bjorn

  reply	other threads:[~2013-08-27 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  7:53 PCIe endpoint crosstalk Ludwig Petrosyan
2013-08-27 16:27 ` Bjorn Helgaas [this message]
2013-08-28  8:09   ` Ludwig Petrosyan
2013-08-28 12:43     ` Bjorn Helgaas

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=20130827162702.GB21180@google.com \
    --to=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=ludwig.petrosyan@desy.de \
    /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