This is v2 of the RFC, fixing a memory leak in
kvm_flush_dynamic_msi_routes and adding support for the proposed
KVM_SIGNAL_MSI IOCTL.
This series depends on kvm: set gsi_bits and max_gsi correctly
(http://thread.gmane.org/gmane.comp.emulators.kvm.devel/88906).
Jan Kiszka (4):
kvm: Refactor
From: Jan Kiszka jan.kis...@siemens.com
If the kernel supports KVM_SIGNAL_MSI, we can avoid the route-based
MSI injection mechanism.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-all.c | 22 +++---
1 files changed, 19 insertions(+), 3 deletions(-)
diff --git
From: Jan Kiszka jan.kis...@siemens.com
This patch basically adds kvm_irqchip_send_msi, a service for sending
arbitrary MSI messages to KVM's in-kernel irqchip models.
As the current KVI API requires us to establish a static route from a
pseudo GSI to the target MSI message and inject the MSI
From: Jan Kiszka jan.kis...@siemens.com
Instead of the bitmap size, store the maximum of GSIs the kernel
support. Move the GSI limit assertion to the API function
kvm_irqchip_add_route and make it stricter.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-all.c |8
1 files
From: Jan Kiszka jan.kis...@siemens.com
Catch writes to the MSI MMIO region in the KVM APIC and forward them to
the kernel. Provide the kernel support GSI routing, this allows to
enable MSI support also for in-kernel irqchip mode.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/apic.c
https://bugzilla.kernel.org/show_bug.cgi?id=42635
--- Comment #3 from Klaus Mueller kmuel...@justmail.de 2012-04-03 07:27:43
---
Meanwhile I detected, that using the boot option iommu=pt (or additional
iommu=1) shows the same problem (regardless of suspend/resume). If the VM is
started
On Mon, Apr 02, 2012 at 08:54:32PM -0400, Sasha Levin wrote:
Hi all,
I got the spew at the bottom of the mail in a KVM guest using the KVM tools
and running trinity.
I'm not quite sure how default_idle managed to trigger a pagefault, so that
part looks odd to me.
This is not regular
Avi,
The following changes since commit 592f5d87b3feee9d60411f19d583038c0c7670ad:
KVM: PPC: Book3S: PR: Fix preemption (2012-04-03 16:42:39 +1000)
are available in the git repository at:
git://github.com/paulusmack/linux tags/powerpc-fixes
for you to fetch changes up to
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/tests/kvm/tests/ksm_overcommit.py |2 +-
client/tests/kvm/tests/virtio_console.py |2 +-
client/virt/aexpect.py | 28 ++--
client/virt/deps/test_cpu_flags/stress.c |2 +-
4 files
On Tue, Apr 03, 2012 at 10:03:05PM +1000, Paul Mackerras wrote:
The following changes since commit 592f5d87b3feee9d60411f19d583038c0c7670ad:
OK, I messed up the git request-pull command. The request should have
looked like this:
The following changes since commit
On 04/01/2012 07:23 PM, Avi Kivity wrote:
On 03/29/2012 11:27 AM, Xiao Guangrong wrote:
If the the present bit of page fault error code is set, it indicates
the shadow page is populated on all levels, it means what we do is only
modify the access bit which can be done out of mmu-lock
On Tue, Apr 03, 2012 at 09:23:12AM +0200, Jan Kiszka wrote:
This is v2 of the RFC, fixing a memory leak in
kvm_flush_dynamic_msi_routes and adding support for the proposed
KVM_SIGNAL_MSI IOCTL.
This series depends on kvm: set gsi_bits and max_gsi correctly
On Mon, Apr 02, 2012 at 08:54:32PM -0400, Sasha Levin wrote:
Hi all,
I got the spew at the bottom of the mail in a KVM guest using the KVM tools
and running trinity.
I'm not quite sure how default_idle managed to trigger a pagefault, so that
part looks odd to me.
Wrapping the offending
On Mon, Mar 19, 2012 at 12:37 PM, Gleb Natapov g...@redhat.com wrote:
On Mon, Mar 19, 2012 at 12:20:30PM +0530, shashank rachamalla wrote:
On Sun, Mar 18, 2012 at 10:21 PM, Gleb Natapov g...@redhat.com wrote:
On Sun, Mar 18, 2012 at 09:47:55PM +0530, shashank rachamalla wrote:
I guess
On 04/03/2012 03:22 PM, Paul Mackerras wrote:
On Tue, Apr 03, 2012 at 10:03:05PM +1000, Paul Mackerras wrote:
The following changes since commit 592f5d87b3feee9d60411f19d583038c0c7670ad:
OK, I messed up the git request-pull command. The request should have
looked like this:
The
I'm afraid my notes are rather rough...
* 1.1
soft freeze apr 15th (less than two weeks)
hard freeze may 1
three months cycle for 1.2
stable machine types only every few releases? pc-next
* Maintainers, got distracted and my notes make no sense, sorry
* MSI injection to KVM irqchips
On 03/29/2012 09:14 PM, Jan Kiszka wrote:
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
On 2012-04-03 18:27, Avi Kivity wrote:
On 03/29/2012 09:14 PM, Jan Kiszka wrote:
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
On 04/03/2012 07:47 PM, Jan Kiszka wrote:
so we have a single ioctl for all interrupt handling. This allows
eventual removal of the line-oriented ioctls.
The other alternative is to have a dma interface, similar to the kvm_run
mmio interface but with the kernel acting as
On Tue, Apr 03, 2012 at 07:20:04PM +0530, shashank rachamalla wrote:
On Mon, Mar 19, 2012 at 12:37 PM, Gleb Natapov g...@redhat.com wrote:
On Mon, Mar 19, 2012 at 12:20:30PM +0530, shashank rachamalla wrote:
On Sun, Mar 18, 2012 at 10:21 PM, Gleb Natapov g...@redhat.com wrote:
On Sun, Mar
On 2012-04-03 18:54, Avi Kivity wrote:
On 04/03/2012 07:47 PM, Jan Kiszka wrote:
so we have a single ioctl for all interrupt handling. This allows
eventual removal of the line-oriented ioctls.
The other alternative is to have a dma interface, similar to the kvm_run
mmio interface but with
On 2012-04-03 15:06, Michael S. Tsirkin wrote:
On Tue, Apr 03, 2012 at 09:23:12AM +0200, Jan Kiszka wrote:
This is v2 of the RFC, fixing a memory leak in
kvm_flush_dynamic_msi_routes and adding support for the proposed
KVM_SIGNAL_MSI IOCTL.
This series depends on kvm: set gsi_bits and
On Tue, Apr 3, 2012 at 10:28 PM, Gleb Natapov g...@redhat.com wrote:
On Tue, Apr 03, 2012 at 07:20:04PM +0530, shashank rachamalla wrote:
On Mon, Mar 19, 2012 at 12:37 PM, Gleb Natapov g...@redhat.com wrote:
On Mon, Mar 19, 2012 at 12:20:30PM +0530, shashank rachamalla wrote:
On Sun, Mar 18,
On Wed, Apr 4, 2012 at 12:13 AM, shashank rachamalla
shashank.rachama...@gmail.com wrote:
On Tue, Apr 3, 2012 at 10:28 PM, Gleb Natapov g...@redhat.com wrote:
On Tue, Apr 03, 2012 at 07:20:04PM +0530, shashank rachamalla wrote:
On Mon, Mar 19, 2012 at 12:37 PM, Gleb Natapov g...@redhat.com
On 2012-04-03 09:23, Jan Kiszka wrote:
This is v2 of the RFC, fixing a memory leak in
kvm_flush_dynamic_msi_routes and adding support for the proposed
KVM_SIGNAL_MSI IOCTL.
This series depends on kvm: set gsi_bits and max_gsi correctly
On 04/03/2012 05:43 PM, Markus Armbruster wrote:
I'm afraid my notes are rather rough...
* 1.1
soft freeze apr 15th (less than two weeks)
hard freeze may 1
three months cycle for 1.2
stable machine types only every few releases? pc-next
* Maintainers, got distracted and my notes
On Tue, Apr 03, 2012 at 11:43:57PM +0300, Dor Laor wrote:
On 04/03/2012 05:43 PM, Markus Armbruster wrote:
I'm afraid my notes are rather rough...
* 1.1
soft freeze apr 15th (less than two weeks)
hard freeze may 1
three months cycle for 1.2
stable machine types only every few
Avi,
The following changes since commit 592f5d87b3feee9d60411f19d583038c0c7670ad:
KVM: PPC: Book3S: PR: Fix preemption (2012-04-03 16:42:39 +1000)
are available in the git repository at:
git://github.com/paulusmack/linux tags/powerpc-fixes
for you to fetch changes up to
On Tue, Apr 03, 2012 at 10:03:05PM +1000, Paul Mackerras wrote:
The following changes since commit 592f5d87b3feee9d60411f19d583038c0c7670ad:
OK, I messed up the git request-pull command. The request should have
looked like this:
The following changes since commit
On 04/03/2012 03:22 PM, Paul Mackerras wrote:
On Tue, Apr 03, 2012 at 10:03:05PM +1000, Paul Mackerras wrote:
The following changes since commit 592f5d87b3feee9d60411f19d583038c0c7670ad:
OK, I messed up the git request-pull command. The request should have
looked like this:
The
30 matches
Mail list logo
