From: Ashok Raj <ashok.raj@intel.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, ak@suse.de, gregkh@suse.de, muli@il.ibm.com
Cc: asit.k.mallick@intel.com, suresh.b.siddha@intel.com
Cc: anil.s.keshavamurthy@intel.com, arjan@linux.intel.com
Cc: ashok.raj@intel.com
Subject: [Intel IOMMU][patch 0/8] Intel IOMMU Support.
Date: Mon, 23 Apr 2007 23:02:59 -0700 [thread overview]
Message-ID: <20070424060259.426374000@intel.com> (raw)
Hello again!
Andrew: Could you help include in -mm to give it more exposure preparing for
mainline inclusion with more testing?
This is a resend of the patches after addressing some feedback we received.
1. As len requested, we moved most of the acpi parts to drivers/pci instead
of leaving them in drivers/acpi, including some renaming of functions,
using just acpi_get_table() only.
2. Made the guard page support configurable.
3. Added new CONFIG option to allocate consecutive address instead of re-using
free addresses as an experimental option, Not validated extensively.
Its expected to improve in certain cases...
4. Fixed a couple minor bugs that got exposed in testing.
Other feedback:
- Some suggested depend on ACPI, but thats not doable for several reasons.
- Graphics 1-1 maps exist only for compatibility until graphics drivers
start calling pci map functions, including user space X that might be
using /dev/mem.
Some more interesting possibilities. -- enhancements to work on.
- In order to ensure we dont break any driver that may not be using dma api's
here are some suggestions to work on.
- Create a single 1-1 map, and make sure any pci device gets this map
when they do a pci_set_master() to enable bus mastering automatically.
- When the device driver does a first call to do a dma mapping, then
dissociate the device from the unity map domain, to its own. This gives
limited protection but doesnt break drivers that do not use dma
mapping.
- Creating context entries only 1 per segment.. today we create one per
IOMMU which is not required.
This way we can avoid doing some of the workarounds we do for some devices
today, and will function as a default container for compatibility.
On one hand, this will provide more compatibility, but we will lose
oppertunity to identify broken device drivers that dont use dma api's
and fix them.... Depending on who you talk to.. some like it.. some just
hate it! and would like to fix the broken ones instead.
Cheers,
Ashok Raj
--
next reply other threads:[~2007-04-24 15:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 6:02 Ashok Raj [this message]
2007-04-24 6:03 ` [Intel IOMMU][patch 1/8] ACPI support for Intel Virtualization Technology for Directed I/O Ashok Raj
2007-04-24 18:50 ` Andi Kleen
2007-04-24 20:17 ` Ashok Raj
2007-04-24 6:03 ` [Intel IOMMU][patch 2/8] Some generic search functions required to lookup device relationships Ashok Raj
2007-04-24 6:03 ` [Intel IOMMU][patch 3/8] Generic hardware support for Intel IOMMU Ashok Raj
2007-04-24 19:27 ` Andi Kleen
2007-04-24 20:59 ` Ashok Raj
2007-04-25 1:17 ` Shaohua Li
2007-04-25 6:53 ` Andi Kleen
2007-04-24 6:03 ` [Intel IOMMU][patch 4/8] Supporting Zero Length Reads in " Ashok Raj
2007-04-24 19:28 ` Andi Kleen
2007-04-24 20:42 ` Ashok Raj
2007-04-24 21:00 ` David Miller
2007-04-24 6:03 ` [Intel IOMMU][patch 5/8] Graphics driver workarounds to provide unity map Ashok Raj
2007-04-24 6:03 ` [Intel IOMMU][patch 6/8] Doc updates for Intel Virtualization Technology for Directed I/O Ashok Raj
2007-04-24 6:03 ` [Intel IOMMU][patch 7/8] Support for legacy ISA devices Ashok Raj
2007-04-24 19:31 ` Andi Kleen
2007-04-24 20:33 ` Arjan van de Ven
2007-04-24 20:39 ` Ashok Raj
2007-04-24 6:03 ` [Intel IOMMU][patch 8/8] Preserve some Virtual Address when devices cannot address entire range Ashok Raj
2007-04-24 19:33 ` Andi Kleen
2007-04-24 20:33 ` Ashok Raj
2007-04-24 21:12 ` Andi Kleen
2007-04-24 21:23 ` David Miller
2007-04-24 21:32 ` Roland Dreier
2007-04-24 21:47 ` David Miller
2007-04-24 21:38 ` Ashok Raj
2007-04-24 21:50 ` David Miller
2007-04-24 22:03 ` Andi Kleen
2007-04-24 22:26 ` Ashok Raj
2007-04-25 1:12 ` H. Peter Anvin
2007-04-25 6:55 ` Andi Kleen
2007-04-24 23:22 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2007-04-23 16:38 [Intel IOMMU][patch 0/8] Intel IOMMU Support Ashok Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070424060259.426374000@intel.com \
--to=ashok.raj@intel.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox