Displaying 4 results from an estimated 4 matches for "acpi_sig_madt".
Did you mean:
acpi_sig_fadt
2019 Nov 22
0
[RFC 02/13] ACPI: Add VIOT definitions
..."IORT" /* IO Remapping Table */
+#define ACPI_SIG_VIOT "VIOT" /* Virtual I/O Table */
#define ACPI_SIG_IVRS "IVRS" /* I/O Virtualization Reporting Structure */
#define ACPI_SIG_LPIT "LPIT" /* Low Power Idle Table */
#define ACPI_SIG_MADT "APIC" /* Multiple APIC Description Table */
@@ -412,6 +413,36 @@ struct acpi_ivrs_memory {
u64 memory_length;
};
+/*******************************************************************************
+ *
+ * VIOT - Virtual I/O Table
+ * Version 1
+ *
+ ******************...
2011 Dec 12
0
[PATCH 1/4] ACPI: eliminate duplicate MADT parsing and unused SBF definitions
...truct acpi_madt_interrupt_source,
+ header);
- plintsrc = (struct acpi_table_plat_int_src *)header;
- if (!plintsrc)
+ if (!header)
return -EINVAL;
if (plintsrc->type == ACPI_INTERRUPT_CPEI) {
@@ -193,12 +194,13 @@ static void __init touch_acpi_table(void
*/
acpi_table_parse(ACPI_SIG_MADT, acpi_backup_table);
- if (acpi_table_parse_madt(ACPI_MADT_LSAPIC, acpi_update_lsapic, 0) < 0)
+ if (acpi_table_parse_madt(ACPI_MADT_TYPE_LOCAL_SAPIC,
+ acpi_update_lsapic, 0) < 0)
printk("Error parsing MADT - no LAPIC entries\n");
acpi_update_madt_checksum(madt);
-...
2019 Nov 22
16
[RFC 00/13] virtio-iommu on non-devicetree platforms
I'm seeking feedback on multi-platform support for virtio-iommu. At the
moment only devicetree (DT) is supported and we don't have a pleasant
solution for other platforms. Once we figure out the topology
description, x86 support is trivial.
Since the IOMMU manages memory accesses from other devices, the guest
kernel needs to initialize the IOMMU before endpoints start issuing DMA.
2019 Nov 22
16
[RFC 00/13] virtio-iommu on non-devicetree platforms
I'm seeking feedback on multi-platform support for virtio-iommu. At the
moment only devicetree (DT) is supported and we don't have a pleasant
solution for other platforms. Once we figure out the topology
description, x86 support is trivial.
Since the IOMMU manages memory accesses from other devices, the guest
kernel needs to initialize the IOMMU before endpoints start issuing DMA.