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]
Date:	Wed, 05 Aug 2009 08:08:51 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Dave Airlie <airlied@...il.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Keir Fraser <kier.fraser@...citrix.com>,
	xen-devel@...ts.xensource.com, Joerg Roedel <joerg.roedel@....com>,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Zhenyu Wang <zhenyu.z.wang@...el.com>
Subject: Re: [Xen-devel] Re: [RFC] Make AGP work with IOMMU

On Wed, 2009-08-05 at 16:57 +1000, Dave Airlie wrote:
> On Wed, Aug 5, 2009 at 4:44 PM, David Woodhouse<dwmw2@...radead.org> wrote:
> > On Tue, 2009-08-04 at 16:52 -0700, Jeremy Fitzhardinge wrote:
> >> And just when I have patches to use them for their original purpose...
> >>
> >> Looking back over the thread, are you saying that most users are already
> >> using the DMA API correctly for AGP accesses?  If that's true then we
> >> should be just fine.
> >
> > No, not 'most users'. But perhaps we should.
> >
> > All we've done so far is make intel-agp use the DMA API correctly. And
> > that's conditional on CONFIG_DMAR. But we could make it unconditional,
> > and make the other drivers do it too. The code is all fairly generic.
> >
> > Without an IOMMU, the overhead would be fairly minimal.
> >
> 
> I'm not sure how prevalent Xen is on AGP systems, I'm going to guess
> not enough that anyone cares. Intel integrated chips are the only AGP
> codebase user that are made any more, and they don't really use AGP
> its just a legacy of the previous designs.

On the other hand, extending the existing code so that it uses the DMA
API correctly _unconditionally_ rather than only for the Intel driver
would be fairly simple and should be harmless...

-- 
dwmw2

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ