The kvm-userspace commit is c41ab776181097efb6e6fbb5aa33b4a1f5df3d4f and
kernel commit is 89075253714a299236b8debfbfdcb670a3932a1b.
I just noticed that the userspace is not kvm-57.
Thanks
Yunfeng
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年12月19日 14:30
>To
Ingo Molnar wrote:
>> While the change mentions that it fixes a time warp bug, it also says
>> it should be rare. So clearly kvm smp tsc handing is buggy.
>> Ingo/Thomas, (or anybody else), do you have any insight as to what kvm
>> can be doing wrong to trigger this behavior?
>>
>
> hm. T
Zhao, Yunfeng wrote:
> Retested it on KVM-57.
> It has been fixed already.
>
Actually, the fix is post kvm-57. What kvm-userspace.git commit did you
test?
--
error compiling committee.c: too many arguments to function
-
Retested it on KVM-57.
It has been fixed already.
Thanks a lot!
Yunfeng
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年12月19日 0:18
>To: Zhao, Yunfeng
>Cc: kvm-devel
>Subject: Re: [kvm-devel] KVM Test result, kernel 5ca24d9.., userspace 120e0c8..
>
>Zhao, Yunfen
Cam Macdonell wrote:
> Cam Macdonell wrote:
>> Dor Laor wrote:
>>> Cam Macdonell wrote:
Dor Laor wrote:
> Christian Borntraeger wrote:
>> Am Mittwoch, 12. Dezember 2007 schrieb Dor Laor:
>>> Christian Borntraeger wrote:
Am Mittwoch, 12. Dezember 2007 schrieb Dor Laor:
* Avi Kivity <[EMAIL PROTECTED]> wrote:
> Booting RHEL 5 i386 in kvm with -no-kvm-irqchip -smp 4 will hang in udev.
> I bisected this to a change in the _guest_ kernel:
>
>> commit 95492e4646e5de8b43d9a7908d6177fb737b61f0
>> Author: Ingo Molnar <[EMAIL PROTECTED]>
>> Date: Fri Feb 16 01:27:34
Cam Macdonell wrote:
> Dor Laor wrote:
>> Cam Macdonell wrote:
>>> Dor Laor wrote:
Christian Borntraeger wrote:
> Am Mittwoch, 12. Dezember 2007 schrieb Dor Laor:
>> Christian Borntraeger wrote:
>>> Am Mittwoch, 12. Dezember 2007 schrieb Dor Laor:
--- a/drivers/net/virtio_
Booting RHEL 5 i386 in kvm with -no-kvm-irqchip -smp 4 will hang in
udev. I bisected this to a change in the _guest_ kernel:
> commit 95492e4646e5de8b43d9a7908d6177fb737b61f0
> Author: Ingo Molnar <[EMAIL PROTECTED]>
> Date: Fri Feb 16 01:27:34 2007 -0800
>
> [PATCH] x86: rewrite SMP TSC s
Christian Ehrhardt wrote:
> Subject: [PATCH][UPDATE] kvm-userspace: sync icache for more architectures
> From: Christian Ehrhardt <[EMAIL PROTECTED]>
>
> A ia64 patch introduced kvm_sync_icache within a ifdef __ia64__, but the
> concept of split caches is not bound to ia64. This patch replaces the
Carlo Marcelo Arenas Belon wrote:
> The following patch (which is composed of 3 different patches from a series)
> has been validated to solve compilation issues observed with kvm-56 in x86
> with kernels older than 2.6.21 and are posted here for testing and debate.
>
> The main points accomplished
Ryan Harper wrote:
> * Ryan Harper <[EMAIL PROTECTED]> [2007-12-14 09:36]:
>
>> * Avi Kivity <[EMAIL PROTECTED]> [2007-12-14 08:49]:
>>
>>> Ryan Harper wrote:
>>>
Add printk_ratelimit check in front of printk. This prevents spamming
of the message during 32-bit ubuntu 6.06
Carlo Marcelo Arenas Belon wrote:
> The following patch eliminates the uninitialized mem pointer, using
> instead the corresponding entry from the slots array to fix :
>
> libkvm.c:580: warning: 'mem' is used uninitialized in this function
>
> Also changes the formatting type for phys_addr to lo
Zhao, Yunfeng wrote:
> Save/restore still passes on IA32e host but fails on IA32 host.
>
This is now fixed.
--
error compiling committee.c: too many arguments to function
-
SF.Net email is sponsored by:
Check out the n
The major focus for this release is a qemu-cvs merge, which brings many
new features, some introduced by kvm developers. Examples are
improved usb support and the new -drive qemu option.
While we've tested this carefully, this is a big merge so please handle
this release with care and report
Marcelo Tosatti wrote:
> Hi,
>
> The following is an improvement on top of an earlier patch by Izik. It
> increases pagefault scalability for SMP guests by allowing concurrent
> guest walking, allocation and instruction emulation on the fault path.
>
> The test being used is pft, which starts a nu
Dong, Eddie wrote:
>> Dong, Eddie wrote:
>>
>>> host side TLB flush can be merged together if multiple
>>> spte need to be write-protected.
>>>
>>> Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
>>>
>>> diff --git a/drivers/kvm/mmu.c b/drivers/kvm/mmu.c
>>> index 92ac0d1..749db46 100644
On Tue, 2007-12-18 at 08:26 -0500, Marcelo Tosatti wrote:
> Hi,
>
> The following is an improvement on top of an earlier patch by Izik. It
i would say MUCH improvement :)
> increases pagefault scalability for SMP guests by allowing concurrent
> guest walking, allocation and instruction emulation
On Tue, Dec 18, 2007 at 08:26:14AM -0500, Marcelo Tosatti wrote:
> + page = __gfn_to_page(vcpu->kvm, gpa >> PAGE_SHIFT);
> + spin_lock(&vcpu->kvm->mmu_lock);
> kvm_mmu_pte_write(vcpu, gpa, val, bytes);
This should be the gfn which the new pte points to, not its address.
--
Hi,
The following is an improvement on top of an earlier patch by Izik. It
increases pagefault scalability for SMP guests by allowing concurrent
guest walking, allocation and instruction emulation on the fault path.
The test being used is pft, which starts a number of threads
allocating and wri
Subject: [PATCH][UPDATE] kvm-userspace: simplify mmio callback
From: Christian Ehrhardt <[EMAIL PROTECTED]>
Merging the read[bwlq]/write[bwlq] callback callback pointers to
mmio_read/write functions simplifies the callback interface.
On the qemu side it now uses the cpu_physical_memory_rw functio
Subject: [PATCH][UPDATE] kvm-userspace: sync icache for more architectures
From: Christian Ehrhardt <[EMAIL PROTECTED]>
A ia64 patch introduced kvm_sync_icache within a ifdef __ia64__, but the
concept of split caches is not bound to ia64. This patch replaces the the
call to kvm_synch_icache by t
Hollis Blanchard wrote:
> On Fri, 2007-12-14 at 10:07 +0100, Christian Ehrhardt wrote:
>> Hollis Blanchard wrote:
>>> A comment to explain why the icache needs flushing only in the KVM
>> case
>>> would be useful. Other than that I'm fine with it.
>>>
>>> Signed-off-by: Hollis Blanchard <[EMAIL PRO
Rusty Russell wrote:
On Wednesday 12 December 2007 23:54:00 Dor Laor wrote:
commit 763769621d271d92204ed27552d75448587c1ac0
Author: Dor Laor <[EMAIL PROTECTED]>
Date: Wed Dec 12 14:52:00 2007 +0200
[virtio-net][PATCH] Don't arm tx hrtimer with a constant 50us each
transmit
The cur
The following patch (which is composed of 3 different patches from a series)
has been validated to solve compilation issues observed with kvm-56 in x86
with kernels older than 2.6.21 and are posted here for testing and debate.
The main points accomplished (in the same sequence that the snippets) a
Cam Macdonell wrote:
Dor Laor wrote:
> Cam Macdonell wrote:
>> Dor Laor wrote:
>>> Christian Borntraeger wrote:
Am Mittwoch, 12. Dezember 2007 schrieb Dor Laor:
> Christian Borntraeger wrote:
>> Am Mittwoch, 12. Dezember 2007 schrieb Dor Laor:
>>> --- a/drivers/net/virtio_net.c
Hollis already pointed me to the mkasm-values patches which are the
continuation of the mkasm-offset discussion on lkml Hollis last patch was based
on.
As stated before by Xiantao and Hollis in this thread the mkasm-value patches
are not yet accepted upstream, but may be useful for us.
Based on
Bugs item #1852938, was opened at 2007-12-18 15:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1852938&group_id=180599
Please note that this message will contain a full copy
The following patch eliminates the uninitialized mem pointer, using
instead the corresponding entry from the slots array to fix :
libkvm.c:580: warning: 'mem' is used uninitialized in this function
Also changes the formatting type for phys_addr to long to prevent :
libkvm.c:581: warning: fo
28 matches
Mail list logo