From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: yhlu.kernel@gmail.com
Cc: fujita.tomonori@lab.ntt.co.jp, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, muli@il.ibm.com, alexisb@us.ibm.com
Subject: Re: [PATCH 2/2] x86: per-device dma_mapping_ops support
Date: Fri, 16 May 2008 12:44:52 +0900 [thread overview]
Message-ID: <20080516120017L.tomof@acm.org> (raw)
In-Reply-To: <86802c440805151345g6f272ab1xb1644ac9d655e6e2@mail.gmail.com>
On Thu, 15 May 2008 13:45:58 -0700
"Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
> On Mon, May 12, 2008 at 11:04 PM, FUJITA Tomonori
> <fujita.tomonori@lab.ntt.co.jp> wrote:
> > This adds per-device dma_mapping_ops support for CONFIG_X86_64.
> >
> > A pointer to dma_mapping_ops to struct dev_archdata is added. If the
> > pointer is non NULL, DMA operations in asm/dma-mapping.h use it. If
> > it's NULL, the system-wide dma_ops pointer is used as before.
> >
> > Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> > ---
> > arch/x86/kernel/pci-calgary_64.c | 2 +-
> > arch/x86/kernel/pci-dma.c | 2 +-
> > arch/x86/kernel/pci-gart_64.c | 2 +-
> > arch/x86/kernel/pci-nommu.c | 14 +-----
> > arch/x86/kernel/pci-swiotlb_64.c | 2 +-
> > include/asm-x86/device.h | 3 +
> > include/asm-x86/dma-mapping.h | 95 ++++++++++++++++++++++++++------------
> > 7 files changed, 74 insertions(+), 46 deletions(-)
(snip)
> do you have other patch to assign value to dma_ops for every device?
> it is always NULL at this time.
Not yet.
As I said, I plan to implement a mechanism to register a hook called
when a new pci (or dma capable) device is created. It enables IOMMUs
to set up an appropriate dma_mapping_ops per device:
http://lkml.org/lkml/2008/5/14/519
But I wanted to make sure whether per-device dma_ops is useful for
everyone.
next prev parent reply other threads:[~2008-05-16 3:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 6:04 [PATCH 0/2] x86: per-device dma_mapping_ops FUJITA Tomonori
2008-05-13 6:04 ` [PATCH 1/2] add the device argument to dma_mapping_error FUJITA Tomonori
2008-05-13 6:04 ` [PATCH 2/2] x86: per-device dma_mapping_ops support FUJITA Tomonori
2008-05-14 5:55 ` Muli Ben-Yehuda
2008-05-15 20:45 ` Yinghai Lu
2008-05-16 3:44 ` FUJITA Tomonori [this message]
2008-05-13 15:39 ` [PATCH 1/2] add the device argument to dma_mapping_error Randy Dunlap
2008-05-15 1:12 ` FUJITA Tomonori
2008-05-14 5:49 ` [PATCH 0/2] x86: per-device dma_mapping_ops Muli Ben-Yehuda
2008-05-15 1:12 ` FUJITA Tomonori
2008-05-15 2:00 ` Alexis Bruemmer
2008-05-15 2:30 ` FUJITA Tomonori
2008-05-15 18:21 ` Alexis Bruemmer
2008-05-15 15:17 ` Muli Ben-Yehuda
2008-05-15 15:15 ` Muli Ben-Yehuda
2008-05-15 9:01 ` Andi Kleen
2008-05-15 9:16 ` FUJITA Tomonori
2008-05-15 9:30 ` Andi Kleen
2008-05-15 9:41 ` FUJITA Tomonori
2008-05-15 10:48 ` Andi Kleen
2008-05-15 15:32 ` Muli Ben-Yehuda
2008-05-16 3:44 ` FUJITA Tomonori
2008-05-16 5:24 ` Andi Kleen
2008-05-19 6:32 ` FUJITA Tomonori
2008-05-15 15:26 ` Muli Ben-Yehuda
2008-05-15 21:03 ` Andi Kleen
2008-05-15 21:39 ` Muli Ben-Yehuda
2008-05-15 21:45 ` Andi Kleen
2008-05-15 21:53 ` Muli Ben-Yehuda
2008-05-15 22:05 ` Muli Ben-Yehuda
2008-05-15 18:25 ` Alexis Bruemmer
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=20080516120017L.tomof@acm.org \
--to=fujita.tomonori@lab.ntt.co.jp \
--cc=akpm@linux-foundation.org \
--cc=alexisb@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=yhlu.kernel@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