Searched hist:"07975 ad3b30579ca27d880491ad992326b930c63" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/virt/kvm/ |
| H A D | Kconfig | diff 07975ad3b30579ca27d880491ad992326b930c63 Thu Mar 29 14:14:12 CDT 2012 Jan Kiszka <jan.kiszka@siemens.com> KVM: Introduce direct MSI message injection for in-kernel irqchips
Currently, MSI messages can only be injected to in-kernel irqchips by
defining a corresponding IRQ route for each message. This is not only
unhandy if the MSI messages are generated "on the fly" by user space,
IRQ routes are a limited resource that user space has to manage
carefully.
By providing a direct injection path, we can both avoid using up limited
resources and simplify the necessary steps for user land.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | kvm_main.c | diff 07975ad3b30579ca27d880491ad992326b930c63 Thu Mar 29 14:14:12 CDT 2012 Jan Kiszka <jan.kiszka@siemens.com> KVM: Introduce direct MSI message injection for in-kernel irqchips
Currently, MSI messages can only be injected to in-kernel irqchips by
defining a corresponding IRQ route for each message. This is not only
unhandy if the MSI messages are generated "on the fly" by user space,
IRQ routes are a limited resource that user space has to manage
carefully.
By providing a direct injection path, we can both avoid using up limited
resources and simplify the necessary steps for user land.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /openbmc/linux/arch/x86/kvm/ |
| H A D | Kconfig | diff 07975ad3b30579ca27d880491ad992326b930c63 Thu Mar 29 14:14:12 CDT 2012 Jan Kiszka <jan.kiszka@siemens.com> KVM: Introduce direct MSI message injection for in-kernel irqchips
Currently, MSI messages can only be injected to in-kernel irqchips by
defining a corresponding IRQ route for each message. This is not only
unhandy if the MSI messages are generated "on the fly" by user space,
IRQ routes are a limited resource that user space has to manage
carefully.
By providing a direct injection path, we can both avoid using up limited
resources and simplify the necessary steps for user land.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /openbmc/linux/include/linux/ |
| H A D | kvm_host.h | diff 07975ad3b30579ca27d880491ad992326b930c63 Thu Mar 29 14:14:12 CDT 2012 Jan Kiszka <jan.kiszka@siemens.com> KVM: Introduce direct MSI message injection for in-kernel irqchips
Currently, MSI messages can only be injected to in-kernel irqchips by
defining a corresponding IRQ route for each message. This is not only
unhandy if the MSI messages are generated "on the fly" by user space,
IRQ routes are a limited resource that user space has to manage
carefully.
By providing a direct injection path, we can both avoid using up limited
resources and simplify the necessary steps for user land.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|