Hello, kvm-devel,
As I understand, virtio is not currently integrated into KVM.
However, there is a git tree of kvm with virtio in:
git://kvm.qumranet.com/home/dor/src/virtio/kvm
and
git://kvm.qumranet.com/home/dor/src/virtio/kvm-userspace
Is there any intention to integrate it into KVM
Rare nude photos of Kate Moss http://www.maoker.com/n453c67.aspx
Stone: I have no problem doing nude scene
http://www.maoker.com/n825c57.aspx
College girls go nude before camera for eternal beauty
http://www.maoker.com/n436c67.aspx
Lil bro's naked truth
Ian Brown wrote:
Hello, kvm-devel,
As I understand, virtio is not currently integrated into KVM.
However, there is a git tree of kvm with virtio in:
git://kvm.qumranet.com/home/dor/src/virtio/kvm
and
git://kvm.qumranet.com/home/dor/src/virtio/kvm-userspace
Is there any intention to
Akio Takebe wrote:
Hi,
I updated the patch of the following thread.
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/8899
Changelog:
- don't change Makefile
- put back some options (BuildRequires and so on).
Thanks, it's much improved.
However, kvm.spec has already changed, so
Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1193849564 18000
# Node ID 7445bcdab796596fb97312b97393e4f2936e5450
# Parent a809d39bd74d33d221dd98cc6afa02d9a35889a4
Move function kvm_create_default_phys_mem to kvmctl-x86 and rename
This patch moves
Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1193849564 18000
# Node ID 179d9b30ab973e6676dcd0b6fa08e9635969d44c
# Parent 7445bcdab796596fb97312b97393e4f2936e5450
Modify out arch specific code from kvm_create function
This function removes all x86
Jerone Young wrote:
Kaniciwa!
I am here to once again bring great honorable patches to refactor
libkvm x86 code. Patches that I sent in the past for this really took
the wrong approach, and also many variables that I was splitting out actually
could be shared amongst many
Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1193849563 18000
# Node ID 9c74b8e493e67f544c017b6bef8dd047c128c8d3
# Parent 19a7c6d2ddfd1383aeb8a9bc09d9fe0673e7f9cc
Make static slot kvm_memory region funcions public
This patch changes static
Dor,
Thanks for the info!
Ian
On 11/1/07, Dor Laor [EMAIL PROTECTED] wrote:
Ian Brown wrote:
Hello, kvm-devel,
As I understand, virtio is not currently integrated into KVM.
However, there is a git tree of kvm with virtio in:
git://kvm.qumranet.com/home/dor/src/virtio/kvm
and
Hollis Blanchard wrote:
These patches are not simple code movement, and I haven't yet tested them so
I'm just putting them out for comment.
Basically we're expanding the VCPU creation path to add an arch layer
between
main.c and svm/vmx.c. Since there is one call in each direction (main.c -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Fitzhardinge escreveu:
Glauber de Oliveira Costa wrote:
This patch introduces, and patch callers when needed, native
versions for read/write_crX functions, clts and wbinvd.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Fitzhardinge escreveu:
Glauber de Oliveira Costa wrote:
under paravirt, read cr2 cannot be issued directly anymore.
So wrap it in a macro, defined to the operation itself in case
paravirt is off, but to something else if we have paravirt
Glauber de Oliveira Costa wrote:
I in fact have seen bugs with mixed reads and writes to the same cr,
(cr4), but adding the volatile
flag to the read function seemed to fix it.
Well, volatile will make a read be repeated rather than caching the
previous value, but it has no effect on ordering.
This patch synchronises the APIC reset with the inkernel implementation
which fixes the reboot issues which can be seen with Linux and Windows.
Signed-off-by: Joerg Roedel [EMAIL PROTECTED]
Signed-off-by: Markus Rechberger [EMAIL PROTECTED]
diff --git a/qemu/hw/apic.c b/qemu/hw/apic.c
index
On 1/11/07 15:30, Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Glauber de Oliveira Costa wrote:
I in fact have seen bugs with mixed reads and writes to the same cr,
(cr4), but adding the volatile
flag to the read function seemed to fix it.
Well, volatile will make a read be repeated rather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Keir Fraser escreveu:
On 1/11/07 15:30, Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Glauber de Oliveira Costa wrote:
I in fact have seen bugs with mixed reads and writes to the same cr,
(cr4), but adding the volatile
flag to the read function
Keir Fraser wrote:
volatile prevents the asm from being 'moved significantly', according to the
gcc manual. I take that to mean that reordering is not allowed.
That phrase doesn't appear in the gcc manual; in fact, it specifically
says that reordering can happen:
The `volatile' keyword
3 files changed, 450 insertions(+), 442 deletions(-)
drivers/kvm/kvm.h | 10 +
drivers/kvm/kvm_main.c | 448
drivers/kvm/x86.c | 434 ++
Signed-off-by: Hollis Blanchard [EMAIL PROTECTED]
---
Cam Macdonell wrote:
Hi,
I'm running an AMD
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
with 4GB of RAM and Scientific Linux 5.0. I've compiled kvm-48 on it and
the compile works and loading the
Markus Rechberger wrote:
This patch synchronises the APIC reset with the inkernel
implementation which fixes the reboot issues which can be seen with
Linux and Windows.
Signed-off-by: Joerg Roedel [EMAIL PROTECTED]
Signed-off-by: Markus Rechberger [EMAIL PROTECTED]
Today's big change is FlexPriority, which drastically improves Windows
SMP and/or ACPI performance on newer Intel processors.
Changes from kvm-49:
- fix smp_call_function_mask() emulation on preemptible kernels
- move libkvm into own directory (Hollis Blanchard)
- fix save/restore/migrate for
Avi Kivity wrote:
Today's big change is FlexPriority, which drastically improves Windows
SMP and/or ACPI performance on newer Intel processors.
Whoops, this is kvm-50, not as the subject line suggests.
--
Any sufficiently difficult bug is indistinguishable from a feature.
Bugs item #1824398, was opened at 2007-11-02 11:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1824398group_id=180599
Please note that this message will contain a full copy of
On Thu, 2007-11-01 at 10:41 -0700, Jeremy Fitzhardinge wrote:
Keir Fraser wrote:
volatile prevents the asm from being 'moved significantly', according to the
gcc manual. I take that to mean that reordering is not allowed.
I understood it as reordering was permitted, but no re-ordering
How can I tell that my cpu has flexpriority?
(Resending this as didn't cc list last time.)
On Nov 1, 2007 7:12 PM, Avi Kivity [EMAIL PROTECTED] wrote:
Today's big change is FlexPriority, which drastically improves Windows
SMP and/or ACPI performance on newer Intel processors.
Changes from
On Friday 02 November 2007 09:10:31 Haydn Solomon wrote:
How can I tell that my cpu has flexpriority?
(Resending this as didn't cc list last time.)
Oops, forgot the patch...
On Nov 1, 2007 7:12 PM, Avi Kivity [EMAIL PROTECTED] wrote:
Today's big change is FlexPriority, which drastically
On Friday 02 November 2007 09:10:31 Haydn Solomon wrote:
How can I tell that my cpu has flexpriority?
(Resending this as didn't cc list last time.)
Try attached printk patch.
And generally, E6850, E6750, E6550, Core2 Duo processors
starting from
G0 stepping should support this.
On Nov 1,
From: Haydn Solomon [mailto:[EMAIL PROTECTED]
Sent: 2007年11月2日 10:15
To: Yang, Sheng
Cc: kvm-devel@lists.sourceforge.net; Avi Kivity
Subject: Re: [kvm-devel] [ANNOUNCE] kvm-49 release
On Nov 1, 2007 9:54 PM, Haydn Solomon [EMAIL PROTECTED] wrote:
On Nov
On Nov 1, 2007 9:54 PM, Haydn Solomon [EMAIL PROTECTED] wrote:
On Nov 1, 2007 9:36 PM, Sheng Yang [EMAIL PROTECTED] wrote:
On Friday 02 November 2007 09:10:31 Haydn Solomon wrote:
How can I tell that my cpu has flexpriority?
(Resending this as didn't cc list last time.)
Oops,
On Nov 1, 2007 9:36 PM, Sheng Yang [EMAIL PROTECTED] wrote:
On Friday 02 November 2007 09:10:31 Haydn Solomon wrote:
How can I tell that my cpu has flexpriority?
(Resending this as didn't cc list last time.)
Oops, forgot the patch...
Thanks Sheng.
Luckily for me I've got the
Save/restore still fails in today's testing.
kvm_get_mem_map failed: Unknown error 18446744073709551594
Thanks
Yunfeng
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Avi Kivity
Sent: 2007年11月2日 7:12
To: kvm-devel
Subject: [kvm-devel] [ANNOUNCE] kvm-49
Yes, when reseting, we need to reset both APIC/PIC/IOAPIC and pv
driver in future, and also VCPU.
But isn't apic_reset a pure user level APIC thing?
BTW
I posted a patch to support kernel device reset which is still pending.
And I think Avi has some idea to support too and is working on:-)
On Friday 02 November 2007 10:14:35 Haydn Solomon wrote:
On Nov 1, 2007 9:54 PM, Haydn Solomon [EMAIL PROTECTED] wrote:
On Nov 1, 2007 9:36 PM, Sheng Yang [EMAIL PROTECTED] wrote:
On Friday 02 November 2007 09:10:31 Haydn Solomon wrote:
How can I tell that my cpu has flexpriority?
On Friday 02 November 2007 12:56:26 Haydn Solomon wrote:
On Nov 1, 2007 11:15 PM, Sheng Yang [EMAIL PROTECTED] wrote:
On Friday 02 November 2007 10:14:35 Haydn Solomon wrote:
On Nov 1, 2007 9:54 PM, Haydn Solomon [EMAIL PROTECTED] wrote:
On Nov 1, 2007 9:36 PM, Sheng Yang [EMAIL
On Nov 1, 2007 11:15 PM, Sheng Yang [EMAIL PROTECTED] wrote:
On Friday 02 November 2007 10:14:35 Haydn Solomon wrote:
On Nov 1, 2007 9:54 PM, Haydn Solomon [EMAIL PROTECTED] wrote:
On Nov 1, 2007 9:36 PM, Sheng Yang [EMAIL PROTECTED] wrote:
On Friday 02 November 2007 09:10:31 Haydn
From 00a52112d813af983dd4d34cb7dc701f6fe88829 Mon Sep 17 00:00:00 2001
From: Sheng Yang [EMAIL PROTECTED]
Date: Fri, 2 Nov 2007 11:56:17 +0800
Subject: [PATCH] KVM: VMX: Fix repeatly calling alloc_apic_access_page()
For SMP guest, alloc_apic_access_page() would be called more than once. So
only
Hi Young,
Quick hand! For patch 07/27, 09/27, i have some concerns about them.
In these two patches you moved the functions kvm_create_kernel_phys_mem,
kvm_create_default_phys_mem to x86 arch. But I think it should work well for
most archs. As somebody said, S390 may have a very
Hi Avi, I'm looking at kvm_init() right now. Since everything is driven
by the arch-specific modules (svm.c and vmx.c), I think it would
simplify things to fold all of kvm_init() into what is today called
kvm_init_x86().
If that's done, kvm_main.c won't have any modinit function, but I
think that
38 matches
Mail list logo
