[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6A3DF150A5B70D4F9B66A25E3F7C888D07196054@039-SN2MPN1-011.039d.mgd.msft.net>
Date: Tue, 8 Oct 2013 17:09:50 +0000
From: Bhushan Bharat-R65777 <R65777@...escale.com>
To: "joro@...tes.org" <joro@...tes.org>,
Bjorn Helgaas <bhelgaas@...gle.com>
CC: "alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"benh@...nel.crashing.org" <benh@...nel.crashing.org>,
"galak@...nel.crashing.org" <galak@...nel.crashing.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"agraf@...e.de" <agraf@...e.de>,
Wood Scott-B07421 <B07421@...escale.com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>
Subject: RE: [PATCH 1/7] powerpc: Add interface to get msi region information
> -----Original Message-----
> From: joro@...tes.org [mailto:joro@...tes.org]
> Sent: Tuesday, October 08, 2013 10:32 PM
> To: Bjorn Helgaas
> Cc: Bhushan Bharat-R65777; alex.williamson@...hat.com; benh@...nel.crashing.org;
> galak@...nel.crashing.org; linux-kernel@...r.kernel.org; linuxppc-
> dev@...ts.ozlabs.org; linux-pci@...r.kernel.org; agraf@...e.de; Wood Scott-
> B07421; iommu@...ts.linux-foundation.org
> Subject: Re: [PATCH 1/7] powerpc: Add interface to get msi region information
>
> On Tue, Oct 08, 2013 at 10:47:49AM -0600, Bjorn Helgaas wrote:
> > I still have no idea what an "aperture type IOMMU" is, other than that
> > it is "different."
>
> An aperture based IOMMU is basically any GART-like IOMMU which can only remap a
> small window (the aperture) of the DMA address space. DMA outside of that window
> is either blocked completly or passed through untranslated.
It is completely blocked for Freescale PAMU.
So for this type of iommu what we have to do is to create a MSI mapping just after guest physical address, Example: guest have a 512M of memory then we create window of 1G (because of power of 2 requirement), then we have to FIT MSI just after 512M of guest.
And for that we need
1) to know the physical address of MSI's in interrupt controller (for that this patch was all about of).
2) When guest enable MSI interrupt then we write MSI-address and MSI-DATA in device. The discussion with Alex Williamson is about that interface.
Thanks
-Bharat
>
>
> Joerg
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists