On 10/12/2011 05:07 AM, Lucas Meneghel Rodrigues wrote:
This is a first attempt at providing a libvirt VM class,
in order to implement the needed methods for virt testing.
With this class, we will be able to implement a libvirt
test, that behaves similarly to the KVM test.
As of implementation
(2011/10/10 19:26), Avi Kivity wrote:
On 10/10/2011 08:06 AM, Lai Jiangshan wrote:
From: Kenji Kaneshigekaneshige.ke...@jp.fujitsu.com
Currently, NMI interrupt is blindly sent to all the vCPUs when NMI
button event happens. This doesn't properly emulate real hardware on
which NMI button
(2011/10/12 2:00), Lai Jiangshan wrote:
From: Kenji Kaneshigekaneshige.ke...@jp.fujitsu.com
Currently, NMI interrupt is blindly sent to all the vCPUs when NMI
button event happens. This doesn't properly emulate real hardware on
which NMI button event triggers LINT1. Because of this, NMI is
On 10/12/2011 05:07 AM, Lucas Meneghel Rodrigues wrote:
This is an initial implementation for a libvirt monitor.
With it, we plan on making the libvirt test use all the
monitor features, making most of the tests available for
kvm available for libvirt.
As of implementation details, it uses
On Tue, Oct 11, 2011 at 06:07:11PM -0300, Lucas Meneghel Rodrigues wrote:
This is a first attempt at providing a libvirt VM class,
in order to implement the needed methods for virt testing.
With this class, we will be able to implement a libvirt
test, that behaves similarly to the KVM test.
Dear All,
I am doing some disk io performance testing on the following environment:
Dell AMD R515 with:
- debian6 (2.6.32) on host and guests.
- raid1 mirror on a perc h700
- lvm used to create virtual disks volumes
- virtio enabled per default on 2.6.32 and used for nic and disk drivers
For my
This patch adds the decompression operation when confirming the qcow or
qcow2 image is compressed. This patch also divides the read cluster
fucntion into two which are respective for qcow and qcow2 in order to be
convenient to support these two kind images. Add some macros for qcow.
On Wed, Oct 12, 2011 at 4:00 PM, Lan Tianyu tianyu@intel.com wrote:
This patch adds the decompression operation when confirming the qcow or
qcow2 image is compressed. This patch also divides the read cluster
fucntion into two which are respective for qcow and qcow2 in order to be
The MSI-X page must start below the address that comes after the end of
a region. Otherwise we risk to register it twice. This bug existed since
day #1 of the MSI-X support and was now reveal by
memory.c:1201: memory_region_add_subregion_common: Assertion
`!subregion-parent' failed.
On Wed, 2011-10-12 at 19:02 +0200, Jan Kiszka wrote:
The MSI-X page must start below the address that comes after the end of
a region. Otherwise we risk to register it twice. This bug existed since
day #1 of the MSI-X support and was now reveal by
memory.c:1201:
I'm running a stock Centos 5.7 on an AMD machine install with KVM 83
on a 2.6.18 kernel. I'm having trouble with a Debian Squeeze guest
running on a bridged ethernet (there are three ethernet cards in the
machine for different networks) sporadically losing its network
connection. I'm running a
Hi all,
I'm working on Chromium OS development. We have a pretty elaborate
chroot inside of which we carry out all development. We use KVM to
launch Chromium OS builds inside a VM for testing. Turns out that for
some reason, when QEMU is launched from inside the chroot, KVM itself
seems not to be
On 12.10.2011, at 20:49, Jorge Lucangeli Obes wrote:
Hi all,
I'm working on Chromium OS development. We have a pretty elaborate
chroot inside of which we carry out all development. We use KVM to
launch Chromium OS builds inside a VM for testing. Turns out that for
some reason, when QEMU
On Wed, Oct 12, 2011 at 3:52 PM, Jorge Lucangeli Obes
jorg...@chromium.org wrote:
On Wed, Oct 12, 2011 at 12:55 PM, Alexander Graf ag...@suse.de wrote:
On 12.10.2011, at 20:49, Jorge Lucangeli Obes wrote:
Hi all,
I'm working on Chromium OS development. We have a pretty elaborate
chroot
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
The code size expands somewhat, and its probably better to just call
a function rather than inline it.
Signed-off-by: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
---
arch/x86/Kconfig |3 +++
kernel/Kconfig.locks |2 +-
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
Although the lock_spinning calls in the spinlock code are on the
uncommon path, their presence can cause the compiler to generate many
more register save/restores in the function pre/postamble, which is in
the fast path. To avoid this,
From: Stefano Stabellini stefano.stabell...@eu.citrix.com
Signed-off-by: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
---
arch/x86/xen/smp.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
index 4dec905..2d01aeb 100644
---
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
If interrupts were enabled when taking the spinlock, we can leave them
enabled while blocking to get the lock.
If we can enable interrupts while waiting for the lock to become
available, and we take an interrupt before entering the poll,
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
Maintain a flag in the LSB of the ticket lock tail which indicates
whether anyone is in the lock slowpath and may need kicking when
the current holder unlocks. The flags are set when the first locker
enters the slowpath, and cleared when
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
Increment ticket head/tails by 2 rather than 1 to leave the LSB free
to store a is in slowpath state bit. This halves the number
of possible CPUs for a given ticket size, but this shouldn't matter
in practice - kernels built for 32k+ CPU
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
Replace the old Xen implementation of PV spinlocks with and implementation
of xen_lock_spinning and xen_unlock_kick.
xen_lock_spinning simply registers the cpu in its entry in lock_waiting,
adds itself to the waiting_cpus set, and blocks
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
There's no need to do it at very early init, and doing it there
makes it impossible to use the jump_label machinery.
Signed-off-by: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
---
arch/x86/xen/smp.c |2 +-
1 files changed, 1
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
[ Changes since last posting:
- Use lock add for unlock operation rather than lock xadd; it is
equivalent to add; mfence, but more efficient than both lock
xadd and mfence.
I think this version is ready for submission.
]
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
Rather than outright replacing the entire spinlock implementation in
order to paravirtualize it, keep the ticket lock implementation but add
a couple of pvops hooks on the slow patch (long spin on lock, unlocking
a contended lock).
Ticket
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
Now that the paravirtualization layer doesn't exist at the spinlock
level any more, we can collapse the __ticket_ functions into the arch_
functions.
Signed-off-by: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
---
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
Signed-off-by: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
---
arch/x86/xen/spinlock.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/x86/xen/spinlock.c b/arch/x86/xen/spinlock.c
index
On Tue, Oct 04, 2011 at 03:26:19PM +0200, Michael S. Tsirkin wrote:
Get rid of manually cut and pasted ssdt_proc,
use ssdt compiled by iasl and offsets extracted
by acpi_extract instead.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
FYI - I pushed the ACPI DSDT simplifications series
27 matches
Mail list logo
