From: Bruce Rogers brog...@novell.com
The boot option is missing from the documentation for the -drive parameter.
If there is a better way to descibe it, I'm all ears.
Signed-off-by: Bruce Rogers brog...@novell.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/qemu-options.hx
From: Gleb Natapov g...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/test/x86/emulator.c b/kvm/user/test/x86/emulator.c
index c6adbb5..db84c13 100644
--- a/kvm/user/test/x86/emulator.c
+++
From: Avi Kivity a...@redhat.com
Bit 4 of the page-fault error code can only be set if efer.nx=1.
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/test/x86/access.c b/kvm/user/test/x86/access.c
index 5addd15..3338fbc 100644
---
From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/test/x86/access.c b/kvm/user/test/x86/access.c
index dbc1213..0906691 100644
--- a/kvm/user/test/x86/access.c
+++ b/kvm/user/test/x86/access.c
@@
From: Avi Kivity a...@redhat.com
Some processors only set accessed bits if the translation is valid; allow
this behaviour. This squelchs errors running with EPT.
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/test/x86/access.c
From: Gleb Natapov g...@redhat.com
Test that ljmp with operand in IO memory works.
Signed-off-by: Gleb Natapov g...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/test/x86/emulator.c b/kvm/user/test/x86/emulator.c
index db84c13..4967d1f 100644
---
From: Michael S. Tsirkin m...@redhat.com
When vhost-net is disabled on reboot, we set msix mask notifier
to NULL to disable further mask/unmask notifications.
Code currently tries to pass this NULL to notifier,
leading to a crash. The right thing to do is
to add explicit APIs to enable/disable
From: Naphtali Sprei nsp...@redhat.com
Mainly removed unused/unnecessary files and references to them
Signed-off-by: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/README b/kvm/user/README
new file mode 100644
index 000..6a83831
---
From: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/test/x86/realmode.c b/kvm/user/test/x86/realmode.c
index bfc2942..bc4ed97 100644
--- a/kvm/user/test/x86/realmode.c
+++
From: Marcelo Tosatti mtosa...@redhat.com
* upstream-merge: (65 commits)
block: read-only: open cdrom as read-only when using monitor's change command
fix whitespace bogon in some versions of make
Changes to usb-linux to conform to coding style
Add KVM CFLAGS to vhost build
QMP:
From: Marcelo Tosatti mtosa...@redhat.com
* upstream-merge: (243 commits)
virtio-serial: Implement flow control for individual ports
virtio-serial: Discard data that guest sends us when ports aren't connected
virtio-serial: Apps should consume all data that guest sends out / Fix virtio
api
From: Naphtali Sprei nsp...@redhat.com
use correct 64 bit mode inline assembly constraints
use a canonical form address when writing to the MSR_KERNEL_GS_BASE MSR
Signed-off-by: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git
From: Jan Kiszka jan.kis...@siemens.com
This fixes make ARCH=i386 of the KVM micro tests on x86-64 hosts.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm/user/config-x86-common.mak b/kvm/user/config-x86-common.mak
index
On 05/04/2010 12:45 AM, H. Peter Anvin wrote:
I was trying to avoid a performance regression relative to the current
code, as it appears that some care was taken to avoid the memory reference.
I agree that it's probably negligible compared to the save/restore
code. If the x86 maintainers
I'm currently running 2.6.33.3 in a KVM instance emulating a core2duo
on 1 cpu with virtio HDs running on top of a core2duo host running 2.6.33.3.
qemu-kvm version 0.12.3. When doing:
echo noop /sys/block/vdd/queue/scheduler
I got:
[ 1424.438241] =
[
On 05/03/2010 07:32 PM, Joerg Roedel wrote:
On Tue, Apr 27, 2010 at 03:58:36PM +0300, Avi Kivity wrote:
So we probably need to upgrade gva_t to a u64. Please send this as
a separate patch, and test on i386 hosts.
Are there _any_ regular tests of KVM on i386 hosts? For me this is
On 05/04/2010 07:38 AM, Rusty Russell wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to me,
this might be a
Am 03.05.2010 23:26, schrieb Peter Lieven:
Hi Qemu/KVM Devel Team,
i'm using qemu-kvm 0.12.3 with latest Kernel 2.6.33.3.
As backend we use open-iSCSI with dm-multipath.
Multipath is configured to queue i/o if no path is available.
If we create a failure on all paths, qemu starts to
On 05/04/2010 10:03 AM, CaT wrote:
I'm currently running 2.6.33.3 in a KVM instance emulating a core2duo
on 1 cpu with virtio HDs running on top of a core2duo host running 2.6.33.3.
qemu-kvm version 0.12.3.
Doesn't appear to be related to kvm. Copying lkml.
When doing:
echo
On Tue, May 04 2010, Rusty Russell wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to me,
this might be
On 05/03/2010 08:03 PM, Michael Tokarev wrote:
Michael, can you try to use -cpu host,-vme and see if that makes a
difference?
With -cpu host,-vme winNT boots just fine as with just -cpu host.
I also tried with -cpu qemu64 and kvm64, with +vme and -vme (4
combinations in total) - in all cases
On Tue, May 04, 2010 at 03:53:57AM -0400, Avi Kivity wrote:
On 05/03/2010 07:32 PM, Joerg Roedel wrote:
On Tue, Apr 27, 2010 at 03:58:36PM +0300, Avi Kivity wrote:
So we probably need to upgrade gva_t to a u64. Please send this as
a separate patch, and test on i386 hosts.
On 05/04/2010 12:11 PM, Roedel, Joerg wrote:
On Tue, May 04, 2010 at 03:53:57AM -0400, Avi Kivity wrote:
On 05/03/2010 07:32 PM, Joerg Roedel wrote:
On Tue, Apr 27, 2010 at 03:58:36PM +0300, Avi Kivity wrote:
So we probably need to upgrade gva_t to a u64. Please send this
This unbreaks the monitor quit command for qemu-kvm.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
qemu-kvm.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/qemu-kvm.c b/qemu-kvm.c
index 91f0222..43d599d 100644
--- a/qemu-kvm.c
+++ b/qemu-kvm.c
@@ -2047,6
On 05/04/2010 05:04 AM, Marcelo Tosatti wrote:
The recent changes to emulate string instructions without entering guest
mode exposed a bug where pending interrupts are not properly reflected
in ready_for_interrupt_injection.
The result is that userspace overwrites a previously queued interrupt,
On 04/28/2010 12:50 PM, Takuya Yoshikawa wrote:
Hi Marcelo, Avi,
I updated the patch as follows.
Changelog:
1. Inserted one r = -ENOMEM; line following Avi's advice.
2. Little change of explanation about performance improvements.
I'm now testing and cleaning up my next patch series based
On Tue, May 04, 2010 at 05:20:02AM -0400, Avi Kivity wrote:
On 05/04/2010 12:11 PM, Roedel, Joerg wrote:
On Tue, May 04, 2010 at 03:53:57AM -0400, Avi Kivity wrote:
On 05/03/2010 07:32 PM, Joerg Roedel wrote:
On Tue, Apr 27, 2010 at 03:58:36PM +0300, Avi Kivity wrote:
On 04/27/2010 12:46 PM, Michael Tokarev wrote:
I've a debian bugreport that claims to have a fix
for apparently wrong keymap for usb keyboard. I
noticed this before with ps/2 keyboard too, the
sympthoms were that e.g windows keys were not
working in guests, but later on that has been
fixed.
On 05/04/2010 12:37 PM, Roedel, Joerg wrote:
This is the lockdep warning I get when I start booting a Linux kernel.
It is with the nested-npt patchset but the warning occurs without it too
(slightly different backtraces then).
[60390.953424]
On 05/04/2010 12:45 PM, Avi Kivity wrote:
Just a silly bug. kvm_pdptr_read() can cause a guest memory read on
svm, in this case with the mmu lock taken. I'll post something to fix
it.
I guess this was not reported because most svm machines have npt, and
this requires npt=0 to trigger.
On svm, kvm_read_pdptr() may require reading guest memory, which can sleep.
Push the spinlock into mmu_alloc_roots(), and only take it after we've read
the pdptr.
Signed-off-by: Avi Kivity a...@redhat.com
---
Marcelo, dropping and re-acquiring the lock before mmu_sync_roots(), is fine,
yes?
Annotate it thusly.
Signed-off-by: Avi Kivity a...@redhat.com
---
arch/x86/kvm/kvm_cache_regs.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/kvm_cache_regs.h b/arch/x86/kvm/kvm_cache_regs.h
index cff851c..d2a98f8 100644
---
On Tue, May 04, 2010 at 02:08:24PM +0930, Rusty Russell wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to
On Tue, May 04, 2010 at 06:03:50AM -0400, Avi Kivity wrote:
On svm, kvm_read_pdptr() may require reading guest memory, which can sleep.
Push the spinlock into mmu_alloc_roots(), and only take it after we've read
the pdptr.
This fixes the lockdep issue for me. Thanks.
Tested-by: Joerg Roedel
David,
This is an amended pull request: I have rebased the tree to the
correct patches. This has been through basic tests and seems
to work fine here.
The following tree includes a couple of enhancements that help vhost-net.
Please pull them for net-next. Another set of patches is under
hi kevin,
i set a breakpint at bmdma_active_if. the first 2 breaks encountered
when the last path in the multipath
failed, but the assertion was not true.
when i kicked one path back in the breakpoint was reached again, this
time leading to an assert.
the stacktrace is from the point shortly
On Tue, May 04, 2010 at 05:50:50AM -0400, Avi Kivity wrote:
On 05/04/2010 12:45 PM, Avi Kivity wrote:
Just a silly bug. kvm_pdptr_read() can cause a guest memory read on
svm, in this case with the mmu lock taken. I'll post something to fix
it.
I guess this was not reported
Wallclock writing uses an unprotected global variable to hold the version;
this can cause one guest to interfere with another if both write their
wallclock at the same time.
Signed-off-by: Avi Kivity a...@redhat.com
---
arch/x86/kvm/x86.c | 12 ++--
1 files changed, 10 insertions(+), 2
On 05/04/2010 03:00 PM, Roedel, Joerg wrote:
On Tue, May 04, 2010 at 05:50:50AM -0400, Avi Kivity wrote:
On 05/04/2010 12:45 PM, Avi Kivity wrote:
Just a silly bug. kvm_pdptr_read() can cause a guest memory read on
svm, in this case with the mmu lock taken. I'll post something to
Avi Kivity wrote:
On 05/03/2010 08:03 PM, Michael Tokarev wrote:
Michael, can you try to use -cpu host,-vme and see if that makes a
difference?
With -cpu host,-vme winNT boots just fine as with just -cpu host.
I also tried with -cpu qemu64 and kvm64, with +vme and -vme (4
combinations in
Am 04.05.2010 13:38, schrieb Peter Lieven:
hi kevin,
i set a breakpint at bmdma_active_if. the first 2 breaks encountered
when the last path in the multipath
failed, but the assertion was not true.
when i kicked one path back in the breakpoint was reached again, this
time leading to an
Andre Przywara wrote:
[]
I managed to get a NT4 CD and can acknowledge the issues you see. I am
about to debug this now.
With -cpu host (on a AMD K8, similar to Michael's) I get to the point
Michael mentioned:
Microsoft (R) Windows NT (TM) Version 4.0 (Build 1381).
1 System Processor [512
Hi, sorry for sending from my personal account.
The following series are all from me:
From: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
The 3rd version of moving dirty bitmaps to user space.
From this version, we add x86 and ppc and asm-generic people to CC lists.
[To KVM people]
Although we always allocate a new dirty bitmap in x86's get_dirty_log(),
it is only used as a zero-source of copy_to_user() and freed right after
that when memslot is clean. This patch uses clear_user() instead of doing
this unnecessary zero-source allocation.
Performance improvement: as we can
This patch introduces is_dirty member for each memory slot.
Using this member, we remove the dirty bitmap scans which are done in
get_dirty_log().
This is important for moving dirty bitmaps to user space because we don't
have any good ways to check bitmaps in user space with low cost and scanning
We will change the vmalloc() and vfree() to do_mmap() and do_munmap() later.
This patch makes it easy and cleanup the code.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
Signed-off-by: Fernando Luis Vazquez Cao ferna...@oss.ntt.co.jp
---
virt/kvm/kvm_main.c | 27
During the work of KVM's dirty page logging optimization, we encountered
the need of copy_in_user() for 32-bit x86 and ppc: these will be used for
manipulating dirty bitmaps in user space.
So we implement copy_in_user() for 32-bit with existing generic copy user
helpers.
Signed-off-by: Takuya
During the work of KVM's dirty page logging optimization, we encountered
the need of manipulating bitmaps in user space efficiantly. To achive this,
we introduce a uaccess function for setting a bit in user space following
Avi's suggestion.
KVM is now using dirty bitmaps for live-migration and
During the work of KVM's dirty page logging optimization, we encountered
the need of copy_in_user() for 32-bit ppc and x86: these will be used for
manipulating dirty bitmaps in user space.
So we implement copy_in_user() for 32-bit with __copy_tofrom_user().
Signed-off-by: Takuya Yoshikawa
From: Jan Kiszka jan.kis...@siemens.com
It is not safe to retrieve the KVM internal state of a given cpu
while its potentially modifying it.
Queue the request to run on cpu context, similarly to qemu-kvm.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/kvm-all.c
run_on_cpu allows to execute work on a given CPUState context.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/cpu-all.h
===
--- qemu.orig/cpu-all.h
+++ qemu/cpu-all.h
@@ -818,6 +818,7 @@ void
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/cpu-all.h
===
--- qemu.orig/cpu-all.h
+++ qemu/cpu-all.h
@@ -818,6 +818,7 @@ void cpu_watchpoint_remove_all(CPUState
void cpu_single_step(CPUState *env, int enabled);
Process INIT/SIPI requests and enable -smp 1.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/kvm-all.c
===
--- qemu.orig/kvm-all.c
+++ qemu/kvm-all.c
@@ -593,11 +593,6 @@ int kvm_init(int smp_cpus)
int ret;
During the work of KVM's dirty page logging optimization, we encountered
the need of manipulating bitmaps in user space efficiantly. To achive this,
we introduce a uaccess function for setting a bit in user space following
Avi's suggestion.
KVM is now using dirty bitmaps for live-migration and
Although we can use *_le_bit() helpers to treat bitmaps le arranged,
having le bit offset calculation as a seperate macro gives us more freedom.
For example, KVM has le arranged dirty bitmaps for VGA, live-migration
and they are used in user space too. To avoid bitmap copies between kernel
and
This is not to break the build for other architectures than x86 and ppc.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
Signed-off-by: Fernando Luis Vazquez Cao ferna...@oss.ntt.co.jp
---
arch/ia64/include/asm/kvm_host.h|5 +
arch/powerpc/include/asm/kvm_host.h |6
We move dirty bitmaps to user space.
- Allocation and destruction: we use do_mmap() and do_munmap().
The new bitmap space is twice longer than the original one and we
use the additional space for double buffering: this makes it
possible to update the active bitmap while letting the user
Now that dirty bitmaps are accessible from user space, we export the
addresses of these to achieve zero-copy dirty log check:
KVM_GET_USER_DIRTY_LOG_ADDR
We also need an API for triggering dirty bitmap switch to take the full
advantage of double buffered bitmaps.
KVM_SWITCH_DIRTY_LOG
See
We use new API for light dirty log access if KVM supports it.
This conflicts with Marcelo's patches. So please take this as a sample patch.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
kvm/include/linux/kvm.h | 11 ++
qemu-kvm.c | 81
On Mon, May 03, 2010 at 09:38:54PM +0800, Gui Jianfeng wrote:
Hi Marcelo
Actually, it doesn't only affect kvm_mmu_change_mmu_pages() but also affects
kvm_mmu_remove_some_alloc_mmu_pages()
which is called by mmu shrink routine. This will induce upper layer get a
wrong number, so i think
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Zero cpu_single_env before leaving global lock protection, and
restore on return.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/kvm-all.c
===
--- qemu.orig/kvm-all.c
+++ qemu/kvm-all.c
@@ -846,9 +846,11 @@ int
From: Jan Kiszka jan.kis...@siemens.com
Validate that KVM vcpu state is only read/written from cpu thread itself
or that cpu is stopped.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/target-i386/kvm.c
===
---
KVM Forum topic ideas
- mgmt interface (qemud)
- working breakout sessions are welcome at the Forum
stable tree
- have a volunteer (thanks Justin)
- Anthony will write up proposal which is basically
- bug fixes actively proposed for stable tree
- stable maintainer collects and applies
-
On Mon, May 03, 2010 at 05:18:54PM +0300, Avi Kivity wrote:
cr0.ts may change between entries, so we copy cr0 to HOST_CR0 before each
entry. That is slow, so instead, set HOST_CR0 to have TS set unconditionally
(which is a safe value), and issue a clts() just before exiting vcpu context
if
On Tuesday 04 May 2010, Takuya Yoshikawa wrote:
Although we can use *_le_bit() helpers to treat bitmaps le arranged,
having le bit offset calculation as a seperate macro gives us more freedom.
For example, KVM has le arranged dirty bitmaps for VGA, live-migration
and they are used in user
Bugs item #2996643, was opened at 2010-05-04 17:23
Message generated for change (Tracker Item Submitted) made by edolstra
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2996643group_id=180599
Please note that this message will contain a full copy of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
Saw a long thread on this back in Oct. but did not see if this was
resolved or not.
We are experiencing hrtimer: interrupt took huge_number ns errors on
the guest console with -smp 2 running on an Intel host. Both are running
2.6.33.3
Make it possible to download the winutils.iso file right
from its repository, making very convenient for users
to perform windows testing.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/get_started.py | 65 +++---
1 files changed,
On 05/04/2010 06:03 PM, Arnd Bergmann wrote:
On Tuesday 04 May 2010, Takuya Yoshikawa wrote:
Although we can use *_le_bit() helpers to treat bitmaps le arranged,
having le bit offset calculation as a seperate macro gives us more freedom.
For example, KVM has le arranged dirty bitmaps for
On 05/04/2010 03:02 PM, Avi Kivity wrote:
Wallclock writing uses an unprotected global variable to hold the version;
this can cause one guest to interfere with another if both write their
wallclock at the same time.
Signed-off-by: Avi Kivitya...@redhat.com
This was pointed out by
On Tue, May 04, 2010 at 03:02:24PM +0300, Avi Kivity wrote:
Wallclock writing uses an unprotected global variable to hold the version;
this can cause one guest to interfere with another if both write their
wallclock at the same time.
makes sense to me.
ACK.
--
To unsubscribe from this
On 05/04/2010 06:27 PM, Andre Przywara wrote:
3. In all other cases so far it BSoDs with STOP 0x3E error
right before displaying that kernel message.
MSDN talks about a mulitprocessor configuration error:
http://msdn.microsoft.com/en-us/library/ms819006.aspx
I suspected the offline CPUs in
On Mon, May 03, 2010 at 05:19:08PM +0300, Avi Kivity wrote:
KVM_REQ_KICK poisons vcpu-requests by having a bit set during normal
operation. This causes the fast path check for a clear vcpu-requests
to fail all the time, triggering tons of atomic operations.
Avi,
Do you have numbers?
Fix
On 05/04/2010 07:31 PM, Marcelo Tosatti wrote:
On Mon, May 03, 2010 at 05:19:08PM +0300, Avi Kivity wrote:
KVM_REQ_KICK poisons vcpu-requests by having a bit set during normal
operation. This causes the fast path check for a clear vcpu-requests
to fail all the time, triggering tons of
On Tue, May 04, 2010 at 04:01:35PM +0200, Kevin Wolf wrote:
Great, I'm going to submit it as a proper patch then.
Christoph, by now I'm pretty sure it's right, but can you have another
look if this is correct, anyway?
It looks correct to me - we really shouldn't update the the fields
until
On Sun, 2010-05-02 at 07:53 -0700, Avi Kivity wrote:
The fpu code currently uses current-thread_info-status TS_XSAVE as
a way to distinguish between XSAVE capable processors and older processors.
The decision is not really task specific; instead we use the task status to
avoid a global memory
On Sun, 2010-05-02 at 07:53 -0700, Avi Kivity wrote:
Currently all fpu state access is through tsk-thread.xstate. Since we wish
to generalize fpu access to non-task contexts, wrap the state in a new
'struct fpu' and convert existing access to use an fpu API.
Signal frame handlers are not
On Tue, 2010-05-04 at 00:41 -0700, Avi Kivity wrote:
On 05/04/2010 12:45 AM, H. Peter Anvin wrote:
I was trying to avoid a performance regression relative to the current
code, as it appears that some care was taken to avoid the memory reference.
I agree that it's probably negligible
On 05/04/2010 11:15 AM, Suresh Siddha wrote:
On Tue, 2010-05-04 at 00:41 -0700, Avi Kivity wrote:
On 05/04/2010 12:45 AM, H. Peter Anvin wrote:
I was trying to avoid a performance regression relative to the current
code, as it appears that some care was taken to avoid the memory reference.
virtio: put last_used and last_avail index into ring itself.
Generally, the other end of the virtio ring doesn't need to see where
you're up to in consuming the ring. However, to completely understand
what's going on from the outside, this information must be exposed.
For example, if you
This patch series fixes I bug I just found with kvmclock,
when I booted into a kernel without kvmclock enabled.
Since I am setting msrs, I took the oportunity to
use yet another function from upstream qemu (patch 1).
Enjoy
Glauber Costa (2):
replace set_msr_entry with kvm_msr_entry
turn off
this is yet another function that upstream qemu implements,
so we can just use its implementation.
Signed-off-by: Glauber Costa glom...@redhat.com
---
qemu-kvm-x86.c| 39 ---
target-i386/kvm.c |3 +++
2 files changed, 19 insertions(+), 23
Currently, in the linux kernel, we reset kvmclock if we are rebooting
into a crash kernel through kexec. The rationale, is that a new kernel
won't follow the same memory addresses, and the memory where kvmclock is
located in the first kernel, will be something else in the second one.
We don't do
On Fri, Feb 19, 2010 at 12:22:20AM +0200, Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to me,
this might be a first step to cleaning them.
The
On Tue, Apr 20, 2010 at 02:46:35AM +0100, Jamie Lokier wrote:
Does this mean that virtio-blk supports all three combinations?
1. FLUSH that isn't a barrier
2. FLUSH that is also a barrier
3. Barrier that is not a flush
1 is good for fsync-like operations;
2 is good for
On Tue, May 04, 2010 at 08:54:59PM +0200, Christoph Hellwig wrote:
On Fri, Feb 19, 2010 at 12:22:20AM +0200, Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems
On Tue, May 04, 2010 at 09:56:18PM +0300, Michael S. Tsirkin wrote:
On Tue, May 04, 2010 at 08:54:59PM +0200, Christoph Hellwig wrote:
On Fri, Feb 19, 2010 at 12:22:20AM +0200, Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph,
On Tue, May 04, 2010 at 08:56:14PM +0200, Christoph Hellwig wrote:
On Tue, Apr 20, 2010 at 02:46:35AM +0100, Jamie Lokier wrote:
Does this mean that virtio-blk supports all three combinations?
1. FLUSH that isn't a barrier
2. FLUSH that is also a barrier
3. Barrier that is not
Jens Axboe wrote:
On Tue, May 04 2010, Rusty Russell wrote:
ISTR someone mentioning a desire for such an API years ago, so CC'ing the
usual I/O suspects...
It would be nice to have a more fuller API for this, but the reality is
that only the flush approach is really workable. Even just
On 05/04/2010 08:35 AM, Glauber Costa wrote:
This patch series fixes I bug I just found with kvmclock,
when I booted into a kernel without kvmclock enabled.
Since I am setting msrs, I took the oportunity to
use yet another function from upstream qemu (patch 1).
Enjoy
Glauber Costa (2):
Rusty Russell wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to me,
this might be a first step to
Marcelo Tosatti wrote:
On Mon, May 03, 2010 at 09:38:54PM +0800, Gui Jianfeng wrote:
Hi Marcelo
Actually, it doesn't only affect kvm_mmu_change_mmu_pages() but also affects
kvm_mmu_remove_some_alloc_mmu_pages()
which is called by mmu shrink routine. This will induce upper layer get a
Currently, kvm_mmu_zap_page() returning the number of freed children sp.
This might confuse the caller, because caller don't know the actual freed
number. Let's make kvm_mmu_zap_page() return the number of pages it actually
freed.
Signed-off-by: Gui Jianfeng guijianf...@cn.fujitsu.com
---
Sometime cmpxchg_gpte doesn't modify gpte, in such case, don't mark
page table page as dirty.
Signed-off-by: Gui Jianfeng guijianf...@cn.fujitsu.com
---
arch/x86/kvm/paging_tmpl.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/paging_tmpl.h
Gentlemen,
Reaching out with a non-development question, sorry if it's not
appropriate here.
I'm looking for a way to improve Linux SMP VMs performance under KVM.
My preliminary results show that single vCPU Linux VMs perform up to 10
times better than 4vCPU Linux VMs (consolidated
Fix a debug output error in walk_addr
Signed-off-by: Gui Jianfeng guijianf...@cn.fujitsu.com
---
arch/x86/kvm/paging_tmpl.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
index 89d66ca..d2c5164 100644
---
On Tue, May 04, 2010 at 11:37:37AM +0300, Avi Kivity wrote:
On 05/04/2010 10:03 AM, CaT wrote:
I'm currently running 2.6.33.3 in a KVM instance emulating a core2duo
on 1 cpu with virtio HDs running on top of a core2duo host running 2.6.33.3.
qemu-kvm version 0.12.3.
Can you try commit
On Wed, May 5, 2010 at 10:32 AM, Yong Zhang yong.zh...@windriver.com wrote:
On Tue, May 04, 2010 at 11:37:37AM +0300, Avi Kivity wrote:
On 05/04/2010 10:03 AM, CaT wrote:
I'm currently running 2.6.33.3 in a KVM instance emulating a core2duo
on 1 cpu with virtio HDs running on top of a core2duo
On Tue, 04 May 2010 19:08:23 +0300
Avi Kivity a...@redhat.com wrote:
On 05/04/2010 06:03 PM, Arnd Bergmann wrote:
On Tuesday 04 May 2010, Takuya Yoshikawa wrote:
...
So let us use the le bit offset calculation part by defining it as a new
macro: generic_le_bit_offset() .
Does
1 - 100 of 104 matches
Mail list logo
