[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070424203919.GC27911@linux-os.sc.intel.com>
Date: Tue, 24 Apr 2007 13:39:20 -0700
From: Ashok Raj <ashok.raj@...el.com>
To: Andi Kleen <ak@...e.de>
Cc: Ashok Raj <ashok.raj@...el.com>, linux-kernel@...r.kernel.org,
akpm@...l.org, gregkh@...e.de, muli@...ibm.com,
asit.k.mallick@...el.com, suresh.b.siddha@...el.com,
anil.s.keshavamurthy@...el.com, arjan@...ux.intel.com,
shaohua.li@...el.com
Subject: Re: [Intel IOMMU][patch 7/8] Support for legacy ISA devices
On Tue, Apr 24, 2007 at 09:31:09PM +0200, Andi Kleen wrote:
> On Tuesday 24 April 2007 08:03:06 Ashok Raj wrote:
> > Floppy disk drivers dont work well with DMA remapping.
>
> What is the problem? You can't allocate mappings <16MB?
No.. these drivers dont call DMA mapping api's.. thats the problem.
>
> > Its possible to
> > extend the current use for x86_64, but the gain is very little. If someone
> > feels compelled to clean this up, its up for grabs. Since these use 16M, we
> > just provide a unity map for the ISA bridge device.
> >
>
> While it's probably not worth for the floppy there are other devices
> with similar weird addressing limitations. Some generic handling of it
> would be nice.
>
In the intro we had outlined a way to handle this via a generic unity
map for all devices, we could do that, i.e
- implement a generic 1-1 map if the device is not calling dma api's and
dynamically dissociate it if the device does start using dma apis.
For some of the addr reservation as well, we could use set_dma_mask()
to ensure there is some dma space. Problem is some drivers may not use
dma apis. Also it might be difficult to address device hotplugged that
has a weird requirement.
-
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