19 Jul, 2010
1 commit
-
This patch allows IOMMU users to determine whether the
hardware and software support safe, isolated interrupt
remapping. Not all Intel IOMMUs have the hardware, and the
software for AMD is not there yet.Signed-off-by: Tom Lyon
Signed-off-by: Joerg Roedel
08 Mar, 2010
4 commits
-
These functions are not longer used and can be removed
savely. There functionality is now provided by the
iommu_{un}map functions which are also capable of multiple
page sizes.Signed-off-by: Joerg Roedel
-
This patch adds new callbacks for mapping and unmapping
pages to the iommu_ops structure. These callbacks are aware
of page sizes which makes them different to the
->{un}map_range callbacks.Signed-off-by: Joerg Roedel
-
These two functions provide support for mapping and
unmapping physical addresses to io virtual addresses. The
difference to the iommu_(un)map_range() is that the new
functions take a gfp_order parameter instead of a size. This
allows the IOMMU backend implementations to detect easier if
a given range can be mapped by larger page sizes.
These new functions should replace the old ones in the long
term.Signed-off-by: Joerg Roedel
-
The new function pointer names match better with the
top-level functions of the iommu-api which are using them.
Main intention of this change is to make the ->{un}map
pointer names free for two new mapping functions.Signed-off-by: Joerg Roedel
24 Mar, 2009
2 commits
-
The user can request to enable snooping control through VT-d page table.
Signed-off-by: Sheng Yang
Signed-off-by: David Woodhouse -
This iommu_op can tell if domain have a specific capability, like snooping
control for Intel IOMMU, which can be used by other components of kernel to
adjust the behaviour.Signed-off-by: Sheng Yang
Signed-off-by: David Woodhouse
03 Jan, 2009
1 commit
-
This patch introduces the API to abstract the exported VT-d functions
for KVM into a generic API. This way the AMD IOMMU implementation can
plug into this API later.Signed-off-by: Joerg Roedel