All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Greg KH <gregkh@suse.de>, Joerg Roedel <joerg.roedel@amd.com>,
	kvm@vger.kernel.org, Han Weidong <weidong.han@intel.com>,
	linux-kernel@vger.kernel.org, Alexander Graf <agraf@suse.de>,
	iommu@lists.linux-foundation.org, Ingo Molnar <mingo@redhat.com>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH 0/12] Factor VT-d KVM functions into a generic API (with multiple device assignment support)
Date: Thu, 4 Dec 2008 05:47:02 -0500	[thread overview]
Message-ID: <20081204104702.GE5541@il.ibm.com> (raw)
In-Reply-To: <20081203090304.GJ26275@8bytes.org>

On Wed, Dec 03, 2008 at 10:03:04AM +0100, Joerg Roedel wrote:

> > > > Have you tried porting any of the current iommu controllers to
> > > > this new framework to see if it works properly for them?
> > > 
> > > It works currently for VT-d. I also port it to AMD IOMMU
> > > currently. With some extensions (offset for start address, flags
> > > and size limitation) it is also suitable for IOMMUs like GART or
> > > similar ones.
> > 
> > What about the Calgary chipset?
> 
> Calgary is quite similar to GART (there is something like the
> aperture and a linear single-level pagetable).

Actually, Calgary has multiple per-bus address spaces (each of which
is a single-level linear pagetable limited to 4GB of addressable
memory), so I think it should work with your current approach pretty
much as is, once we take into account these two (per-bus and 32-bit
addressability) limitations.

Cheers,
Muli
-- 
The First Workshop on I/O Virtualization (WIOV '08)
Dec 2008, San Diego, CA, http://www.usenix.org/wiov08/
                       <->
SYSTOR 2009---The Israeli Experimental Systems Conference
http://www.haifa.il.ibm.com/conferences/systor2009/

  reply	other threads:[~2008-12-04 10:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 13:01 [PATCH 0/12] Factor VT-d KVM functions into a generic API (with multiple device assignment support) Joerg Roedel
2008-12-02 13:01 ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 01/12] VT-d: Support multiple device assignment for KVM Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 02/12] KVM: change to use new APIs for kvm vtd Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 03/12] KVM: rename vtd.c to iommu.c Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 04/12] introcude linux/iommu.h for an iommu api Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 05/12] add frontend implementation for the IOMMU API Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 06/12] select IOMMU_API when DMAR and/or AMD_IOMMU is selected Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 07/12] KVM: change KVM iommu.c to use IOMMU API Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 08/12] VT-d: adapt domain init and destroy functions for " Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 09/12] VT-d: adapt device attach and detach " Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 10/12] VT-d: adapt domain map and unmap " Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 11/12] VT-d: adapt domain iova_to_phys function " Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-02 13:01 ` [PATCH 12/12] VT-d: register functions for the " Joerg Roedel
2008-12-02 13:01   ` Joerg Roedel
2008-12-03  3:44 ` [PATCH 0/12] Factor VT-d KVM functions into a generic API (with multiple device assignment support) Greg KH
2008-12-03  7:50   ` Joerg Roedel
2008-12-03  7:53     ` Greg KH
2008-12-03  9:03       ` Joerg Roedel
2008-12-04 10:47         ` Muli Ben-Yehuda [this message]
2008-12-03 10:17 ` Han, Weidong
2008-12-03 10:17   ` Han, Weidong

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=20081204104702.GE5541@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=gregkh@suse.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=weidong.han@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 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.