Displaying 8 results from an estimated 8 matches for "iommu_intremap".
2012 Oct 24
5
[PATCH v3] IOMMU: keep disabled until iommu_setup() is called
...h fixes this by keeping the iommu disabled until iommu_setup()
is entered.
Originally-by: Ronny Hegewald <ronny.hegewald@online.de>
In order for iommu_enable to be off initially, iommu_supports_eim()
must not depend on it anymore, nor must acpi_parse_dmar(). The former
in turn requires that iommu_intremap gets uncoupled from iommu_enabled
(in particular, failure during IOMMU setup should no longer result in
iommu_intremap getting cleared by generic code; IOMMU specific code
can still do so provided in can live with the consequences).
This could have the nice side effect of allowing to use "iom...
2013 Mar 19
7
[PATCH 0/3] IOMMU errata treatment adjustments
1: IOMMU: properly check whether interrupt remapping is enabled
2: AMD IOMMU: only disable when certain IVRS consistency checks fail
3: VT-d: deal with 5500/5520/X58 errata
Patch 1 and 2 are version 2 of a previously submitted, then
withdrawn patch following up after XSA-36. Patch 3 is version 3 of
a patch previously sent by Malcolm and Andrew.
Signed-off-by: Jan Beulich
2013 Sep 12
3
[PATCH 1/1 V3] x86/AMD-Vi: Add additional check for invalid special->handle
...special->variety, special->handle);
+ special->variety, special->handle, special->used_id);
add_ivrs_mapping_entry(bdf, bdf, special->header.data_setting, iommu);
switch ( special->variety )
{
case ACPI_IVHD_IOAPIC:
- if ( !iommu_intremap )
+ if ( !iommu_intremap ||
+ is_ioapic_overidden(seg, bdf, special->handle) )
break;
+
/*
* Some BIOSes have IOAPIC broken entries so we check for IVRS
* consistency here --- whether entry''s IOAPIC ID is valid and
@@ -725,10...
2013 Jan 15
14
[PATCH] VTD/Intremap: Disable Intremap on Chipset 5500/5520/X58 due to errata
...v = pci_conf_read8(0, bus, 20, 0, PCI_REVISION_ID);
+
+ if ( rev == 0x13 && device == 0x342e8086 )
+ {
+ dprintk(XENLOG_INFO VTDPREFIX,
+ "Disabling Interrupt Remapping due to Intel 5500/5520/X58 Chipset errata #47, #53\n");
+ iommu_intremap = 0;
+ break;
+ }
+ }
+}
+
/* initialize platform identification flags */
void __init platform_quirks_init(void)
{
@@ -264,6 +287,9 @@ void __init platform_quirks_init(void)
/* ioremap IGD MMIO+0x2000 page */
map_igd_reg();
+
+ /* Tylersburg interrupt remap qu...
2012 Oct 18
3
[PATCH 1/1] keep iommu disabled until iommu_setup is called
...nabled_default = 0;
else if ( !strcmp(s, "force") || !strcmp(s, "required") )
force_iommu = 1;
else if ( !strcmp(s, "workaround_bios_bug") )
@@ -312,6 +314,7 @@
{
int rc = -ENODEV;
bool_t force_intremap = force_iommu && iommu_intremap;
+ iommu_enabled = iommu_enabled_default;
if ( iommu_dom0_strict )
iommu_passthrough = 0;
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
2013 Aug 28
12
[PATCH V2] x86/AMD-Vi: Add additional check for invalid special->handle
...ndle);
+ special->variety, special->handle, special->used_id);
add_ivrs_mapping_entry(bdf, bdf, special->header.data_setting, iommu);
switch ( special->variety )
{
case ACPI_IVHD_IOAPIC:
+ {
+ unsigned int apic_id = 0;
if ( !iommu_intremap )
break;
/*
@@ -715,29 +717,45 @@ static u16 __init parse_ivhd_device_special(
*/
for ( apic = 0; apic < nr_ioapics; apic++ )
{
- if ( IO_APIC_ID(apic) != special->handle )
- continue;
+ apic_id = special-&...
2013 Jul 22
69
[xen-unstable] Commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, makes dom0 boot process stall several times.
Hi Jan,
After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times.
Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times.
(It also stalls on shutdown BTW)
I have