[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200706261310.16221.jesse.barnes@intel.com>
Date: Tue, 26 Jun 2007 13:10:15 -0700
From: Jesse Barnes <jesse.barnes@...el.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: Arjan van de Ven <arjan@...ux.intel.com>,
Muli Ben-Yehuda <muli@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>,
linux-kernel@...r.kernel.org, gregkh@...e.de,
suresh.b.siddha@...el.com, ashok.raj@...el.com,
davem@...emloft.net, clameter@....com
Subject: Re: [Intel IOMMU 00/10] Intel IOMMU support, take #2
On Tuesday, June 26, 2007 10:31:57 Andi Kleen wrote:
> > >>(and I think it mostly already doesn't even without that)
> > >
> > >It uses /sys/bus/pci/* which is not any better as seen from the
> > > IOMMU.
> > >
> > >Any interface will need to be explicit because user space needs to
> > > know which
> > >DMA addresses to put into the hardware. It's not enough to just
> > >transparently
> > >translate the mappings.
> >
> > that's what DRM is used for nowadays...
>
> But DRM does support much less hardware than the X server?
Yeah, the number of DRM drivers is relatively small compared to X or
fbdev, but for simple DMA they're fairly easy to write.
> Perhaps we just need an ioctl where an X server can switch this.
Switch what? Turn on or off transparent translation?
Jesse
-
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