search for: machine_irq

vtd: Fix for irq bind failure after PCI attaching 32 times Originally when detaching a PCI device, pirq_to_emuirq and pirq_to_irq are freed via hypercall do_physdev_op. Now in function pt_irq_destroy_bind_vtd, duplicated logic is added to free pirq_to_emuirq, but not pirq_to_irq. This causes do_physdev_op fail to free both emuirq and irq. After attaching a PCI device for 32 times, irq resources

...e_intx = 0; /* unbind INTx */ - e_device = (ptdev->dev.devfn >> 3) & 0x1f; - /* fix virtual interrupt pin to INTA# */ - e_intx = 0; + e_device = PCI_SLOT(ptdev->dev.devfn); + e_intx = pci_intx(ptdev); if (ptdev->msi_trans_en == 0 && ptdev->machine_irq) { @@ -4131,7 +4130,6 @@ static struct pt_dev * register_real_dev if (rc < 0 && machine_irq != 0) { e_device = PCI_SLOT(assigned_device->dev.devfn); - /* fix virtual interrupt pin to INTA# */ e_intx = pci_intx(assigned_device); rc = x...

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

These two patches were originally part of the XSM series that I have posted, and remain prerequisites for that series. However, they are independent of the XSM changes and are a useful simplification regardless of the use of XSM. The Acked-bys on these patches were provided before rebasing them over the copyback changes in 26268:1b72138bddda, which had minor conflicts that I resolved. [PATCH

...rst_gport, uint32_t first_mport, uint32_t nr_ports, uint32_t add_mapping); int xc_irq_mapping(int xc_handle, uint32_t domain_id, uint32_t method, uint32_t machine_irq, uint32_t device, uint32_t intx, uint32_t add_mapping); int xc_domain_memory_mapping(int xc_handle, uint32_t domid, unsigned long first_gfn, unsigned long...

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm: