On 10/12/07, James Dykman <[EMAIL PROTECTED]> wrote:
> Dor,
>
> I ran some netperf tests with your PV
> virtio drivers, along with some Xen PV cases
> and a few others for comparison. I thought you
> (and the list) might be interested in the numbers.
>
> I am going to start looking for bottlenecks,
>N+1, for me is that synchronous device emulation (like pio and mmio)
>happens in in the vcpu thread and asynchronous device emulation
>(handling signals in qemu, performing dma, and injecting interrupts)
>happens in the device thread. This minimizes context switching and
>heavyweight exits.
>
If
Avi Kivity wrote:
> Zhang, Xiantao wrote:
>>> From 12457e0fb85ef32f1a1f808be294bebe8d22667c Mon Sep 17 00:00:00
>>> 2001
>> From: Zhang xiantao <[EMAIL PROTECTED]>
>> Date: Fri, 12 Oct 2007 13:29:30 +0800
>> Subject: [PATCH] Split kvm_vcpu to support new archs. Define a new
>> sub field kvm_arch_v
>
>That 0.1% kills me though. do you mean, that every 1 second, 1
>will be 1ms
>off? And for every second thereafter, leaving me with 1 second
>drift after
>only 1000 seconds?
>
Oh, that is not my intension :-(
I just put a rought estimation here. In old Xen
time, I know there are ~10-30 secon
>>> 1) the PIT is periodic. a PV timer can offer a one shot
>timer which
>>> enables dynticks.
>>>
>>
>> Obviously people have figured out how to do dynticks on real x86
>> hardware, so I don't accept this reason. :)
>>
>
>Using more advanced timers like the HPET.
>
I'd think there is
您好!
本公司向外代开全国各省各市,增值税发票(国税.地税)发票!商品销售.商业.企业.工业.服务.广告.运输.咨询.建筑,海关票等!公司本着互惠互利,
可为贵公司节约一部份资金,信誉第一, 诚信为本的原则, 所开出的发票皆可让贵公司验证后再付款!欢迎来电咨询!
电话:13560231980陈家俊
QQ; 784503636 公司地址;唐山市丰南区光明大街青年路175号。
-
This
Hi,
I intended to use qemu-system-x86_64 with kvm for full virtualization.
My host is
# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 127
model name : AMD Athlon(tm) 64 Processor 3500+
stepping: 1
cpu MHz : 1000.00
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>> Avi Kivity wrote:
Anthony Liguori wrote:
> I think it's just a matter of calling do_mmap() with the
> appropriate parameters. It looks likes there's some drivers call
> do_mmap() directly.
>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Anthony Liguori wrote:
>>>
I think it's just a matter of calling do_mmap() with the
appropriate parameters. It looks likes there's some drivers call
do_mmap() directly.
>>>
>>> This will halve t
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>
>>> I think it's just a matter of calling do_mmap() with the appropriate
>>> parameters. It looks likes there's some drivers call do_mmap()
>>> directly.
>>>
>>>
>>
>> This will halve the maximum size of virtual mac
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> I think it's just a matter of calling do_mmap() with the appropriate
>> parameters. It looks likes there's some drivers call do_mmap() directly.
>>
>>
>>
>
> This will halve the maximum size of virtual machines on i386 since
> userspace w
Blue Swirl wrote:
> On 10/14/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Some kvm users complained that the blue and red channels are flipped on
>> their displays. Reverting sdl.c rev 1.40 fixed that problem, so
>> apparently that commit made the problem larger than it was previously.
>>
>>
On 10/14/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Some kvm users complained that the blue and red channels are flipped on
> their displays. Reverting sdl.c rev 1.40 fixed that problem, so
> apparently that commit made the problem larger than it was previously.
>
> Attached a patch the removes t
Some kvm users complained that the blue and red channels are flipped on
their displays. Reverting sdl.c rev 1.40 fixed that problem, so
apparently that commit made the problem larger than it was previously.
Attached a patch the removes the commit and fixes the problem. Please
apply.
--
err
Hi,
what Mainboards with AMD690 chipsets are known to enable virtualization
functionality (be default or by BIOS setting)?
Elmar
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find prob
Avi Kivity wrote:
I wonder if there's a more elegant way dealing with older
userspaces. For instance, is there any reason why we can allocate a
userspace memory region on behalf of userspace. That way swap would
even work with older userspaces.
>>>
Emmanuel Nicolas Millan wrote:
>> Hi,
>>
>> is there any option to reenable virtualisation support (AMD-CPU) if it
>> is disabled by bios (and Bios does not show an option to enable
>> virtualisation support)?
>>
>
>
>> Elmar
>>
>
> Hi, i'm having the same problem, my bios doesn't have
On Sat, Oct 13, 2007 at 01:36:56AM +0200, Oliver Kowalke wrote:
> Hi,
> I've applied the patch now the kernel detects:
> cpu0: Intel Pentium Pro, II or III...
> cpu0: FPU,V86,...
> But I get in the next line:
> kernel: page fault trap, code=0
> Stopped at trap+0x16f: testb $0x3,0x38(%ecx)
Apparen
18 matches
Mail list logo