public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: 康剑斌 <kjbmail@gmail.com>
Cc: "Koul, Vinod" <vinod.koul@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Can I/OAT DMA engineer access PCI MMIO space
Date: Tue, 03 May 2011 09:05:30 -0700	[thread overview]
Message-ID: <4DC027CA.5000606@intel.com> (raw)
In-Reply-To: <4DBF66C0.9020600@gmail.com>

On 5/2/2011 7:21 PM, 康剑斌 wrote:
>
>>> I try to use ioatdam to copy data from system memory to pci MMIO space:
>>> If dst points to a memory space, the operation would pass.
>>> But if dst points to a pci MMIO space, it failed with kernel oops.
>>> It seems the code:
>>> BUG_ON(is_ioat_bug(chanerr));
>>> in drivers/dma/ioat/dma_v3.c, line 365 cause the oops.
>>> Is there anyway to access pci MMIO space using ioat?
>>> The datasheet says that ioat supports MMIO access.
>> Did you map the IO memory in kernel using ioremap and friends first?
>>
> yes, I had used 'ioremap_nocache' to map the IO memory and I can use
> memcpy to copy data to this region. The async_tx should have been
> correctly configured as
> I can use aync_memcpy to copy data between different system memory address.
>

ioremap maps mmio space for the cpu not bus mastering devices.  You need 
to program the physical address into the descriptor.

--
Dan

      parent reply	other threads:[~2011-05-03 21:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 10:13 Can I/OAT DMA engineer access PCI MMIO space 康剑斌
2011-05-02  6:04 ` Koul, Vinod
2011-05-03  2:21   ` 康剑斌
2011-05-03  4:12     ` Koul, Vinod
2011-05-03  6:31       ` 康剑斌
2011-05-03 15:58         ` Dan Williams
2011-05-05  8:45           ` 康剑斌
2011-05-05 15:11             ` Dan Williams
2011-05-03 16:05     ` Dan Williams [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=4DC027CA.5000606@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=kjbmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vinod.koul@intel.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