[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070410164325.GD31505@linux-os.sc.intel.com>
Date: Tue, 10 Apr 2007 09:43:26 -0700
From: Ashok Raj <ashok.raj@...el.com>
To: Jeff Garzik <jeff@...zik.org>
Cc: Shaohua Li <shaohua.li@...el.com>, 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, Apr 10, 2007 at 04:34:48AM -0400, Jeff Garzik wrote:
> Shaohua Li wrote:
> >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.
>
> The Linux kernel _really_ wants a non-ACPI way to detect this.
>
> Just use the hardware registers themselves, you don't need an ACPI table.
>
> Jeff
ACPI is required just not for identifying the DMA remapping hardware in the
system. We also need them to identify which engines control which pci devices.
Also there are some reserved sections that BIOS uses for its purpose that it
needs identity map.. say for legacy emulation via usb etc that needs
to be passed to the OS.
not sure we can get away from using ACPI that easily.. its just only for setup
information, once the identification is complete we dont bother ACPI anymore.
-
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