Re: [PATCH 0/3] Remove interrupt stack table usage from x86_64 kernel

2008-12-26 Thread Ingo Molnar
* Avi Kivity a...@redhat.com wrote: The interrupt stack table (IST) mechanism is the only thing preventing kvm from deferring saving and reloading of some significant state. It is also somewhat complicated. Remove it by switching the special exceptions to use the normal irqstack. Avi

Re: [PATCH] KVM: userspace: Remove duplicated functionality for cpuid processing

2008-12-26 Thread Alexander Graf
Hi Amit, On 26.12.2008, at 07:02, Amit Shah wrote: host_cpuid is now available in target-i386/helper.c. Remove the duplicated code now in kvm-specific code. Signed-off-by: Amit Shah amit.s...@redhat.com --- qemu/qemu-kvm-x86.c | 70 --- 1

[PATCH 0/4] Remove interrupt stack table usage from x86_64 kernel (v2)

2008-12-26 Thread Avi Kivity
The interrupt stack table (IST) mechanism is the only thing preventing kvm from deferring saving and reloading of some significant state. It is also somewhat complicated. Remove it by switching the special exceptions to use the normal irqstack. Changes from v1: - rebase on tip/master - as a

[PATCH 1/4] x86: drop the use of the tss interrupt stack table (IST)

2008-12-26 Thread Avi Kivity
The IST is the only thing that requires a valid TSS while running in kernel mode. Dropping its use unlocks an optimization opportunity for kvm: if we don't need a valid TSS while in kernel mode we can defer the use of the VMLOAD/VMSAVE instructions until the next context switch, reducing the

[PATCH 2/4] x86: Consolidate irq stack switching to a single macro

2008-12-26 Thread Avi Kivity
Instead of scattering the logic around, move all stack switching logic into a single macro which calls a caller-supplied logic. This makes changing the logic easier and improves readability. Signed-off-by: Avi Kivity a...@redhat.com --- arch/x86/kernel/entry_64.S | 59

[PATCH 4/4] x86: Move NMI back to interrupt stack

2008-12-26 Thread Avi Kivity
Now that interrupt stack switching is atomic, we can move the NMI handler to the interrupt stack. Signed-off-by: Avi Kivity a...@redhat.com --- arch/x86/kernel/entry_64.S |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/x86/kernel/entry_64.S

[PATCH 3/4] x86: Make interrupt stack switching atomic

2008-12-26 Thread Avi Kivity
Instead of relying on pda.irqcount to tell us whether we're already in an interrupt or not, examine the stack pointer directly. This makes the switch atomic (since there's no window between incrementing the counter and switching the stack where an NMI could see the new counter but the old stack),

Re: how increase/decrease ram on running vm ?

2008-12-26 Thread Ryota OZAKI
Hi, http://www.linux-kvm.com/content/memory-ballooning-feature-coming-soon-kvm This page might help you. Regards, ozaki-r 2008/12/26 Василец Дмитрий d.vasil...@peterhost.ru: how increase/decrease ram on running vm ? i found virtio_balloon module , but don't know how it work. -- To

Re: [PATCH 0/4] Remove interrupt stack table usage from x86_64 kernel (v2)

2008-12-26 Thread Ingo Molnar
* Avi Kivity a...@redhat.com wrote: The interrupt stack table (IST) mechanism is the only thing preventing kvm from deferring saving and reloading of some significant state. It is also somewhat complicated. Remove it by switching the special exceptions to use the normal irqstack.

Re: [PATCH 0/4] Remove interrupt stack table usage from x86_64 kernel (v2)

2008-12-26 Thread Ingo Molnar
* Ingo Molnar mi...@elte.hu wrote: They have the following commit IDs, and they are also in tip/master: 921e521: x86: move NMI back to interrupt stack 36ef6c9: x86: make interrupt stack switching atomic dd64891: x86: consolidate irq stack switching to a single macro 955a368: x86: drop

Re: how increase/decrease ram on running vm ?

2008-12-26 Thread Василец Дмитрий
i read this , but i haven't balloon in cli. В Птн, 26/12/2008 в 23:25 +0900, Ryota OZAKI пишет: Hi, http://www.linux-kvm.com/content/memory-ballooning-feature-coming-soon-kvm This page might help you. Regards, ozaki-r 2008/12/26 Василец Дмитрий d.vasil...@peterhost.ru: how

Re: how increase/decrease ram on running vm ?

2008-12-26 Thread Ryota OZAKI
Have you tried decreasing memory? AFAIK, current ballooning cannot increase memory. Regards, ozaki-r 2008/12/27 Василец Дмитрий d.vasil...@peterhost.ru: i read this , but i haven't balloon in cli. В Птн, 26/12/2008 в 23:25 +0900, Ryota OZAKI пишет: Hi,

Re: how increase/decrease ram on running vm ?

2008-12-26 Thread Ryota OZAKI
2008/12/27 Ryota OZAKI ozaki.ry...@gmail.com: Have you tried decreasing memory? AFAIK, current ballooning cannot increase memory. oops, i mean ballooning cannot increase memory over the amount of memory specified in qemu/kvm arguments. Regards, ozaki-r 2008/12/27 Василец Дмитрий

BUG() with SCSI-interfaced disk images

2008-12-26 Thread John Morrissey
I'm encountering a kernel BUG() in guests using SCSI-interfaced disk images. I've tried with the Debian packaging of KVM 79 and 82; both exhibit the same behavior (disclaimer: Debian has about a dozen patches in their kvm packaging, but they all seem to be changes to the build/install process or

Re: [Qemu-devel] Re: gdbstub: packet reply is too long

2008-12-26 Thread Daniel Jacobowitz
On Sun, Dec 21, 2008 at 12:44:04AM +0100, Jan Kiszka wrote: And that means setting current_gdbarch while keeping target_gdbarch - that's where reality (existing gdb code) bites us. Again, I'm not arguing against fixing this, I'm arguing in keeping qemu's workaround until this is done. I will