From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: markh@compro.net,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with AMD chipsets. Was "Re: problems doing direct dma from a pci device to pci-e device"
Date: Fri, 30 Sep 2011 06:08:41 -0400 [thread overview]
Message-ID: <4E859529.2020504@cfl.rr.com> (raw)
In-Reply-To: <4E858200.8070302@ladisch.de>
On 09/30/2011 04:46 AM, Clemens Ladisch wrote:
> Mark Hounschell wrote:
>> We have no problem with this same configuration using a MB with an
>> nvidia chipset. I suspect it might have something to do with the the MB
>> that usines the AMD chipset having an IOMMU, but I really don't know for
>> sure. I've also read something in the AMD chipset docs about some type
>> of restrictions on peer to peer transfers but again I really have no
>> idea if this is related to why I'm having this problem.
>
> According to the published RS780 docs, "P2P traffic could be only memory
> writes" (RPR 2.7). In any case, check the P2P bits (MISC is described
> in BDG 2.4).
>
>
I wonder what they expect you to get out of "P2P traffic _could_ be only
memory writes" Does that mean it _can_ be configured as "P2P traffic is
enabled for only writes"? In any case I can do neither reads or writes.
As for the MISC bits described in the BDG, it appears that by default all
the P2PDIS bits will be set to 0. Are there tools that would enable me to
look at these bits and even change them if they are set. Would these bits
normally be set/reset by the BIOS or the OS?
I previously asked about this problem on the AMD developers forum but got
no response.
Thanks
Mark
next prev parent reply other threads:[~2011-09-30 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 19:41 Problem with AMD chipsets. Was "Re: problems doing direct dma from a pci device to pci-e device" Mark Hounschell
2011-09-29 20:30 ` Mark Hounschell
2011-09-30 8:46 ` Clemens Ladisch
2011-09-30 10:08 ` Mark Hounschell [this message]
2011-09-30 10:55 ` Clemens Ladisch
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=4E859529.2020504@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=markh@compro.net \
/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