Displaying 2 results from an estimated 2 matches for "iommu_qinv".
Did you mean:
iommu_qinval
2012 Oct 24
5
[PATCH v3] IOMMU: keep disabled until iommu_setup() is called
...u_dom0_strict )
iommu_passthrough = 0;
- if ( iommu_enabled )
+ if ( iommu_enable )
{
rc = iommu_hardware_setup();
iommu_enabled = (rc == 0);
@@ -409,8 +410,6 @@ int __init iommu_setup(void)
if ( !iommu_enabled )
{
iommu_snoop = 0;
- iommu_qinval = 0;
- iommu_intremap = 0;
iommu_passthrough = 0;
iommu_dom0_strict = 0;
}
@@ -419,6 +418,8 @@ int __init iommu_setup(void)
printk(" - Dom0 mode: %s\n",
iommu_passthrough ? "Passthrough" :
iommu_dom0_strict...
2012 Jan 05
9
[PATCHv2 0 of 2] Deal with IOMMU faults in softirq context.
Hello everyone,
Reposting with after having applied the (minor) fixes suggested by Wei
and Jan.
Allen, if you can tell us what you think about this, or suggest someone
else to ask some feedback to, if you''re no longer involved with VT-d,
that would be great! :-)
--
As already discussed here [1], dealing with IOMMU faults in interrupt
context may cause nasty things to happen, up to