linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	alexisb@us.ibm.com
Subject: Re: [PATCH 0/2] x86: per-device dma_mapping_ops
Date: Thu, 15 May 2008 18:15:10 +0300	[thread overview]
Message-ID: <20080515151510.GE6778@il.ibm.com> (raw)
In-Reply-To: <20080515101212Z.tomof@acm.org>

On Thu, May 15, 2008 at 10:12:25AM +0900, FUJITA Tomonori wrote:
> On Wed, 14 May 2008 08:49:24 +0300
> Muli Ben-Yehuda <muli@il.ibm.com> wrote:
> 
> > On Tue, May 13, 2008 at 03:04:50PM +0900, FUJITA Tomonori wrote:
> > 
> > > This patchset adds per-device dma_mapping_ops support for
> > > CONFIG_X86_64 like POWER architecture does. This change enables us
> > > to cleanly fix the Calgary IOMMU issue that some devices are not
> > > behind the IOMMU [1]. It also would be helpful to handle KVM PCI
> > > passthrough.
> > 
> > Awesome! Much needed, thank you for doing this.
> 
> No problem. Well, as you know, it's just a base. We need more work
> to solve the problems on the top of this.
> 
> I'd like to have 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.

That's great---it will be needed to support hot-plugging of devices on
systems with isolation-capable IOMMUs.

> It could also enables us to simplify the IOMMUs code to initilize
> devices at startup (for exmple, intel-iommu checks all the pci
> devices and creates a domain per device if necessary).

I'm not sure if it will be easier than the current "loop over all
devices" method, but since we will need it for hotplug anyway, we
might as well just switch to it.

> I'll post an updated version against -mm. If people seems to be fine
> with per-device dma_mapping_ops, then I'll work on further issues.

Excellent.

Cheers,
Muli


  parent reply	other threads:[~2008-05-15 20:26 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
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 [this message]
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=20080515151510.GE6778@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexisb@us.ibm.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    /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).