On Thu, 2011-12-01 at 09:58 +0200, Michael S. Tsirkin wrote:
On Thu, Dec 01, 2011 at 01:12:25PM +1030, Rusty Russell wrote:
On Wed, 30 Nov 2011 18:11:51 +0200, Sasha Levin levinsasha...@gmail.com
wrote:
On Tue, 2011-11-29 at 16:58 +0200, Avi Kivity wrote:
On 11/29/2011 04:54 PM,
On Thu, Dec 01, 2011 at 12:58:59PM +1030, Rusty Russell wrote:
On Thu, 1 Dec 2011 01:13:07 +0200, Michael S. Tsirkin m...@redhat.com
wrote:
For x86, stores into memory are ordered. So I think that yes, smp_XXX
can be selected at compile time.
So let's forget the virtio strangeness for
On Wed, 30 Nov 2011, Asias He wrote:
In virtio net's notify_vq(), we simply signal the tx/rx handle thread
and return.
Why not use the threadpool?
No.
Sasha?
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo
On Thu, 2011-12-01 at 10:48 +0200, Pekka Enberg wrote:
On Wed, 30 Nov 2011, Asias He wrote:
In virtio net's notify_vq(), we simply signal the tx/rx handle thread
and return.
Why not use the threadpool?
No.
Sasha?
I was looking into the concept of adding 'dedicated' threads to the
On Thu, Dec 01, 2011 at 08:14:26AM +0200, Ohad Ben-Cohen wrote:
On Thu, Dec 1, 2011 at 1:13 AM, Michael S. Tsirkin m...@redhat.com wrote:
For x86, stores into memory are ordered. So I think that yes, smp_XXX
can be selected at compile time.
But then you can't use the same kernel image for
On 11/29/2011 09:10 PM, Markus Armbruster wrote:
Avi Kivity a...@redhat.com writes:
On 11/29/2011 05:51 PM, Juan Quintela wrote:
How to do high level stuff?
- python?
One of the disadvantages of the various scripting languages is the lack
of static type checking, which makes it
On Thu, Dec 01, 2011 at 10:09:37AM +0200, Sasha Levin wrote:
On Thu, 2011-12-01 at 09:58 +0200, Michael S. Tsirkin wrote:
On Thu, Dec 01, 2011 at 01:12:25PM +1030, Rusty Russell wrote:
On Wed, 30 Nov 2011 18:11:51 +0200, Sasha Levin levinsasha...@gmail.com
wrote:
On Tue, 2011-11-29
On Wed, 2011-11-30 at 18:32 +, Stefano Stabellini wrote:
On Wed, 30 Nov 2011, Arnd Bergmann wrote:
KVM and Xen at least both fall into the single-return-value category,
so we should be able to agree on a calling conventions. KVM does not
have an hcall API on ARM yet, and I see no
On 11/30/2011 11:43 AM, Xiao Guangrong wrote:
Subject: [PATCH] KVM: MMU: audit: inline audit function
inline audit function and little cleanup
Thanks, applied.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
On Wed, 2011-11-30 at 18:15 +, Arnd Bergmann wrote:
On Wednesday 30 November 2011, Ian Campbell wrote:
On Wed, 2011-11-30 at 14:32 +, Arnd Bergmann wrote:
On Wednesday 30 November 2011, Ian Campbell wrote:
What I suggested to the KVM developers is to start out with the
vexpress
On Thu, Dec 1, 2011 at 10:58 AM, Sasha Levin levinsasha...@gmail.com wrote:
I was looking into the concept of adding 'dedicated' threads to the
threadpool, since when the threadpool was added originally one of the
purposes was to have all worker threads in a single place.
This way we could
On 11/30/2011 10:59 AM, Raghavendra K T wrote:
Add a hypercall to KVM hypervisor to support pv-ticketlocks
KVM_HC_KICK_CPU allows the calling vcpu to kick another vcpu out of halt
state.
The presence of these hypercalls is indicated to guest via
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together
in transferring $19,500,000.USD from my bank. Finally if you are interested I
shall provide you with more details. my private Email: mrsong.l...@yahoo.cn
--
To unsubscribe from this list: send the line unsubscribe kvm
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together
in transferring $19,500,000.USD from my bank. Finally if you are interested I
shall provide you with more details. my private Email: mrsong.l...@yahoo.cn
--
To unsubscribe from this list: send the line unsubscribe kvm
On 2011-11-04 09:45, Jan Kiszka wrote:
[ Rebase of v1 over yesterday's linux-next ]
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access via sysfs, but that service wrongly
assumes it is only called by one
This patch introduces two ioctls for virtual cpus, that are only
valid for kernel virtual machines that are controlled by userspace.
Each virtual cpu has its individual address space in this mode of
operation, and each address space is backed by the gmap
implementation just like the address space
This patch allows the user to fault in pages on a virtual cpus
address space for user controlled virtual machines. Typically this
is superfluous because userspace can just create a mapping and
let the kernel's page fault logic take are of it. There is one
exception: SIE won't start if the lowcore
Hi Avi, Hi Marcelo,
this patch series introduces an interface to allow a privileged userspace
program to control a KVM virtual machine. The interface is intended for
use by a machine simulator called CECSIM that can simulate an entire
mainframe machine with nested virtualization and I/O for the
This patch disables the in-kernel interrupt stack for KVM virtual
machines that are controlled by user. Userspace has to take care
of handling interrupts on its own.
Signed-off-by: Carsten Otte co...@de.ibm.com
---
Index: linux-2.5-cecsim/arch/s390/kvm/kvm-s390.c
This patch introduces a new config option for user controlled kernel
virtual machines. It introduces a new ioctl named
KVM_S390_ENABLE_UCONTROL on the kvm file descriptor which allows for
a one way transition from a regular kernel virtual machine to a
user controlled virtual machine. The virtual
This patch introduces an interface to access the guest visible
storage keys. It supports three operations that model the behavior
that SSKE/ISKE/RRBE instructions would have if they were issued by
the guest. These instructions are all documented in the z architecture
principles of operation book.
This patch introduces a new exit reason in the kvm_run structure
named KVM_EXIT_UCONTROL. This exit indicates, that a virtual cpu
has regognized a fault on the host page table. The idea is that
userspace can handle this fault by mapping memory at the fault
location into the cpu's address space and
This patch announces a new capability KVM_CAP_S390_UCONTROL that
indicates that kvm can now support virtual machines that are
controlled by userspace.
Signed-off-by: Carsten Otte co...@de.ibm.com
---
---
arch/s390/kvm/kvm-s390.c |3 +++
include/linux/kvm.h |1 +
2 files changed, 4
This patch exports the SIE hardware control block to userspace
via the mapping of the vcpu file descriptor.
Signed-off-by: Carsten Otte co...@de.ibm.com
---
---
arch/s390/include/asm/kvm_host.h |2 ++
virt/kvm/kvm_main.c |5 +
2 files changed, 7 insertions(+)
---
This patch fixes definition of the idle_mask and the local_int array
in kvm_s390_float_interrupt. Previous definition had 64 cpus max
hardcoded instead of using KVM_MAX_VCPUS.
Signed-off-by: Carsten Otte co...@de.ibm.com
---
Index: linux-2.5-cecsim/arch/s390/include/asm/kvm_host.h
This patch disables in-kernel handling of SIE intercepts for user
controlled virtual machines. All intercepts are passed to userspace
via KVM_EXIT_SIE exit reason just like SIE intercepts that cannot be
handled in-kernel for regular KVM guests.
Signed-off-by: Carsten Otte co...@de.ibm.com
---
This patch makes sure user controlled virtual machines do not use a
system control area (sca). This is needed in order to create
virtual machines with more cpus than the size of the sca [64].
Signed-off-by: Carsten Otte co...@de.ibm.com
---
Index: linux-2.5-cecsim/arch/s390/kvm/kvm-s390.c
This patch fixes the return code of kvm_arch_vcpu_ioctl in case
of an unkown ioctl number.
Signed-off-by: Carsten Otte co...@de.ibm.com
---
Index: linux-2.5-cecsim/arch/s390/kvm/kvm-s390.c
===
---
On 12/01/2011 02:57 PM, Carsten Otte wrote:
Hi Avi, Hi Marcelo,
this patch series introduces an interface to allow a privileged userspace
program to control a KVM virtual machine. The interface is intended for
use by a machine simulator called CECSIM that can simulate an entire
mainframe
On 12/01/2011 02:57 PM, Carsten Otte wrote:
This patch introduces a new config option for user controlled kernel
virtual machines. It introduces a new ioctl named
KVM_S390_ENABLE_UCONTROL on the kvm file descriptor which allows for
a one way transition from a regular kernel virtual machine to
On 12/01/2011 02:57 PM, Carsten Otte wrote:
This patch introduces two ioctls for virtual cpus, that are only
valid for kernel virtual machines that are controlled by userspace.
Each virtual cpu has its individual address space in this mode of
operation, and each address space is backed by the
On 12/01/2011 02:57 PM, Carsten Otte wrote:
This patch exports the SIE hardware control block to userspace
via the mapping of the vcpu file descriptor.
Signed-off-by: Carsten Otte co...@de.ibm.com
---
---
arch/s390/include/asm/kvm_host.h |2 ++
virt/kvm/kvm_main.c |5
On 12/01/2011 02:57 PM, Carsten Otte wrote:
This patch exports the SIE hardware control block to userspace
via the mapping of the vcpu file descriptor.
else if (vmf-pgoff == KVM_COALESCED_MMIO_PAGE_OFFSET)
page = virt_to_page(vcpu-kvm-coalesced_mmio_ring);
#endif
+#if
On 12/01/2011 03:15 PM, Avi Kivity wrote:
+
+ if (kvm-arch.gmap)
+ gmap_free(kvm-arch.gmap);
+
+ kvm-arch.gmap = NULL;
Locking?
What happens if a vcpu is created afterwards?
Having read the code, I think you can repurpose the argument of
KVM_CREATE_VM to be a vm
On 12/01/2011 03:10 PM, Avi Kivity wrote:
On 12/01/2011 02:57 PM, Carsten Otte wrote:
Hi Avi, Hi Marcelo,
this patch series introduces an interface to allow a privileged userspace
program to control a KVM virtual machine. The interface is intended for
use by a machine simulator called
Hi,
my name's Daniele and I'm using the native linux kvm tool.
If I try to execute it in this way ./kvm run -d ~/linux-0.2.img I get
a kernel panic like this: http://paste.org/41673
Only using the addictional option -p idle=halt I can run a virtual machine.
Printing cat /proc/cpuinfo on the host i
In automated test environments, we often build and test
qemu from arbitrary paths, rather than installing them
on standard PATH directories. Of course, appending directories
to PATH might produce the desired result, but making it
possible to specify arbitrary qemu paths through environment
Print the paths of the programs under test
(qemu, qemu-img and qemu-io).
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
check |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/check b/check
index 84ef3e5..8499a04 100755
--- a/check
+++ b/check
@@ -158,6
Since we might want to test arbitrary qemu, qemu-img and
qemu-io paths, allow users to specify environment variable
values for QEMU_PROG, QEMU_IMG_PROG and QEMU_IO_PROG so
the testsuite will use those values rather than find them
on PATH. Obviously, if such env variables are not set
prior to
On 12/01/2011 03:37 PM, Daniele Carollo wrote:
Hi,
my name's Daniele and I'm using the native linux kvm tool.
If I try to execute it in this way ./kvm run -d ~/linux-0.2.img I get
a kernel panic like this: http://paste.org/41673
Only using the addictional option -p idle=halt I can run a
On Thu, 2011-12-01 at 15:48 +0200, Avi Kivity wrote:
On 12/01/2011 03:37 PM, Daniele Carollo wrote:
Hi,
my name's Daniele and I'm using the native linux kvm tool.
If I try to execute it in this way ./kvm run -d ~/linux-0.2.img I get
a kernel panic like this: http://paste.org/41673
Only
On 12/01/2011 03:50 PM, Sasha Levin wrote:
On Thu, 2011-12-01 at 15:48 +0200, Avi Kivity wrote:
On 12/01/2011 03:37 PM, Daniele Carollo wrote:
Hi,
my name's Daniele and I'm using the native linux kvm tool.
If I try to execute it in this way ./kvm run -d ~/linux-0.2.img I get
a
Il 01 dicembre 2011 14:48, Avi Kivity a...@redhat.com ha scritto:
On 12/01/2011 03:37 PM, Daniele Carollo wrote:
Hi,
my name's Daniele and I'm using the native linux kvm tool.
If I try to execute it in this way ./kvm run -d ~/linux-0.2.img I get
a kernel panic like this:
On 12/01/2011 03:54 PM, Daniele Carollo wrote:
Il 01 dicembre 2011 14:48, Avi Kivity a...@redhat.com ha scritto:
On 12/01/2011 03:37 PM, Daniele Carollo wrote:
Hi,
my name's Daniele and I'm using the native linux kvm tool.
If I try to execute it in this way ./kvm run -d ~/linux-0.2.img I
On 01.12.2011 14:26, Avi Kivity wrote:
On 12/01/2011 02:57 PM, Carsten Otte wrote:
This patch exports the SIE hardware control block to userspace
via the mapping of the vcpu file descriptor.
else if (vmf-pgoff == KVM_COALESCED_MMIO_PAGE_OFFSET)
page =
On 12/01/2011 03:59 PM, Carsten Otte wrote:
On 01.12.2011 14:26, Avi Kivity wrote:
On 12/01/2011 02:57 PM, Carsten Otte wrote:
This patch exports the SIE hardware control block to userspace
via the mapping of the vcpu file descriptor.
else if (vmf-pgoff ==
On Thu, 01 Dec 2011 15:15:03 +0200
Avi Kivity a...@redhat.com wrote:
+
+ if (kvm-arch.gmap)
+ gmap_free(kvm-arch.gmap);
+
+ kvm-arch.gmap = NULL;
Locking?
What happens if a vcpu is created afterwards?
I guess you don't mind too much since this is a privileged
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed that
will give the host the ability to tell the guest that it is being stopped and
should ignore the
On 2011-10-23 17:39, Vadim Rozenfeld wrote:
---
Makefile.target |2 +
target-i386/cpuid.c | 14 ++
target-i386/hyperv.c | 65
++
target-i386/hyperv.h | 37
4 files changed, 118
On 2011-10-23 17:39, Vadim Rozenfeld wrote:
---
target-i386/kvm.c | 73 +++-
1 files changed, 71 insertions(+), 2 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index 82fec8c..c061e3b 100644
--- a/target-i386/kvm.c
+++
On Thu, 01 Dec 2011 13:04:15 +0100
Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-11-04 09:45, Jan Kiszka wrote:
[ Rebase of v1 over yesterday's linux-next ]
This series tries to heal the currently broken locking scheme
around PCI config space accesses.
We have an interface lock
On Thu, 1 Dec 2011, Ian Campbell wrote:
On Wed, 2011-11-30 at 18:32 +, Stefano Stabellini wrote:
On Wed, 30 Nov 2011, Arnd Bergmann wrote:
KVM and Xen at least both fall into the single-return-value category,
so we should be able to agree on a calling conventions. KVM does not
have
On 11/30/2011 09:03 AM, Xiao Guangrong wrote:
On 11/29/2011 08:01 PM, Avi Kivity wrote:
On 11/29/2011 01:56 PM, Xiao Guangrong wrote:
On 11/29/2011 07:20 PM, Avi Kivity wrote:
We used to have a bitmap in a shadow page with a bit set for every slot
pointed to by the page. If we
On Thu, Dec 01, 2011 at 10:26:37AM +, Ian Campbell wrote:
On Wed, 2011-11-30 at 18:32 +, Stefano Stabellini wrote:
On Wed, 30 Nov 2011, Arnd Bergmann wrote:
KVM and Xen at least both fall into the single-return-value category,
so we should be able to agree on a calling
On 11/30/2011 07:15 AM, Takuya Yoshikawa wrote:
(2011/11/30 14:02), Takuya Yoshikawa wrote:
IIUC, even though O(1) is O(1) at the timing of GET DIRTY LOG, it
needs O(N) write
protections with respect to the total number of dirty pages:
distributed, but
actually each page fault, which should
On Thursday 01 December 2011, Catalin Marinas wrote:
Given the way register banking is done on AArch64, issuing an HVC on a
32-bit guest OS doesn't require translation on a 64-bit hypervisor. We
have a similar implementation at the SVC level (for 32-bit user apps on
a 64-bit kernel), the only
On Thu, 2011-12-01 at 15:10 +, Catalin Marinas wrote:
On Thu, Dec 01, 2011 at 10:26:37AM +, Ian Campbell wrote:
On Wed, 2011-11-30 at 18:32 +, Stefano Stabellini wrote:
On Wed, 30 Nov 2011, Arnd Bergmann wrote:
KVM and Xen at least both fall into the single-return-value
On Thu, Dec 01, 2011 at 03:42:19PM +, Arnd Bergmann wrote:
On Thursday 01 December 2011, Catalin Marinas wrote:
Given the way register banking is done on AArch64, issuing an HVC on a
32-bit guest OS doesn't require translation on a 64-bit hypervisor. We
have a similar implementation at
On Thursday 01 December 2011, Catalin Marinas wrote:
On Thu, Dec 01, 2011 at 03:42:19PM +, Arnd Bergmann wrote:
On Thursday 01 December 2011, Catalin Marinas wrote:
How do you deal with signed integer arguments passed into SVC or HVC from
a caller? If I understand the architecture
On Thu, Dec 01, 2011 at 04:44:40PM +, Arnd Bergmann wrote:
On Thursday 01 December 2011, Catalin Marinas wrote:
On Thu, Dec 01, 2011 at 03:42:19PM +, Arnd Bergmann wrote:
On Thursday 01 December 2011, Catalin Marinas wrote:
How do you deal with signed integer arguments passed into
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed
that
will give the host the ability to tell the guest
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed
that
will give the host the ability to tell the guest
On Wed, Nov 30, 2011 at 06:41:13PM +0100, Andrea Arcangeli wrote:
On Wed, Nov 30, 2011 at 09:52:37PM +0530, Dipankar Sarma wrote:
create the guest topology correctly and optimize for NUMA. This
would work for us.
Even on the case of 1 guest that fits in one node, you're not going to
max
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed that
will give the host the ability to tell the guest that it is being stopped and
should ignore the soft lockup warning that generates. This
On 12/01/2011 06:19 PM, Eric B Munson wrote:
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
+
static void cpu_update_state(void *opaque, int running, RunState state)
{
CPUState *env = opaque;
if (running) {
env-tsc_valid = false;
On 2011-12-01 18:19, Eric B Munson wrote:
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will
report spurious soft lockup warnings on resume. There are
kernel patches being discussed that will give
On 2011-12-01 18:31, Arend van Spriel wrote:
On 12/01/2011 06:19 PM, Eric B Munson wrote:
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
+
static void cpu_update_state(void *opaque, int running, RunState state)
{
CPUState *env = opaque;
if
On 2011-12-01 18:22, Eric B Munson wrote:
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed
that
will give
On Thu, Dec 01, 2011 at 10:55:20PM +0530, Dipankar Sarma wrote:
On Wed, Nov 30, 2011 at 06:41:13PM +0100, Andrea Arcangeli wrote:
On Wed, Nov 30, 2011 at 09:52:37PM +0530, Dipankar Sarma wrote:
create the guest topology correctly and optimize for NUMA. This
would work for us.
Even on
On Wed, 2011-11-23 at 16:03 +0100, Andrea Arcangeli wrote:
Hi!
On Mon, Nov 21, 2011 at 07:51:21PM -0600, Anthony Liguori wrote:
Fundamentally, the entity that should be deciding what memory should be
present
and where it should located is the kernel. I'm fundamentally opposed to
On Thu, Dec 01, 2011 at 06:36:23PM +0100, Andrea Arcangeli wrote:
On Thu, Dec 01, 2011 at 10:55:20PM +0530, Dipankar Sarma wrote:
On Wed, Nov 30, 2011 at 06:41:13PM +0100, Andrea Arcangeli wrote:
On Wed, Nov 30, 2011 at 09:52:37PM +0530, Dipankar Sarma wrote:
create the guest topology
Currently we silently fail if VMX is already in use by a different
virtualization technology.
This is bad since it's non-obvious for the user, and its not too uncommon
for users to have several of these installed on same host.
This patch adds a message to notify the user of the problem.
Cc:
Currently we silently fail if SVM is already in use by a different
virtualization technology.
This is bad since it's non-obvious for the user, and its not too uncommon
for users to have several of these installed on same host.
This patch adds a message to notify the user of the problem.
Cc:
It's enough for memory slot to be readable, as the comment above the check
states.
A user should be able to create read-only memory slot.
Cc: Avi Kivity a...@redhat.com
Cc: Marcelo Tosatti mtosa...@redhat.com
Cc: kvm@vger.kernel.org
Signed-off-by: Sasha Levin levinsasha...@gmail.com
---
[ CCing Jeremy's new email ID ]
Hi Avi,
Thanks for review and inputs.
On 12/01/2011 04:41 PM, Avi Kivity wrote:
On 11/30/2011 10:59 AM, Raghavendra K T wrote:
The hypercall needs to be documented in
Documentation/virtual/kvm/hypercalls.txt.
Yes, Sure 'll document. hypercalls.txt is a new
The attributes are not intrinsic features of the domain. User space will
need to set them. But in thinking about it a bit more I think the attributes
are more properties of the domain rather than a per map() operation
characteristic. I think a separate API might be appropriate. Define a
On Thu, 2011-12-01 at 14:58 -0600, Stuart Yoder wrote:
The attributes are not intrinsic features of the domain. User space will
need to set them. But in thinking about it a bit more I think the
attributes
are more properties of the domain rather than a per map() operation
On Tue, Nov 29, 2011 at 04:35:34PM -0500, Eric B Munson wrote:
Changes from V3:
Include CC's on patch 3
Drop clear flag ioctl and have the watchdog clear the flag when it is reset
Changes from V2:
A new kvm functions defined in kvm_para.h, the only change to pvclock is the
initial flag
On Thu, Dec 01, 2011 at 06:36:17PM +0100, Jan Kiszka wrote:
On 2011-12-01 18:22, Eric B Munson wrote:
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report
spurious
soft lockup warnings on
On Thu, Dec 01, 2011 at 12:19:38PM -0500, Eric B Munson wrote:
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report
spurious
soft lockup warnings on resume. There are kernel patches
On Thu, 01 Dec 2011, Marcelo Tosatti wrote:
On Thu, Dec 01, 2011 at 06:36:17PM +0100, Jan Kiszka wrote:
On 2011-12-01 18:22, Eric B Munson wrote:
On Thu, 01 Dec 2011, Jan Kiszka wrote:
On 2011-11-29 22:36, Eric B Munson wrote:
Often when a guest is stopped from the qemu console,
Currently, qemu-iotests is implemented outside
the KVM autotest realm. Although convenient if
you want to test the default qemu shipped with
your distro, it's not so convenient to integrate
with the KVM autotest workflow.
In order to take advantage of the fact kvm autotest
tests are already
As it is important for qemu-iotests that this particular
program is used.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/base.cfg.sample |1 +
client/tests/kvm/tests.cfg.sample |4
client/virt/kvm_installer.py | 24
3
In order to run always the latest up to date qemu iotests
on all KVM branches, insert qemu-iotests execution inside
KVM autotest. It'll attempt to git fetch the latest contents
of the qemu-iotests test suite, then carry on with tests,
reporting errors to autotest.
Besides having the latest test,
On Thu, 1 Dec 2011 12:26:42 +0200, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Dec 01, 2011 at 10:09:37AM +0200, Sasha Levin wrote:
On Thu, 2011-12-01 at 09:58 +0200, Michael S. Tsirkin wrote:
We'll presumably need some logic to increment is back,
to account for random workload
On Thu, 1 Dec 2011 10:12:37 +0200, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Dec 01, 2011 at 12:58:59PM +1030, Rusty Russell wrote:
On Thu, 1 Dec 2011 01:13:07 +0200, Michael S. Tsirkin m...@redhat.com
wrote:
For x86, stores into memory are ordered. So I think that yes, smp_XXX
(2011/12/02 4:42), Sasha Levin wrote:
It's enough for memory slot to be readable, as the comment above the check
states.
A user should be able to create read-only memory slot.
I submitted the original patch like you to speed up page table walking,
a hot path in KVM, and Avi applied the patch
On Mon, 2011-11-21 at 17:00 +0800, Alex,Shi wrote:
On Thu, 2011-10-20 at 16:38 +0800, Eric Dumazet wrote:
Le jeudi 20 octobre 2011 à 15:32 +0800, Alex,Shi a écrit :
percpu_xxx funcs are duplicated with this_cpu_xxx funcs, so replace them
for further code clean up.
And in preempt
(2011/12/02 10:15), Takuya Yoshikawa wrote:
(2011/12/02 4:42), Sasha Levin wrote:
It's enough for memory slot to be readable, as the comment above the check
states.
A user should be able to create read-only memory slot.
Note: at that time, it looked to me that the API did not allow me to
On 29/11/11 16:48, Alex Williamson wrote:
On Tue, 2011-11-29 at 15:34 +1100, Alexey Kardashevskiy wrote:
Hi!
On 29/11/11 14:46, Alex Williamson wrote:
On Tue, 2011-11-29 at 12:52 +1100, Alexey Kardashevskiy wrote:
Hi!
I tried (successfully) to run it on POWER and while doing that I found
On Fri, 2011-12-02 at 12:16 +0900, Takuya Yoshikawa wrote:
(2011/12/02 10:15), Takuya Yoshikawa wrote:
(2011/12/02 4:42), Sasha Levin wrote:
It's enough for memory slot to be readable, as the comment above the check
states.
A user should be able to create read-only memory slot.
Note:
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Currently, vcpu can be destructed only when kvm instance destroyed.
Change this to vcpu's destruction taken when its refcnt is zero,
and then vcpu MUST and CAN be destroyed before kvm's destroy.
Signed-off-by: Liu Ping Fan
(2011/12/02 14:46), Sasha Levin wrote:
On Fri, 2011-12-02 at 12:16 +0900, Takuya Yoshikawa wrote:
(2011/12/02 10:15), Takuya Yoshikawa wrote:
(2011/12/02 4:42), Sasha Levin wrote:
It's enough for memory slot to be readable, as the comment above the check
states.
A user should be able to
Signed-off-by: Sasha Levin levinsasha...@gmail.com
---
tools/kvm/builtin-run.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index 43cf2c4..33de4f6 100644
--- a/tools/kvm/builtin-run.c
+++ b/tools/kvm/builtin-run.c
@@
This patch adds a '--sandbox' argument when used in conjuction with a custom
rootfs, it allows running a script or an executable in the guest environment
by using executables and other files from the host.
This is useful when testing code that might cause problems on the host, or
to automate
On Fri, Dec 2, 2011 at 9:16 AM, Sasha Levin levinsasha...@gmail.com wrote:
This patch adds a '--sandbox' argument when used in conjuction with a custom
rootfs, it allows running a script or an executable in the guest environment
by using executables and other files from the host.
This is
On Fri, 2011-12-02 at 09:26 +0200, Pekka Enberg wrote:
On Fri, Dec 2, 2011 at 9:16 AM, Sasha Levin levinsasha...@gmail.com wrote:
This patch adds a '--sandbox' argument when used in conjuction with a custom
rootfs, it allows running a script or an executable in the guest environment
by
On Fri, 2011-12-02 at 09:26 +0200, Pekka Enberg wrote:
On Fri, Dec 2, 2011 at 9:16 AM, Sasha Levin levinsasha...@gmail.com wrote:
This patch adds a '--sandbox' argument when used in conjuction with a custom
rootfs, it allows running a script or an executable in the guest environment
by using
On Fri, 2011-12-02 at 09:39 +0200, Pekka Enberg wrote:
On Fri, 2011-12-02 at 09:26 +0200, Pekka Enberg wrote:
On Fri, Dec 2, 2011 at 9:16 AM, Sasha Levin levinsasha...@gmail.com
wrote:
This patch adds a '--sandbox' argument when used in conjuction with a
custom
rootfs, it allows
On Fri, Dec 2, 2011 at 9:44 AM, Sasha Levin levinsasha...@gmail.com wrote:
Would it not be better to introduce a new command that works like 'perf
stat', for example:
./kvm sandbox -k kernel to test -- trinity --mode=random --quiet -i
?
So basically proxy the first set of parameters to
1 - 100 of 102 matches
Mail list logo
