public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Amit Shah <amit.shah@qumranet.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	alexisb@us.ibm.com, andi@firstfloor.org, kvm@vger.kernel.org,
	avi@qumranet.com
Subject: Re: [PATCH v2 -mm 0/2] x86: per-device dma_mapping_ops
Date: Sun, 25 May 2008 10:20:11 +0300	[thread overview]
Message-ID: <20080525072011.GM7334@il.ibm.com> (raw)
In-Reply-To: <200805221613.03686.amit.shah@qumranet.com>

On Thu, May 22, 2008 at 04:13:02PM +0530, Amit Shah wrote:

> OK; this sounds helpful. the hook can make a hypercall and confirm
> with the host kernel if the device in question is an assigned
> physical device. If yes, we replace the dma_ops. Though, the
> original intent of having stackable ops is that we might want to go
> through the swiotlb in the guest even for an assigned device if the
> guest dma addresses are not in the addressable range of the guest
> chipset.
> 
> > created (it works with hot plugging). It enables IOMMUs to set up an
> > appropriate dma_mapping_ops per device.
> 
> From what we've discussed so far, it looks like stackable dma ops will 
> definitely be needed. Does this patchset provide something that stacking 
> won't?

Yes---this patchset let's you have a per-device dma-ops, whereas with
stackable you only get global dma-ops. I think it's clear we need
both, and I think per-device dma-ops are the first thing that's
needed. Stacking can then be introduced on a per-device basis.

Cheers,
Muli


  reply	other threads:[~2008-05-25  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1211178689-3507-1-git-send-email-fujita.tomonori@lab.ntt.co.jp>
2008-05-22 10:43 ` [PATCH v2 -mm 0/2] x86: per-device dma_mapping_ops Amit Shah
2008-05-25  7:20   ` Muli Ben-Yehuda [this message]
2008-05-26  4:09     ` Amit Shah
2008-05-26  6:11       ` FUJITA Tomonori
2008-05-26 16:44         ` Amit Shah
2008-05-26 23:50           ` FUJITA Tomonori
2008-05-27  4:53             ` Amit Shah
2008-05-27  5:24               ` FUJITA Tomonori
2008-05-27  5:54                 ` Amit Shah
2008-05-28 10:19                   ` FUJITA Tomonori

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=20080525072011.GM7334@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexisb@us.ibm.com \
    --cc=amit.shah@qumranet.com \
    --cc=andi@firstfloor.org \
    --cc=avi@qumranet.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=kvm@vger.kernel.org \
    --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