On 12/14/2010 06:04 PM, Anthony Liguori wrote:
On 12/14/2010 09:38 AM, Avi Kivity wrote:
Fortunately, we have a very good bytecode interpreter that's
accelerated in the kernel called KVM ;-)
We have exactly the same bytecode interpreter under a different name,
it's called userspace.
If you
Am 15.12.2010 09:05, Thomas Gleixner wrote:
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 14.12.2010 22:46, Thomas Gleixner wrote:
On Mon, 13 Dec 2010, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
chip_bus_lock(desc);
retval = __setup_irq(irq, desc, action);
Convert do_inject_nmi() to QObject, QError, we need to use it(via libvirt).
changed from v1
Add document.
Add error handling when the cpu index is invalid.
changed from v2
use QERR_INVALID_PARAMETER_VALUE as Markus suggest.
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
diff --git
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 15.12.2010 09:05, Thomas Gleixner wrote:
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 14.12.2010 22:46, Thomas Gleixner wrote:
On Mon, 13 Dec 2010, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
chip_bus_lock(desc);
On Mon, Dec 13, 2010 at 04:56:29PM -0700, Alex Williamson wrote:
On Tue, 2010-12-14 at 00:25 +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
Define a mask of PCI command register bits that need to be emulated,
i.e. read back from their shadow state. We will need this for
On Wed, 2010-12-15 at 00:57 +0100, Manfred Heubach wrote:
Vadim Rozenfeld vrozenfe at redhat.com writes:
On Mon, 2010-12-13 at 22:12 +0200, Dor Laor wrote:
On 12/13/2010 09:42 PM, Manfred Heubach wrote:
I was running the host with Ubuntu 10.04 but upgraded to 10.10 - mainly
Lai Jiangshan la...@cn.fujitsu.com writes:
Convert do_inject_nmi() to QObject, QError, we need to use it(via libvirt).
changed from v1
Add document.
Add error handling when the cpu index is invalid.
changed from v2
use QERR_INVALID_PARAMETER_VALUE as Markus suggest.
Signed-off-by: Lai
- Anthony Liguori anth...@codemonkey.ws wrote:
On 12/14/2010 06:09 AM, Ulrich Obergfell wrote:
[...]
Parts 1 thru 4 of this RFC contain experimental source code which
I recently used to investigate the performance benefit. In a Linux
guest, I was running a program that calls
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 14.12.2010 21:54, Thomas Gleixner wrote:
On Mon, 13 Dec 2010, Jan Kiszka wrote:
@@ -943,6 +950,9 @@ static struct irqaction *__free_irq(unsigned int irq,
void *dev_id)
/* Make sure it's not being used on another CPU: */
On Thu, Dec 09, 2010, Joerg Roedel wrote about Re: [PATCH 02/28] nVMX: Add VMX
and SVM to list of supported cpuid features:
This patch should be the last one in your series because VMX should be
fully supported before it is reported to userspace.
Joerg
Thanks, good idea - especially
Am 15.12.2010 14:04, Thomas Gleixner wrote:
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 14.12.2010 21:54, Thomas Gleixner wrote:
On Mon, 13 Dec 2010, Jan Kiszka wrote:
@@ -943,6 +950,9 @@ static struct irqaction *__free_irq(unsigned int irq,
void *dev_id)
/* Make sure it's not being used
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 15.12.2010 14:04, Thomas Gleixner wrote:
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 14.12.2010 21:54, Thomas Gleixner wrote:
On Mon, 13 Dec 2010, Jan Kiszka wrote:
@@ -943,6 +950,9 @@ static struct irqaction *__free_irq(unsigned int
irq, void
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 15.12.2010 14:04, Thomas Gleixner wrote:
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 14.12.2010 21:54, Thomas Gleixner wrote:
On Mon, 13 Dec 2010, Jan Kiszka wrote:
@@ -943,6 +950,9 @@ static struct irqaction *__free_irq(unsigned int
irq, void
Am 15.12.2010 16:41, Thomas Gleixner wrote:
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 15.12.2010 14:04, Thomas Gleixner wrote:
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 14.12.2010 21:54, Thomas Gleixner wrote:
On Mon, 13 Dec 2010, Jan Kiszka wrote:
@@ -943,6 +950,9 @@ static struct
We currently enable KVM by default, and when it's not available, we
print a message and fall back to TCG. Option -enable-kvm is ignored.
Option -no-kvm suppresses KVM.
Upstream works differently: KVM is off by default, -enable-kvm
switches it on. -enable-kvm terminates the process
On Wed, 15 Dec 2010, Jan Kiszka wrote:
Am 15.12.2010 16:41, Thomas Gleixner wrote:
Talking about headache. Your solution above does not prevent that
scenario.
CPU 0 CPU 1
synchronize_irq();
hard irq comes in sees shared and
This patchset adds an API test framework. Rather than driving kvm from qemu,
we now have a way of calling the kvm API directly and observing the results.
We can switch to guest mode and back at will and see any micro effects such
as the result of executing particular instructions.
A first test
Signed-off-by: Avi Kivity a...@redhat.com
---
Makefile |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index d25e6f2..9b0256d 100644
--- a/Makefile
+++ b/Makefile
@@ -30,11 +30,13 @@ CFLAGS += -O1
CFLAGS += $(autodepend-flags) -g
Signed-off-by: Avi Kivity a...@redhat.com
---
api/exception.cc | 20
api/exception.hh | 16
2 files changed, 36 insertions(+), 0 deletions(-)
create mode 100644 api/exception.cc
create mode 100644 api/exception.hh
diff --git a/api/exception.cc
This patch provides a way to establish an identity guest which has
a 1:1 gva-hva translation. This allows the host to switch to guest
mode, call a function in the same address space, and return.
Because long mode virtual addresses are 47 bits long, and some hosts
have smaller physical addresses,
Signed-off-by: Avi Kivity a...@redhat.com
---
Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index 85ebd37..b6e8759 100644
--- a/Makefile
+++ b/Makefile
@@ -6,7 +6,7 @@ DESTDIR := $(PREFIX)/share/qemu/tests
.PHONY: arch_clean clean
#make
Call a function setting a global variable.
Signed-off-by: Avi Kivity a...@redhat.com
---
api/api-sample.cc | 29 +
config-x86-common.mak |7 +++
2 files changed, 36 insertions(+), 0 deletions(-)
create mode 100644 api/api-sample.cc
diff --git
This checks the failure that was fixed by kernel commit edde99ce0529
(KVM: Write protect memory after slot swap). Two threads are used;
a guest thread continuously updates a shared variable, which is also
sampled by a host thread that also checks if dirty logging marked it
as dirty.
It detects
Signed-off-by: Avi Kivity a...@redhat.com
---
config-x86-common.mak | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/config-x86-common.mak b/config-x86-common.mak
index 436f4bd..ce36cde 100644
--- a/config-x86-common.mak
+++ b/config-x86-common.mak
@@ -85,8 +85,10
Add a class to manage the memory map and a class to represent
a memory slot.
Signed-off-by: Avi Kivity a...@redhat.com
---
api/memmap.cc | 76 +
api/memmap.hh | 43
2 files changed, 119 insertions(+), 0
Signed-off-by: Avi Kivity a...@redhat.com
---
api/kvmxx.cc |8
api/kvmxx.hh |1 +
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/api/kvmxx.cc b/api/kvmxx.cc
index 42e8781..7ebebb5 100644
--- a/api/kvmxx.cc
+++ b/api/kvmxx.cc
@@ -163,6 +163,14 @@ void
The hole may be used for mmio or dirty logging.
Signed-off-by: Avi Kivity a...@redhat.com
---
api/api-sample.cc |3 ++-
api/identity.cc | 23 +--
api/identity.hh | 17 -
config-x86-common.mak |1 +
4 files changed, 40 insertions(+),
Signed-off-by: Avi Kivity a...@redhat.com
---
api/kvmxx.cc |5 +++--
api/kvmxx.hh |3 ++-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/api/kvmxx.cc b/api/kvmxx.cc
index ad27907..42e8781 100644
--- a/api/kvmxx.cc
+++ b/api/kvmxx.cc
@@ -150,12 +150,13 @@ vm::vm(system
Introduce exception-safe objects for calling system, vm, and vcpu ioctls.
Signed-off-by: Avi Kivity a...@redhat.com
---
api/kvmxx.cc | 185 ++
api/kvmxx.hh | 83 ++
2 files changed, 268 insertions(+), 0
Signed-off-by: Avi Kivity a...@redhat.com
---
api/exception.cc | 13 +
api/exception.hh |3 +++
2 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/api/exception.cc b/api/exception.cc
index 500569a..910bdff 100644
--- a/api/exception.cc
+++ b/api/exception.cc
@@
This patchset consists of three patches:
[1/3] KVM: Take missing slots_lock for kvm_io_bus_unregister_dev()
[2/3] KVM: Centralize slots_lock aquisition during KVM_CREATE_IRQCHIP
[3/3] KVM: Centralize irq_lock aquisition during KVM_CREATE_IRQCHIP
Though patch 1 is a fix, this is only for an
From: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
In KVM_CREATE_IRQCHIP, kvm_io_bus_unregister_dev() is called without taking
slots_lock in the error handling path.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/ia64/kvm/kvm-ia64.c |2 ++
arch/x86/kvm/x86.c
From: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
Move slots_lock aquisition from kvm_ioapic_init() and kvm_create_pic()
to their caller.
As a result, x86's KVM_CREATE_IRQCHIP is now covered by a unified slots_lock
section, including kvm_setup_default_irq_routing().
Signed-off-by: Takuya
From: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
Move irq_lock aquisition from kvm_setup_default_irq_routing(), inside of
kvm_set_irq_routing(), to its caller.
This makes the lock management clearer, with a bit longer irq_lock section.
Signed-off-by: Takuya Yoshikawa
On Wed, 15 Dec 2010 17:49:27 +0800
Lai Jiangshan la...@cn.fujitsu.com wrote:
Convert do_inject_nmi() to QObject, QError, we need to use it(via libvirt).
changed from v1
Add document.
Add error handling when the cpu index is invalid.
changed from v2
use QERR_INVALID_PARAMETER_VALUE as
On Wed, 15 Dec 2010 11:49:23 +0100
Markus Armbruster arm...@redhat.com wrote:
Lai Jiangshan la...@cn.fujitsu.com writes:
Convert do_inject_nmi() to QObject, QError, we need to use it(via libvirt).
changed from v1
Add document.
Add error handling when the cpu index is invalid.
On 12/15/2010 07:09 PM, Luiz Capitulino wrote:
On Wed, 15 Dec 2010 17:49:27 +0800
Lai Jiangshanla...@cn.fujitsu.com wrote:
Convert do_inject_nmi() to QObject, QError, we need to use it(via libvirt).
changed from v1
Add document.
Add error handling when the cpu index is invalid.
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Why do we care? How are you defining actual VM RAM?
Surely the whole point of qemu_ram_alloc is to allocate a chunk of memory that
can be
On Wed, 15 Dec 2010 19:18:32 +0200
Avi Kivity a...@redhat.com wrote:
On 12/15/2010 07:09 PM, Luiz Capitulino wrote:
On Wed, 15 Dec 2010 17:49:27 +0800
Lai Jiangshanla...@cn.fujitsu.com wrote:
Convert do_inject_nmi() to QObject, QError, we need to use it(via
libvirt).
On 12/15/2010 09:50 AM, Markus Armbruster wrote:
We currently enable KVM by default, and when it's not available, we
print a message and fall back to TCG. Option -enable-kvm is ignored.
Option -no-kvm suppresses KVM.
Upstream works differently: KVM is off by default, -enable-kvm
switches it
Luiz Capitulino lcapitul...@redhat.com writes:
On Wed, 15 Dec 2010 19:18:32 +0200
Avi Kivity a...@redhat.com wrote:
On 12/15/2010 07:09 PM, Luiz Capitulino wrote:
On Wed, 15 Dec 2010 17:49:27 +0800
Lai Jiangshanla...@cn.fujitsu.com wrote:
Convert do_inject_nmi() to QObject,
On Wed, 15 Dec 2010 18:39:07 +0100
Markus Armbruster arm...@redhat.com wrote:
Luiz Capitulino lcapitul...@redhat.com writes:
On Wed, 15 Dec 2010 11:49:23 +0100
Markus Armbruster arm...@redhat.com wrote:
Lai Jiangshan la...@cn.fujitsu.com writes:
Convert do_inject_nmi() to
Anthony Liguori anth...@codemonkey.ws writes:
On 12/15/2010 09:50 AM, Markus Armbruster wrote:
We currently enable KVM by default, and when it's not available, we
print a message and fall back to TCG. Option -enable-kvm is ignored.
Option -no-kvm suppresses KVM.
Upstream works differently:
On Wed, 15 Dec 2010 18:45:09 +0100
Markus Armbruster arm...@redhat.com wrote:
Luiz Capitulino lcapitul...@redhat.com writes:
On Wed, 15 Dec 2010 19:18:32 +0200
Avi Kivity a...@redhat.com wrote:
On 12/15/2010 07:09 PM, Luiz Capitulino wrote:
On Wed, 15 Dec 2010 17:49:27 +0800
Lai
On Wed, 2010-12-15 at 17:23 +, Paul Brook wrote:
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Why do we care? How are you defining actual VM RAM?
Surely the whole point of
On 12/15/2010 11:23 AM, Paul Brook wrote:
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Why do we care? How are you defining actual VM RAM?
Surely the whole point of qemu_ram_alloc
We are pleased to announce availability of ConVirt 2.0.1 open
source. We would like to thank ConVirt user community for their
continuing participation and support. This release incorporates
feedback gathered from the community over last few months.
To learn more about the release, please visit
On Wed, Dec 15, 2010 at 8:28 PM, jd jdsw2...@yahoo.com wrote:
We are pleased to announce availability of ConVirt 2.0.1 open
source. We would like to thank ConVirt user community for their
continuing participation and support. This release incorporates
feedback gathered from the community over
2010/12/3 Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp:
2010/12/2 Michael S. Tsirkin m...@redhat.com:
On Wed, Dec 01, 2010 at 05:03:43PM +0900, Yoshiaki Tamura wrote:
2010/11/28 Michael S. Tsirkin m...@redhat.com:
On Sun, Nov 28, 2010 at 08:27:58PM +0900, Yoshiaki Tamura wrote:
2010/11/28
2010/11/28 Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp:
2010/11/28 Michael S. Tsirkin m...@redhat.com:
On Thu, Nov 25, 2010 at 03:06:50PM +0900, Yoshiaki Tamura wrote:
Record ioport event to replay it upon failover.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Interesting.
On 12/14/2010 07:53 PM, Hollis Blanchard wrote:
On 12/14/2010 12:48 AM, Avi Kivity wrote:
On 12/13/2010 07:17 PM, Hollis Blanchard wrote:
Rewriting is dangerous if the guest is unaware of it. As soon as
it is made aware of it, it might as well actually do it in the best
way that suits it.
On 12/15/2010 01:16 PM, Sethi Varun-B16395 wrote:
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org [mailto:kvm-ppc-
ow...@vger.kernel.org] On Behalf Of Avi Kivity
Sent: Tuesday, December 14, 2010 9:18 PM
To: Yoder Stuart-B08248
Cc: Hollis Blanchard; Alexander Graf;
-Original Message-
From: Avi Kivity [mailto:a...@redhat.com]
Sent: Wednesday, December 15, 2010 4:49 PM
To: Sethi Varun-B16395
Cc: Yoder Stuart-B08248; Hollis Blanchard; Alexander Graf; kvm-
p...@vger.kernel.org
Subject: Re: re-writing on powerpc
On 12/15/2010 01:16 PM, Sethi
On 12/15/2010 01:32 PM, Sethi Varun-B16395 wrote:
But KVM would be aware of guest page mappings, so access permissions
for any particular mapping can be controlled by KVM.
kvm isn't aware of all guest mappings (only those that were instantiated
in shadow tlb/pagetables).
I am not
54 matches
Mail list logo
