linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Ramesh Errabolu <ramesh.errabolu@gmail.com>, linux-pci@vger.kernel.org
Subject: Re: Understanding P2P DMA related errors
Date: Wed, 5 Oct 2022 12:09:55 -0500	[thread overview]
Message-ID: <20221005170955.GA2300238@bhelgaas> (raw)
In-Reply-To: <5d3b257a-c125-fdd6-e29f-229e54679f45@deltatee.com>

On Wed, Oct 05, 2022 at 09:54:50AM -0600, Logan Gunthorpe wrote:
> On 2022-10-04 22:42, Ramesh Errabolu wrote:
> > Hi,
> > 
> > Thanks for taking a look at this. I will see if I can add 0x09A2 to the
> > whitelist and see what happens. But could you clarify my reading of the
> > device tree. In the tree I don't see an AMD device attached to the
> > 0x09A2 device. Is that a misread on my part? Would appreciate it if you
> > could shed light on this aspect.

Ramesh, just FIYI, your emails aren't making it to the mailing list,
probably because they're "too fancy," e.g., they are multi-part or
contain HTML.  See http://vger.kernel.org/majordomo-info.html

You can see the effect at
https://lore.kernel.org/all/5d3b257a-c125-fdd6-e29f-229e54679f45@deltatee.com/
The archive contains Logan's responses, but not the emails from you
that Logan is responding to.

Bjorn

  reply	other threads:[~2022-10-05 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFGSPrzM_pRZ-JEWimKYDPzv76t_Nw2Q6od19S_3dzbG_0-bDA@mail.gmail.com>
2022-10-04 23:44 ` Understanding P2P DMA related errors Logan Gunthorpe
     [not found]   ` <CAFGSPrz2ym5oEot9gLi3Z38PWS5A_wCFM4OWk36U_RazDMR67A@mail.gmail.com>
2022-10-05 15:54     ` Logan Gunthorpe
2022-10-05 17:09       ` Bjorn Helgaas [this message]
2022-10-06  2:56       ` Ramesh Errabolu
2022-10-06 15:26         ` Logan Gunthorpe
2022-10-06 19:33       ` Ramesh Errabolu

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=20221005170955.GA2300238@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=ramesh.errabolu@gmail.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;
as well as URLs for NNTP newsgroup(s).