From: Clemens Ladisch <clemens@ladisch.de>
To: dmarkh@cfl.rr.com
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 12:55:54 +0200 [thread overview]
Message-ID: <4E85A03A.4030200@ladisch.de> (raw)
In-Reply-To: <4E859529.2020504@cfl.rr.com>
Mark Hounschell wrote:
> 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.
AFAICT you won't be able to do P2P reads in any case.
> 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.
setpci
Regards,
Clemens
prev parent reply other threads:[~2011-09-30 10:55 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
2011-09-30 10:55 ` Clemens Ladisch [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=4E85A03A.4030200@ladisch.de \
--to=clemens@ladisch.de \
--cc=dmarkh@cfl.rr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.