Displaying 6 results from an estimated 6 matches similar to: "use of struct hvm_mirq_dpci_mapping.gmsi vs. HVM_IRQ_DPCI_*_MSI flags"
2011 Jan 26
9
[PATCH]vtd: Fix for irq bind failure after PCI attaching 32 times
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
2007 Oct 17
7
[VTD][RESEND]add a timer for the shared interrupt issue for vt-d
Keir,
It''s a resending patch for the timeout mechanism to deal with the shared
interrupt issue for vt-d enabled hvm guest.
We modify the patch following your comments last time and make some
other small fix:
1) We don''t touch the locking around the hvm_dpci_eoi().
2) Remove the HZ from the TIME_OUT_PERIOD macro which may confuse
others.
3) Add some
2008 Sep 26
2
RE: [Xen-changelog] [xen-unstable] x86: Properly synchronise updates to pirq-to-vector mapping.
@@ -491,16 +512,15 @@ int pirq_guest_bind(struct vcpu *v, int
int rc = 0;
cpumask_t cpumask = CPU_MASK_NONE;
+ WARN_ON(!spin_is_locked(&v->domain->evtchn_lock));
I find this WARN_ON() is triggered harmlessly when I assign device to HVM guest.
The call trace is XEN_DOMCTL_bind_pt_irq -> pt_irq_create_bind_vtd() -> pirq_guest_bind().
Should we
2008 Jul 24
6
PCI MSI questions
Looking at the MSI implementation I have a couple of questions:
1) There currently seems to be a hidden requirement of NR_PIRQS in the
kernel needing to be no smaller than NR_IRQS in the hypervisor.
Otherwise, the pirq returned from PHYSDEVOP_map_pirq may collide
with the dynamic IRQs in the kernel or even be out of range altogether.
Therefore I think that NR_PIRQS has to become a variable
2009 Jan 09
5
[PATCH] Enable PCI passthrough with stub domain.
This patch enables PCI passthrough with stub domain.
PCI passthrough with stub domain has failed in the past.
The primary reason is that hypercalls from qemu in stub domain are rejected.
This patch allows qemu in stub domain to call the hypercalls which is
needed for PCI passthrough. For security, if target domain of
hypercall is different from that of stub domain, it rejects hypercall.
To use
2009 Jan 18
0
libmsi.a import library from wine, and header files available (entirely free software), available for python-win32 builds under msys+wine
as part of building python2.5.2 under msys under wine on linux using
mingw, i thought i'd try building _msi.pyd just for kicks. of course,
that required having an msi.lib import library, and associated header
files. so, purely as an experiment, i've documented the process by
which it is possible to take wine 1.1.13 (current development release)
source code, modify the header files for