On Sun, 2007-10-28 at 19:42 -0500, Jerone Young wrote:
# HG changeset patch
# User Jerone Young [EMAIL PROTECTED]
# Date 1193618330 18000
# Node ID 8bf5e4e6a4c9d2dab89062a0ab24a2ae5d144a02
# Parent 3bf072e498768885ab96b7ccb668b61c96db0e83
Move kvm_context structure to kvmctl.h header
Avi Kivity wrote:
Zhang, Xiantao wrote:
Avi Kivity wrote:
Wht about aliases? Aliases allow you go have two different physical
addresses for the same page. This is useful for mapping the
framebuffer on x86 (both at the pci region and at 0xa, the
traditional ISA location).
Are they
Izik Eidus wrote:
my idea was to let kvm register userspace memory that will hold the
guest memory,
and then much like qemu do with its cpu_register_physical_memory
function, run ioctls
that will tell the kernel how to map this memory,
what i wanted to achieved is making the memory
Avi Kivity wrote:
Dong, Eddie wrote:
Jan Kiszka wrote:
So if you want the higher performance of PCIe you need
performance-killing wbindv (not to speak of latency)? That sounds a
bit contradictory to me. So this is also true for native PCIe usage?
Mmm, I won't say so. When you want to
Anthony Liguori wrote:
Dong, Eddie wrote:
BTW, is it wise to enable this by default for all guests?
Ignoring the
fact that we're modifying guest's memory without its knowledge, if a
guest unmaps the VA mappings for the BIOS then all sorts of
problems could occur.
Good movement!
But,
On Mon, 2007-10-29 at 11:31 +0100, Andi Kleen wrote:
FYI,
I got this BUG while playing around with some guests with kvm-48
on a Core2 system. Base kernel was 2.6.23+ff patches
(that is why you see the LBR output; BTW that makes KVM complain
too when it happens in a guest) . Haven't looked
FYI,
I got this BUG while playing around with some guests with kvm-48
on a Core2 system. Base kernel was 2.6.23+ff patches
(that is why you see the LBR output; BTW that makes KVM complain
too when it happens in a guest) . Haven't looked at it closely.
-Andi
[ cut here ]
On Mon, 2007-10-29 at 12:55 +0800, Yang, Sheng wrote:
From 34ee5ae67ff5d3f4b8a0b9313dd80980f57705eb Mon Sep 17 00:00:00 2001
From: Sheng Yang [EMAIL PROTECTED]
Date: Mon, 29 Oct 2007 09:40:42 +0800
Subject: [PATCH] KVM: VMX: Enable memory mapped TPR shadow(FlexPriority)
This patch based on
On Mon, Oct 29, 2007 at 12:42:16PM +0200, Izik Eidus wrote:
On Mon, 2007-10-29 at 11:31 +0100, Andi Kleen wrote:
FYI,
I got this BUG while playing around with some guests with kvm-48
on a Core2 system. Base kernel was 2.6.23+ff patches
(that is why you see the LBR output; BTW that
On 10/29/07, Izik Eidus [EMAIL PROTECTED] wrote:
Haydn Solomon wrote:
Thanks Avi. Question: Does this release include the TPR optimization
for windows features?
nope, the code need some cleanup
Thanks.
-
This SF.net
Dong, Eddie wrote:
Anthony Liguori wrote:
Dong, Eddie wrote:
BTW, is it wise to enable this by default for all guests?
Ignoring the
fact that we're modifying guest's memory without its knowledge, if a
guest unmaps the VA mappings for the BIOS then all sorts of
problems could
Uhm, not sure who to send this too...
I thought I'd try out the realtime patch set and it didn't work at all
with kvm. The console didn't dump anything and the system completely
locked up.
Anyone have any suggestions as to how to get more output on this issue?
It got to the point of bringing up
Hollis Blanchard wrote:
On Sun, 2007-10-28 at 22:50 -0500, Anthony Liguori wrote:
You could certainly get even more clever and have the arch backend
register the appropriate tables based on the as type but that's merely
an implementation detail. The key observation, that I believe is
I didn't some tests against the release.
Basically, it works well, and no any new regressions has been introduced.
The booting speed of windows is also much faster.
But I still failed to boot 64bit smp XP and 2k3.
And after run a series of tests, I found a defunct qemu process.
This patch series continues the split of kvm_main.c for portability. The
first patch that splits kvm_vm_ioctl is unchanged since last submit, but
has not yet been picked up upstream. There are no more ongoing
discussions regarding it's content, therefore I'd like to ask for
integration of that
This patch splits kvm_vm_ioctl into archtecture independent parts, and
x86 specific parts which go to kvm_arch_vcpu_ioctl in x86.c.
The patch is unchanged since last submission.
Common ioctls for all architectures are:
KVM_CREATE_VCPU, KVM_GET_DIRTY_LOG, KVM_SET_USER_MEMORY_REGION
x86 specific
This patch moves the definition of segment_descriptor_64 for AMD64 and
EM64T from kvm_main.c to segment_descriptor.h. It also adds a proper
#ifndef...#define...#endif around that header file.
The implementation of segment_base is moved from kvm_main.c to x86.c.
Signed-off-by: Carsten Otte [EMAIL
This patch moves the implementation of get_apic_base and set_apic_base
from kvm_main.c to x86.c
Signed-off-by: Carsten Otte [EMAIL PROTECTED]
Reviewed-by: Christian Borntraeger [EMAIL PROTECTED]
---
kvm_main.c | 19 ---
x86.c | 19 +++
2 files changed, 19
This patch moves the definitions of CR0_RESERVED_BITS,
CR4_RESERVED_BITS, and CR8_RESERVED_BITS along with the following
functions from kvm_main.c to x86.c:
set_cr0(), set_cr3(), set_cr4(), set_cr8(), get_cr8(), lmsw(),
load_pdptrs()
The static function wrapper inject_gp is duplicated in
On Mon, 2007-10-29 at 16:08 +0100, Carsten Otte wrote:
This patch splits kvm_vm_ioctl into archtecture independent parts, and
x86 specific parts which go to kvm_arch_vcpu_ioctl in x86.c.
The patch is unchanged since last submission.
Common ioctls for all architectures are:
KVM_CREATE_VCPU,
Izik Eidus wrote:
i think KVM_SET_MEMORY_ALIAS, is useful not just to x86,
avi talked with the ia64 guys and they told him that they have use for
this function.
is it that bad for you?
KVM_SET_USER_MEMORY_REGION is a superset of KVM_SET_MEMORY_ALIAS, at
least that's how I read Avi's reply
Hollis Blanchard wrote:
AFAICS, you can just issue two KVM_SET_USER_MEMORY_REGION ioctls in a
row, changing 'guest_phys_addr' and leaving 'userspace_addr' the same.
That will create an alias.
That was also my understanding of Avi's comment.
qemu doesn't quit (no poweroff?) on halt for linux 2.6.23 x86 guests (confirmed
by danieldg on irc), but it works for 64bit guests and it works for linux 2.6.22
x86 guests. I tried kvm-45 and kvm-49. -no-kvm does not help.
Cheers,
--Denys
On 10/29/07, Denys Duchier [EMAIL PROTECTED] wrote:
qemu doesn't quit (no poweroff?) on halt for linux 2.6.23 x86 guests
(confirmed
by danieldg on irc), but it works for 64bit guests and it works for linux
2.6.22
x86 guests. I tried kvm-45 and kvm-49. -no-kvm does not help.
Try acpi=force
Anthony Liguori wrote:
Luca Tettamanti wrote:
On 10/29/07, Denys Duchier [EMAIL PROTECTED] wrote:
qemu doesn't quit (no poweroff?) on halt for linux 2.6.23 x86 guests
(confirmed
by danieldg on irc), but it works for 64bit guests and it works for
linux 2.6.22
x86 guests. I tried kvm-45
Luca Tettamanti [EMAIL PROTECTED] writes:
Try acpi=force on the kernel command line (guest). QEmu doesn't expose
a DMI block and Linux guests usually don't enable ACPI since they're
unable to check BIOS year (all BIOSes shipped before 2001 are
blacklisted because they tend to be very broken).
Hi,
I've finally gotten around to incorporating the feedback from KVM Forum
into kvm-test. I think it's ready for more people to use now. kvm-test
allows the user to record a KVM session and replay it. This is useful
for doing things like automated installation testing.
Ryan Harper is also
Luca Tettamanti wrote:
On 10/29/07, Denys Duchier [EMAIL PROTECTED] wrote:
qemu doesn't quit (no poweroff?) on halt for linux 2.6.23 x86 guests
(confirmed
by danieldg on irc), but it works for 64bit guests and it works for linux
2.6.22
x86 guests. I tried kvm-45 and kvm-49. -no-kvm
On 10/29/07, Anthony Liguori [EMAIL PROTECTED] wrote:
Hi,
I've finally gotten around to incorporating the feedback from KVM Forum
into kvm-test. I think it's ready for more people to use now. kvm-test
allows the user to record a KVM session and replay it. This is useful
for doing things
Anthony Liguori [EMAIL PROTECTED] writes:
This would require CONFIG_ACPI_BLACKLIST_YEAR=2001. In my kernel
config, it's set to 0 and my guests still don't shut off so I think
there's more to it than just this.
Nevermind, I was looking at an x86_64 config.
that's odd, because it works for
Anthony Liguori wrote:
KVM's nopage handler calls gfn_to_page() which acquires the mmap_sem when
calling out to get_user_pages(). nopage handlers are already invoked with the
mmap_sem held though. Introduce a __gfn_to_page() for use by the nopage
handler which requires the lock to already be
Anthony Liguori wrote:
Hi,
I've finally gotten around to incorporating the feedback from KVM Forum
into kvm-test. I think it's ready for more people to use now. kvm-test
allows the user to record a KVM session and replay it. This is useful
for doing things like automated installation
KVM's nopage handler calls gfn_to_page() which acquires the mmap_sem when
calling out to get_user_pages(). nopage handlers are already invoked with the
mmap_sem held though. Introduce a __gfn_to_page() for use by the nopage
handler which requires the lock to already be held.
This was noticed by
On Mon, 29 Oct 2007, Glauber de Oliveira Costa wrote:
CC'ed John and removed [EMAIL PROTECTED] :)
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change it's frequency, i.e. when it works), so it should have its rating
On Mon, 2007-10-29 at 20:10 -0300, Glauber de Oliveira Costa wrote:
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change it's frequency, i.e. when it works), so it should have its rating
raised to a value greater than,
What host kernel ? 32-bit or 64-bit ?
Also, the only way to get rid of qemu process/window is to reboot the
machine, same with kvm-48.
Use kill -9 PID to kill KVM.
--
-Alexey Eremenko Technologov
-
This SF.net email is
Ingo Molnar wrote:
* Zachary Amsden [EMAIL PROTECTED] wrote:
On Mon, 2007-10-29 at 20:10 -0300, Glauber de Oliveira Costa wrote:
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change it's frequency, i.e. when
Zachary Amsden wrote:
On Mon, 2007-10-29 at 20:10 -0300, Glauber de Oliveira Costa wrote:
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change it's frequency, i.e. when it works), so it should have its rating
raised
On Mon, 2007-10-29 at 16:08 +0100, Carsten Otte wrote:
This patch series continues the split of kvm_main.c for portability. The
first patch that splits kvm_vm_ioctl is unchanged since last submit, but
has not yet been picked up upstream. There are no more ongoing
discussions regarding it's
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change it's frequency, i.e. when it works), so it should have its rating
raised to a value greater than, or equal 400.
Since it's being a tendency among paravirt clocksources to
32 bit host
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk
Hello again,
I attempted to install Windows XP(sp2) as a guest and it crashes with a blank
window and QEMU/KVM[Stopped] in the title. The install starts fine
with -no-kvm. Below is the output from /proc/version, /proc/cpuinfo and
dmesg. I am using kvm-49. Also, the only way to get rid of qemu
On Tue, 2007-10-30 at 00:02 +0100, Ingo Molnar wrote:
* Zachary Amsden [EMAIL PROTECTED] wrote:
Not every guest support paravirt, but for correctness, all guests
require TSC, which must be exposed all the way up to userspace, no
matter what the efficiency or accuracy may be.
but if
* Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Ingo Molnar wrote:
that's totally broken then. You cannot create an SMP-safe monotonic
clocksource via interpolation - native does not do it either. Good thing
this problem got exposed, it needs to be fixed.
Sigh, I don't really
Ingo Molnar wrote:
that's totally broken then. You cannot create an SMP-safe monotonic
clocksource via interpolation - native does not do it either. Good thing
this problem got exposed, it needs to be fixed.
Sigh, I don't really want to have this fight again.
I don't really see what
* Zachary Amsden [EMAIL PROTECTED] wrote:
On Tue, 2007-10-30 at 00:02 +0100, Ingo Molnar wrote:
* Zachary Amsden [EMAIL PROTECTED] wrote:
Not every guest support paravirt, but for correctness, all guests
require TSC, which must be exposed all the way up to userspace, no
matter
On 10/29/2007 04:02 PM, Ingo Molnar wrote:
* Zachary Amsden [EMAIL PROTECTED] wrote:
On Mon, 2007-10-29 at 23:48 +0100, Ingo Molnar wrote:
* Zachary Amsden [EMAIL PROTECTED] wrote:
if it's inaccurate why are you exposing it to the guest then? Native
only uses the TSC if it's safe and
* Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
if it's inaccurate why are you exposing it to the guest then? Native
only uses the TSC if it's safe and accurate to do so.
It is used as part of the Xen clocksource as a short term
extrapolator, with correction parameters supplied by the
Ingo Molnar wrote:
i dont remember us having discussed this before, ever. If there's any
fight about monotonicity and SMP then it would be a pretty onesided
affair, with you being beaten up seriously ;-)
This is part of Xen's ABI, so it isn't easily changed. You're right
that getting
* Zachary Amsden [EMAIL PROTECTED] wrote:
On Mon, 2007-10-29 at 23:48 +0100, Ingo Molnar wrote:
* Zachary Amsden [EMAIL PROTECTED] wrote:
if it's inaccurate why are you exposing it to the guest then? Native
only uses the TSC if it's safe and accurate to do so.
Not every guest
Glauber de Oliveira Costa wrote:
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change it's frequency, i.e. when it works), so it should have its rating
raised to a value greater than, or equal 400.
Since it's being a
* Zachary Amsden [EMAIL PROTECTED] wrote:
On Mon, 2007-10-29 at 20:10 -0300, Glauber de Oliveira Costa wrote:
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change it's frequency, i.e. when it works), so it should
I will give it a try. It would be very useful!:)
Thanks
Yunfeng
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anthony Liguori
Sent: 2007年10月30日 2:58
To: kvm-devel
Subject: [kvm-devel] [ANN] kvm-test
Hi,
I've finally gotten around to incorporating the
Carsten Otte wrote:
This patch series continues the split of kvm_main.c for portability.
The first patch that splits kvm_vm_ioctl is unchanged since last
submit, but has not yet been picked up upstream. There are no more
ongoing discussions regarding it's content, therefore I'd like to ask
* Thomas Gleixner [EMAIL PROTECTED] wrote:
Since it's being a tendency among paravirt clocksources to use
values around 400, we should declare tsc as even better: So we use
500.
This patch also touches the comments on clocksource.h, which
suggests that 499 would be a limit on the
Sigh, I don't really want to have this fight again.
i dont remember us having discussed this before, ever. If there's any
fight about monotonicity and SMP then it would be a pretty onesided
affair, with you being beaten up seriously ;-)
Actually, it is possible, even for NUMA systems with
On Mon, 2007-10-29 at 23:17 +0100, Thomas Gleixner wrote:
On Mon, 29 Oct 2007, Glauber de Oliveira Costa wrote:
CC'ed John and removed [EMAIL PROTECTED] :)
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change
On Tuesday 30 October 2007 09:17:38 Thomas Gleixner wrote:
On Mon, 29 Oct 2007, Glauber de Oliveira Costa wrote:
CC'ed John and removed [EMAIL PROTECTED] :)
From: Glauber de Oliveira Costa [EMAIL PROTECTED]
tsc is very good time source (when it does not have drifts, does not
change
Anthony Liguori wrote:
KVM's nopage handler calls gfn_to_page() which acquires the mmap_sem when
calling out to get_user_pages(). nopage handlers are already invoked with the
mmap_sem held though. Introduce a __gfn_to_page() for use by the nopage
handler which requires the lock to already be
Carsten Otte wrote:
This patch series continues the split of kvm_main.c for portability. The
first patch that splits kvm_vm_ioctl is unchanged since last submit, but
has not yet been picked up upstream. There are no more ongoing
discussions regarding it's content, therefore I'd like to ask for
Zhao, Yunfeng wrote:
I didn't some tests against the release.
Basically, it works well, and no any new regressions has been introduced.
The booting speed of windows is also much faster.
But I still failed to boot 64bit smp XP and 2k3.
And after run a series of tests, I found a defunct qemu
Carsten Otte wrote:
Hollis Blanchard wrote:
AFAICS, you can just issue two KVM_SET_USER_MEMORY_REGION ioctls in a
row, changing 'guest_phys_addr' and leaving 'userspace_addr' the same.
That will create an alias.
That was also my understanding of Avi's comment.
That is indeed what I meant.
Yang, Sheng wrote:
From 34ee5ae67ff5d3f4b8a0b9313dd80980f57705eb Mon Sep 17 00:00:00 2001
From: Sheng Yang [EMAIL PROTECTED]
Date: Mon, 29 Oct 2007 09:40:42 +0800
Subject: [PATCH] KVM: VMX: Enable memory mapped TPR shadow(FlexPriority)
This patch based on CR8/TPR patch, and enable the TPR
Andi Kleen wrote:
it look like the slab cache is not initlized for some reason,
there was fix in kvm-49 that initied the slab cache in another place.
(check out commits arround b95061aec006bc4c44e4b244e4ec15c009ab880a)
can you please check if it happen in kvm-49 as well?
I can try it
Luca Tettamanti wrote:
On 10/29/07, Denys Duchier [EMAIL PROTECTED] wrote:
qemu doesn't quit (no poweroff?) on halt for linux 2.6.23 x86 guests
(confirmed
by danieldg on irc), but it works for 64bit guests and it works for linux
2.6.22
x86 guests. I tried kvm-45 and kvm-49. -no-kvm
Anthony Liguori wrote:
Hi,
I've finally gotten around to incorporating the feedback from KVM Forum
into kvm-test. I think it's ready for more people to use now. kvm-test
allows the user to record a KVM session and replay it. This is useful
for doing things like automated installation
David Brown wrote:
Uhm, not sure who to send this too...
I thought I'd try out the realtime patch set and it didn't work at all
with kvm. The console didn't dump anything and the system completely
locked up.
Anyone have any suggestions as to how to get more output on this issue?
Make
[EMAIL PROTECTED] wrote:
Hello again,
I attempted to install Windows XP(sp2) as a guest and it crashes with a blank
window and QEMU/KVM[Stopped] in the title. The install starts fine
with -no-kvm. Below is the output from /proc/version, /proc/cpuinfo and
dmesg. I am using kvm-49. Also, the
Avi Kivity wrote:
Anthony Liguori wrote:
Hi,
I've finally gotten around to incorporating the feedback from KVM Forum
into kvm-test. I think it's ready for more people to use now. kvm-test
allows the user to record a KVM session and replay it. This is useful
for doing things like
Avi Kivity wrote:
Zhao, Yunfeng wrote:
I didn't some tests against the release.
Basically, it works well, and no any new regressions has been introduced.
The booting speed of windows is also much faster.
But I still failed to boot 64bit smp XP and 2k3.
And after run a series of tests, I
Move libkvm into its own directory. No functional changes.
Signed-off-by: Hollis Blanchard [EMAIL PROTECTED]
---
I've build-tested this pretty thoroughly on x86(32).
Changes from v1: update libkvm.h #include guard macro.
diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -5,16
Dan Hecht wrote:
Not really. In the case hardware TSC is perfect, the paravirt time
counter can be implemented directly in terms of hardware TSC; there is
no loss in optimization. This is done transparently. And virtual TSC
can be implemented this way too.
The real improvement that a
On Tue, 2007-10-30 at 05:40 +0200, Avi Kivity wrote:
While mercurial is easier to use than git, using git would make it
easier for more kvm developers to contribute.
Anybody who manages to use git can figure out Mercurial in minutes.
--
Hollis Blanchard
IBM Linux Technology Center
Anthony Liguori wrote:
Dong, Eddie wrote:
Anthony Liguori wrote:
Dong, Eddie wrote:
BTW, is it wise to enable this by default for all guests?
Ignoring the
fact that we're modifying guest's memory without its knowledge, if a
guest unmaps the VA mappings for the BIOS then all sorts of
Anthony Liguori wrote:
Avi Kivity wrote:
Zhao, Yunfeng wrote:
I didn't some tests against the release.
Basically, it works well, and no any new regressions has been introduced.
The booting speed of windows is also much faster.
But I still failed to boot 64bit smp XP and 2k3.
Hollis Blanchard wrote:
Also, can't x86 rep instructions go beyond 64 bits? I guess that must
be handled in the arch-specific caller of io_write(), which would call
it multiple times.
'rep' has special support in the ABI (it's N accesses of M bits, not an
NxM bit access).
--
Any
Avi Kivity wrote:
Anthony Liguori wrote:
Dong, Eddie wrote:
Anthony Liguori wrote:
Dong, Eddie wrote:
BTW, is it wise to enable this by default for all guests?
Ignoring the
fact that we're modifying guest's memory without its knowledge, if a
guest unmaps the VA mappings for the BIOS
77 matches
Mail list logo
