Displaying 11 results from an estimated 11 matches similar to: "[PATCH 3/3] VT-d: use msi_compose_msg()"
2011 Sep 20
0
[PATCH 4/4] x86: split MSI IRQ chip
With the .end() accessor having become optional and noting that
several of the accessors'' behavior really depends on the result of
msi_maskable_irq(), the splits the MSI IRQ chip type into two - one
for the maskable ones, and the other for the (MSI only) non-maskable
ones.
At once the implementation of those methods gets moved from io_apic.c
to msi.c.
Signed-off-by: Jan Beulich
2012 Oct 02
3
[PATCH] VT-d: make remap_entry_to_msi_msg() return consistent message
During debugging of another problem I found that in x2APIC mode, the
destination field of the low address value wasn''t passed back
correctly. While this is benign in most cases (as the value isn''t being
used anywhere), it can be confusing (and misguiding) when printing the
value read or when comparing it to the one previously passed into the
inverse function.
Signed-off-by: Jan
2013 Apr 09
39
[PATCH 0/4] Add posted interrupt supporting
From: Yang Zhang <yang.z.zhang@Intel.com>
The follwoing patches are adding the Posted Interrupt supporting to Xen:
Posted Interrupt allows vAPIC interrupts to inject into guest directly
without any vmexit.
- When delivering a interrupt to guest, if target vcpu is running,
update Posted-interrupt requests bitmap and send a notification event
to the vcpu. Then the vcpu will handle this
2014 Aug 20
1
[RFC PATCH 11/11] x86/MSI: Refactor x86 MSI code
> -----Original Message-----
> From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org]
> On Behalf Of Yijing Wang
> Sent: Saturday, July 26, 2014 8:39 AM
> To: linux-kernel at vger.kernel.org
> Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org;
> Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm-
> kernel at
2014 Aug 20
1
[RFC PATCH 11/11] x86/MSI: Refactor x86 MSI code
> -----Original Message-----
> From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org]
> On Behalf Of Yijing Wang
> Sent: Saturday, July 26, 2014 8:39 AM
> To: linux-kernel at vger.kernel.org
> Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org;
> Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm-
> kernel at
2012 Sep 11
1
[PATCH 0/3] passthrough/x86: use PCI/MSI definitions and functions where possible
1: amd iommu: use PCI macros instead of open coding them
2: amd iommu: use base platform MSI implementation
3: VT-d: use msi_compose_msg()
Signed-off-by: Jan Beulich <jbeulich@suse.com>
2014 Jul 26
0
[RFC PATCH 11/11] x86/MSI: Refactor x86 MSI code
Signed-off-by: Yijing Wang <wangyijing at huawei.com>
---
arch/x86/include/asm/io_apic.h | 2 +-
arch/x86/include/asm/irq_remapping.h | 4 +-
arch/x86/include/asm/pci.h | 6 ++--
arch/x86/include/asm/x86_init.h | 10 +++---
arch/x86/kernel/apic/io_apic.c | 23 +++++++--------
arch/x86/kernel/x86_init.c | 12 ++++----
2007 Apr 18
2
refactoring io_apic.c
OK, I need to do something like this to io_apic.c - split the hardware
specific parts out under mach-default, so we can override them for other
subarchitectures. It's not finished, needs header file and makefile
work. Would you be willing to take this if I do it? I'm not going to
bother if you're not, such refactorings are a pig to maintain out of
tree.
Frankly, io_apic.c needs a
2007 Apr 18
2
refactoring io_apic.c
OK, I need to do something like this to io_apic.c - split the hardware
specific parts out under mach-default, so we can override them for other
subarchitectures. It's not finished, needs header file and makefile
work. Would you be willing to take this if I do it? I'm not going to
bother if you're not, such refactorings are a pig to maintain out of
tree.
Frankly, io_apic.c needs a
2014 Jul 26
20
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi all,
The series is a draft of generic MSI driver that supports PCI
and Non-PCI device which have MSI capability. If you're not interested
it, sorry for the noise.
The series is based on Linux-3.16-rc1.
MSI was introduced in PCI Spec 2.2. Currently, kernel MSI
driver codes are bonding with PCI device. Because MSI has a lot
advantages in design. More and more non-PCI devices want to
use
2014 Jul 26
20
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi all,
The series is a draft of generic MSI driver that supports PCI
and Non-PCI device which have MSI capability. If you're not interested
it, sorry for the noise.
The series is based on Linux-3.16-rc1.
MSI was introduced in PCI Spec 2.2. Currently, kernel MSI
driver codes are bonding with PCI device. Because MSI has a lot
advantages in design. More and more non-PCI devices want to
use