linux-kernel - Re: [PATCH] iommu: Remove stub functions for !CONFIG_IOMMU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADMYwHwZPiH12HxOP952-Znm_+uMXKpj2M6ew8W-frZ7R8EcWg@mail.gmail.com>
Date:	Mon, 29 Aug 2011 13:59:05 +0300
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	"Roedel, Joerg" <Joerg.Roedel@....com>
Cc:	"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
	Stepan Moskovchenko <stepanm@...eaurora.org>,
	David Woodhouse <dwmw2@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Brown <davidb@...eaurora.org>
Subject: Re: [PATCH] iommu: Remove stub functions for !CONFIG_IOMMU_API

On Mon, Aug 29, 2011 at 1:15 PM, Roedel, Joerg <Joerg.Roedel@....com> wrote:
> Isn't the abstraction that the drivers use the dma-api? There should be
> an implementation that doesn't require the iommu-api for such devices,
> no?

Before we boot a remote processor device we often need to map it to
some (specific) bus addresses (e.g. to allow the processor access to
certain peripheral devices), and we're doing it directly with the
IOMMU API.

Do you think this kind of functionality should be added to the DMA API as well ?

IIRC, it was suggested awhile ago but you supported using the IOMMU
API directly in this case.

Thanks,
Ohad.
--
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/