On Thursday 08 May 2008 23:20:38 Christian Borntraeger wrote:
> Changing stop_machine to yield the cpu to the hypervisor when yielding
> inside the guest fixed the problem for me. While I am not completely happy
> with this patch, I think it causes no harm and it really improves the
> situation for
Hi Jan,
On Thu, May 08, 2008 at 10:29:32AM +0200, Jan Kiszka wrote:
> Resetting guests used to be racy, deadlock-prone, or simply broken (for
> SMP). This patch fixes the issues - at least for me on x86 (tested on
> Intel SMP host, UP and SMP guest, in-kernel und user space irqchip,
> guest- and m
On Wed, May 07, 2008 at 08:45:12PM +0200, Gerd Hoffmann wrote:
> Ok folks, here is the band aid fix for testing from the odd bugs
> department. Goes on top of the four patches of this series. A real,
> clean solution is TBD. Tomorrow I hope (some urgent private problems
> are in the queue too ..
There's still a race in kvm_vcpu_block(), if a wake_up_interruptible()
call happens before the task state is set to TASK_INTERRUPTIBLE:
CPU0CPU1
kvm_vcpu_block
add_wait_queue
kvm_cpu_has_interrupt = 0
Dor Laor wrote:
> On Thu, 2008-05-08 at 12:03 +0200, Nicolas Daneau wrote:
>> Hi,
>>
>> I saw there was an active discussion about pci passthrough support in
>> KVM. I'm not a Dev, only a sys admin that need this support. As i saw
>> on the KVM home page that this feature is plan for 2H2008 in the
On Thu, May 08, 2008 at 09:11:33AM -0700, Linus Torvalds wrote:
> Btw, this is an issue only on 32-bit x86, because on 64-bit one we already
> have the padding due to the alignment of the 64-bit pointers in the
> list_head (so there's already empty space there).
>
> On 32-bit, the alignment of l
This patch implements the core of save/restore support for virtio. It's
modelled after how PCI save/restore works.
N.B. This makes savevm/loadvm work, but not live migration. The issue with
live migration is that we're manipulating guest memory without updating the
dirty bitmap correctly. I wil
This patch implements the core of save/restore support for virtio. It's
modelled after how PCI save/restore works.
N.B. This makes savevm/loadvm work, but not live migration. The issue with
live migration is that we're manipulating guest memory without updating the
dirty bitmap correctly. I wil
No additional state needs to be saved.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/qemu/hw/virtio-blk.c b/qemu/hw/virtio-blk.c
index 048285a..148cb75 100644
--- a/qemu/hw/virtio-blk.c
+++ b/qemu/hw/virtio-blk.c
@@ -162,11 +162,30 @@ static uint32_t virtio_blk_get_features(Virt
The only interesting bit here is that we have to ensure that we rearm the
timer if necessary.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c
index d15c2f4..5fe66ac 100644
--- a/qemu/hw/virtio-net.c
+++ b/qemu/hw/virtio-net.c
@@ -207,9 +
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Aurelien Jarno wrote:
>>> On Wed, May 07, 2008 at 04:40:58PM -0500, Anthony Liguori wrote:
>>>
The current logic of the can_receive handler is to allow packets
whenever the
receiver is disabled or when there are descriptors available i
Avi Kivity wrote:
>
> Note that flow control still makes sense since it allows us to buffer
> some packets if the guest is scheduled out. But we can't use it as
> the primary mechanism since it won't exist with multiqueue NICs (where
> the virtio descriptors are fed to driver).
>
... are fed t
Anthony Liguori wrote:
> This patch adds compatibility code so that we can make use of eventfd() within
> QEMU. eventfd() is a pretty useful mechanism as it allows multiple
> notifications to be batched in a single system call.
>
> We emulate eventfd() using a standard pipe().
>
Applied all si
Anthony Liguori wrote:
> Aurelien Jarno wrote:
>> On Wed, May 07, 2008 at 04:40:58PM -0500, Anthony Liguori wrote:
>>
>>> The current logic of the can_receive handler is to allow packets
>>> whenever the
>>> receiver is disabled or when there are descriptors available in the
>>> ring.
>>>
>>> I
Am Donnerstag, 8. Mai 2008 schrieb Jeremy Fitzhardinge:
> > Sorry, forgot to mention. Its kvm.git from 2 days ago on s390.
> >
>
> And on s390 cpu_relax yields the vcpu? That's not common behaviour
> across architectures.
Yes, cpu_relax on s390 calls diagnose 44. Diagnose 44 translates to y
Strange situation, I have a Ubuntu JeOS image that crashes with this
error when started by the kvm-068 user-space. Bellow is the trace from
the kernel...
The same image, works with:
- kvm-066 user space, kvm-068 kernel module (on 2.6.24 and 2.6.25)
- kvm-066 user space, vanilla kernel module (fro
On Thu, 8 May 2008, Linus Torvalds wrote:
>
> Also, we'd need to make it
>
> unsigned short flag:1;
>
> _and_ change spinlock_types.h to make the spinlock size actually match the
> required size (right now we make it an "unsigned int slock" even when we
> actually only use 16 bits).
Jan Kiszka wrote:
> Yang, Sheng wrote:
>> Hi
>>
>> This patchset enabled NMI support for KVM.
>>
>> The first three patches enabled NMI for in-kernel irqchip and NMI supporting
>> on VMX. The last patch enabled NMI watchdog in linux, can be used to test
>> the
>> NMI injection.
>>
>> In fact, th
On Thu, 8 May 2008, Andrea Arcangeli wrote:
>
> Actually I looked both at the struct and at the slab alignment just in
> case it was changed recently. Now after reading your mail I also
> compiled it just in case.
Put the flag after the spinlock, not after the "list_head".
Also, we'd need to m
Christian Borntraeger wrote:
> I really like 64 guest cpus as a good testcase for all kind of things.
>
Sure, I do the same kind of thing.
>> I think x86 (at least) is now using ticket locks, which is fair. Which
>> kernel are you seeing this problem on?
>>
>
> Sorry, forgot to mention
Am Donnerstag, 8. Mai 2008 schrieb Jeremy Fitzhardinge:
> Christian Borntraeger wrote:
> > On kvm I have seen some rare hangs in stop_machine when I used more guest
> > cpus than hosts cpus. e.g. 32 guest cpus on 1 host cpu triggered the
> > hang quite often. I could also reproduce the problem on a
On Thu, May 08, 2008 at 05:02:28PM +0300, Eren T?rkay wrote:
> Hello,
>
> An advisory about $subject was released today by secunia. The security flaw
> was fixed in QEmu SVN repository.
>
> Kvm uses some of the old version of qemu that I can't backport patch I
> grabbed
> from qemu svn reposit
On 08 May 2008 Thu 17:12:14 Daniel P. Berrange wrote:
> If you look at the KVM userspace code you'll see this patch is already
> included:
>
> http://git.kernel.org/?p=virt/kvm/kvm-userspace.git;a=commit;h=ce486fc1116e
>b53d40635be926bfa147ad520908
Thank you, I'll grab the patch and apply it to ta
Aurelien Jarno wrote:
> On Wed, May 07, 2008 at 04:40:58PM -0500, Anthony Liguori wrote:
>
>> The current logic of the can_receive handler is to allow packets whenever the
>> receiver is disabled or when there are descriptors available in the ring.
>>
>> I think the logic ought to be to allow pa
Hello,
An advisory about $subject was released today by secunia. The security flaw
was fixed in QEmu SVN repository.
Kvm uses some of the old version of qemu that I can't backport patch I grabbed
from qemu svn repository. Could you look at this issue and provide a patch?
http://secunia.com/adv
Christian Borntraeger wrote:
> On kvm I have seen some rare hangs in stop_machine when I used more guest
> cpus than hosts cpus. e.g. 32 guest cpus on 1 host cpu triggered the
> hang quite often. I could also reproduce the problem on a 4 way z/VM host
> with
> a 64 way guest.
>
I think that's
On Wed, May 07, 2008 at 04:40:58PM -0500, Anthony Liguori wrote:
> The current logic of the can_receive handler is to allow packets whenever the
> receiver is disabled or when there are descriptors available in the ring.
>
> I think the logic ought to be to allow packets whenever the receiver is
On kvm I have seen some rare hangs in stop_machine when I used more guest
cpus than hosts cpus. e.g. 32 guest cpus on 1 host cpu triggered the
hang quite often. I could also reproduce the problem on a 4 way z/VM host with
a 64 way guest.
It turned out that the guest was consuming all available cp
On Wed, 07 May 2008 16:35:54 +0200
Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
> Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
> Signed-off-by: Andrea Arcangeli <[EMAIL PROTECTED]>
Acked-by: Rik van Riel <[EMAIL PROTECTED]>
--
All rights reversed.
---
On Wed, 07 May 2008 16:35:55 +0200
Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
> Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
> Signed-off-by: Andrea Arcangeli <[EMAIL PROTECTED]>
Acked-by: Rik van Riel <[EMAIL PROTECTED]>
--
All rights reversed.
---
On Wed, 07 May 2008 16:35:53 +0200
Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
> # HG changeset patch
> # User Andrea Arcangeli <[EMAIL PROTECTED]>
> # Date 1210115129 -7200
> # Node ID d60d200565abde6a8ed45271e53cde9c5c75b426
> # Parent c5badbefeee07518d9d1acca13e94c981420317c
> invalidate_page
On Wed, 07 May 2008 16:35:51 +0200
Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
> Signed-off-by: Andrea Arcangeli <[EMAIL PROTECTED]>
> Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
> Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
Acked-by: Rik van Riel <[EMAIL PROTECTED]>
--
All rights r
This patch switches the kvm clocksource code over to use the
paravirt clock helpers, thereby making it compatible with xen.
Signed-off-by: Gerd Hoffmann <[EMAIL PROTECTED]>
---
arch/x86/Kconfig |1 +
arch/x86/kernel/kvmclock.c | 84 ---
2 fi
This patch switches the xen paravirt clock over to use the
generic paravirt clock code.
Cc: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Signed-off-by: Gerd Hoffmann <[EMAIL PROTECTED]>
---
arch/x86/xen/Kconfig |1 +
arch/x86/xen/time.c | 110 +-
2
Signed-off-by: Gerd Hoffmann <[EMAIL PROTECTED]>
---
arch/x86/kvm/x86.c | 63 +++
1 files changed, 53 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 979f983..6906d54 100644
--- a/arch/x86/kvm/x86.c
+++ b
Respin of the paravirt clock patch series.
On the host side the kvm paravirt clock is made compatible with the
xen clock.
On the guest side some xen code has been factored out into a separate
source file shared by both kvm and xen clock implementations.
This time it should work ok for kvm smp gu
The helper functions are intended to be used by both xen and kvm
paravirtual clock sources. Following patches of this series put
them into use. They are based on the xen code.
Cc: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Signed-off-by: Gerd Hoffmann <[EMAIL PROTECTED]>
---
arch/x86/Kconfig
Yang, Sheng wrote:
> Hi
>
> This patchset enabled NMI support for KVM.
>
> The first three patches enabled NMI for in-kernel irqchip and NMI supporting
> on VMX. The last patch enabled NMI watchdog in linux, can be used to test the
> NMI injection.
>
> In fact, this series should also included
FYI.
Please review it at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/228163
Regards
Paolo
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time
From 3a5e332c32a2ec585447505e2503d91cf2fb2a54 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Tue, 1 Apr 2008 14:47:59 +0800
Subject: [PATCH 2/4] KVM: IOAPIC/LAPIC: Enable NMI support
Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
arch/x86/kvm/lapic.c |3 ++-
arc
From 650cad44069541fcd9fea8be6a78837e812b3dfd Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Thu, 8 May 2008 09:58:50 +0800
Subject: [PATCH 1/4] KVM: LAPIC: Unified the duplicate calling of setting IRR
It's strange got two callings of setting IRR seperately for IOAPIC and IPI
From 176a066e5fd0d98cb63e910c93d57f7ec2850105 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Thu, 8 May 2008 16:00:59 +0800
Subject: [PATCH 4/4] KVM: Enable NMI Watchdog by PIT source
The NMI watchdog used LINT0 of LAPIC to deliver NMI. It didn't disable PIC
after switch to I
From 4942a5c35c97e5edb6fe1303e04fb86f25cac345 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Thu, 8 May 2008 16:00:57 +0800
Subject: [PATCH 3/4] KVM: VMX: Enable NMI with in-kernel irqchip
Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
arch/x86/kvm/vmx.c | 133
+
Hi
This patchset enabled NMI support for KVM.
The first three patches enabled NMI for in-kernel irqchip and NMI supporting
on VMX. The last patch enabled NMI watchdog in linux, can be used to test the
NMI injection.
In fact, this series should also included Jan Kiszka's patch to enable NMI for
Some monitor commands as well as the vm_stop() issued by the gdbstub on
external interruption so far deadlock on some vcpu locks in the kernel.
Patch below resolve the issue by temporarily or permanently stopping all
vcpu threads before issuing the related KVM IOCTLs.
Among other things, this patc
Resetting guests used to be racy, deadlock-prone, or simply broken (for
SMP). This patch fixes the issues - at least for me on x86 (tested on
Intel SMP host, UP and SMP guest, in-kernel und user space irqchip,
guest- and monitor-issued resets). Note that ia64 and powerpc may need
to look into the S
46 matches
Mail list logo
