[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1176193673.6781.24.camel@sli10-conroe.sh.intel.com>
Date: Tue, 10 Apr 2007 16:27:53 +0800
From: Shaohua Li <shaohua.li@...el.com>
To: Jeff Garzik <jeff@...zik.org>
Cc: Ashok Raj <ashok.raj@...el.com>, linux-kernel@...r.kernel.org,
akpm@...l.org, ak@...e.de, 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,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [patch 0/8] [Intel IOMMU] Support for Intel Virtualization
Technology for Directed I/O
On Tue, 2007-04-10 at 04:21 -0400, Jeff Garzik wrote:
> Ashok Raj wrote:
> > 1. Support for ACPI framework to parse and work with DMA Remapping Tables.
> > 2. Add support for PCI infrastructure to search parent relationships.
> > 3. Hardware support for providing DMA remapping support for Intel Chipsets.
> > 4. Supporting Zero Length Reads on DMAR's not able to support ZLR.
> > 5. Graphics driver workarounds to provide unity map since they dont use dma api.
> > 6. Updates to Documentation area for startup options and some basics.
> > 7. Workaround to provide unity map for ISA bridge device to enable floppy disk.
> > 8. Ability to preserve some mappings for devices not able to address entire
> > range.
>
> I really think it would be best to avoid ACPI for something as critical
> as DMA remapping!
DMA remapping just uses ACPI table to tell which dma remapping engine a
pci device is controlled by at boot time. At run time, DMA remapping
hasn't any interactive with ACPI.
Thanks,
Shaohua
-
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