From: Jan Kiszka jan.kis...@siemens.com
Report KVM_EXIT_UNKNOWN, KVM_EXIT_FAIL_ENTRY, and KVM_EXIT_EXCEPTION
with more details to stderr. The latter two are so far x86-only, so move
them into the arch-specific handler. Integrate the Intel real mode
warning on KVM_EXIT_FAIL_ENTRY that qemu-kvm
From: Jan Kiszka jan.kis...@siemens.com
kvm_arch_reset_vcpu initializes mp_state, and that function is invoked
right after kvm_arch_init_vcpu.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c |2 --
1 files changed, 0
From: Jan Kiszka jan.kis...@siemens.com
If we lack kvm_para.h, MSR_KVM_ASYNC_PF_EN is not defined. The change in
kvm_arch_init_vcpu is just for consistency reasons.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c |8
From: Jin Dongming jin.dongm...@np.css.fujitsu.com
Add function for checking whether current CPU support mca broadcast.
Signed-off-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/cpu.h|1 +
target-i386/helper.c | 33
From: Jin Dongming jin.dongm...@np.css.fujitsu.com
When the following test case is injected with mce command, maybe user could not
get the expected result.
DATA
command cpu bank status mcg_status addr misc
(qemu) mce 1 10xbd00 0x05
From: Jan Kiszka jan.kis...@siemens.com
All CPUX86State variables before CPU_COMMON are automatically cleared on
reset. Reorder nmi_injected and nmi_pending to avoid having to touch
them explicitly.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Marcelo Tosatti
From: Jan Kiszka jan.kis...@siemens.com
The DPL is stored in the flags and not in the selector. In fact, the RPL
may differ from the DPL at some point in time, and so we were corrupting
the guest state so far.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Avi Kivity
From: Jan Kiszka jan.kis...@siemens.com
Instead of splattering the code with #ifdefs and runtime checks for
capabilities we cannot work without anyway, provide central test
infrastructure for verifying their availability both at build and
runtime.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
From: Jin Dongming jin.dongm...@np.css.fujitsu.com
Share same error handing, and rename this function after
MCIP (Machine Check In Progress) flag.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Signed-off-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
Signed-off-by: Marcelo
From: Jin Dongming jin.dongm...@np.css.fujitsu.com
Refactor codes for maintainability.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Signed-off-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c | 111
From: Jan Kiszka jan.kis...@siemens.com
This is required to support keeping VCPU states across a system reset.
If we do not read the current state before the reset,
cpu_synchronize_all_post_reset may write back incorrect state
information.
The first user of this will be MCE MSR synchronization
From: Jan Kiszka jan.kis...@siemens.com
There is no need to restrict writing back MCE MSRs to reset or full
state updates as setting their values has no side effects.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
CC: Huang Ying ying.hu...@intel.com
Signed-off-by: Marcelo Tosatti
On Thu, Jan 6, 2011 at 4:41 PM, Serge E. Hallyn se...@hallyn.com wrote:
Thanks, Stefan. That patch actually doesn't compile for me, because
it leaves references in hw/pckbd.c to both ioport92_write and
ioport92_read, which it deletes from there. Should ioport92_read
just be renamed to
On 01/06/2011 11:56 AM, Marcelo Tosatti wrote:
From: Jan Kiszkajan.kis...@siemens.com
QEMU supports only one VM, so there is only one kvm_state per process,
and we gain nothing passing a reference to it around. Eliminate any need
to refer to it outside of kvm-all.c.
Signed-off-by: Jan
Oops. I guess it was not intended to ignore the exception, but just do
cleanup in case of errors.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
client/tests/kvm/scripts/unattended.py |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
On 01/06/2011 01:32 AM, Avi Kivity wrote:
On 01/06/2011 12:10 PM, Zachary Amsden wrote:
Reasons to trap the TSC are numerous, but we want to avoid it as much
as possible for performance reasons.
We provide two conservative modes via modules parameters and userspace
hinting. First, the module
Rather than what it was found on the user's PATH.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/scripts/unattended.py |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/client/tests/kvm/scripts/unattended.py
On 01/06/2011 01:38 AM, Alexander Graf wrote:
On 06.01.2011, at 12:30, Zachary Amsden wrote:
On 01/06/2011 12:41 AM, Alexander Graf wrote:
Am 06.01.2011 um 11:10 schrieb Zachary Amsdenzams...@redhat.com:
Reasons to trap the TSC are numerous, but we want to avoid it as
On 01/06/2011 01:40 AM, Alexander Graf wrote:
On 06.01.2011, at 12:27, Zachary Amsden wrote:
On 01/06/2011 12:34 AM, Alexander Graf wrote:
Am 06.01.2011 um 11:10 schrieb Zachary Amsdenzams...@redhat.com:
Use an MSR to allow soft migration to hosts which do not support
TSC
On Thu, Jan 6, 2011 at 7:44 AM, Simon Horman ho...@verge.net.au wrote:
On Thu, Jan 06, 2011 at 11:22:42AM +0100, Eric Dumazet wrote:
Le jeudi 06 janvier 2011 à 18:33 +0900, Simon Horman a écrit :
Hi,
Back in October I reported that I noticed a problem whereby flow control
breaks down
On 06.01.2011, at 21:24, Zachary Amsden wrote:
On 01/06/2011 01:38 AM, Alexander Graf wrote:
On 06.01.2011, at 12:30, Zachary Amsden wrote:
On 01/06/2011 12:41 AM, Alexander Graf wrote:
Am 06.01.2011 um 11:10 schrieb Zachary Amsdenzams...@redhat.com:
Reasons to trap
On Thu, Jan 06, 2011 at 02:28:18PM +0100, Eric Dumazet wrote:
Le jeudi 06 janvier 2011 à 21:44 +0900, Simon Horman a écrit :
Hi Eric !
Thanks for the advice. I had thought about the socket buffer but at some
point it slipped my mind.
In any case the following patch seems to
On Thu, Jan 06, 2011 at 05:38:01PM -0500, Jesse Gross wrote:
[ snip ]
I know that everyone likes a nice netperf result but I agree with
Michael that this probably isn't the right question to be asking. I
don't think that socket buffers are a real solution to the flow
control problem: they
subscription
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 01/06/2011 12:38 PM, Alexander Graf wrote:
snip
Sure, I'm not saying your patch is bad or goes in the wrong direction. I'd just
think it'd be awesome to have an easy way for the guest OS to know that
something as crucial as TSC reading speed got changed, hopefully even TSC
frequency.
On Wed, 2011-01-05 at 18:04 +0100, Peter Zijlstra wrote:
On Wed, 2011-01-05 at 17:57 +0100, Mike Galbraith wrote:
+ p_cfs_rq = cfs_rq_of(pse);
+ local = 1;
+ }
+#endif
+
+ /* Tell the scheduler that we'd really like pse to run next. */
+
On Thu, 06 Jan 2011 14:15:37 +0100
Dominik Klein d...@in-telegence.net wrote:
Hi
I am playing with cgroups and try to limit block io for guests.
The proof of concept is:
# mkdir /dev/cgroup/blkio
# mount -t cgroup -o blkio blkio /dev/cgroup/blkio/
# cd blkio/
# mkdir test
# cd test/
If the migration destination specifies an assigned device, qemu will
segfault because there is always expected to be an end marker for
fields. Add to our dummy VMStateDescription to avoid this.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/device-assignment.c |5 -
1
qemu consists of several threads. Cgroup works per thread now.
Could you double check all threads for qemu are in a cgroup ?
I think you have to write all thread-ID to tasks file when you
move qemu after starting it.
As stated yesterday: Yes, that was the problem. Works as expected now,
Fix:
[ 1001.499596] ===
[ 1001.499599] [ INFO: suspicious rcu_dereference_check() usage. ]
[ 1001.499601] ---
[ 1001.499604] include/linux/kvm_host.h:301 invoked rcu_dereference_check()
without
We can interrupt the vcpu only when it's running in guest mode
to reduce IPI
It looks like only ia64 and x86 need to send IPI to other vcpus, so
i only add the implementation of 'vcpu-guest_mode' in ia64, but i
don't know ia64 well, please point out the right way for me if the
implementation is
Now, we have 'vcpu-guest_mode' to judge whether need to send
ipi to other cpus, this way is very exact, so checking request
bit is needless, then we can drop the spinlock let it's collateral
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
include/linux/kvm_host.h |6 --
On Wed, Dec 29, 2010 at 01:51:25PM -0600, Peter Tyser wrote:
Previously SPRGs 4-7 were improperly read and written in
kvm_arch_vcpu_ioctl_get_regs() and kvm_arch_vcpu_ioctl_set_regs();
Signed-off-by: Peter Tyser pty...@xes-inc.com
---
I noticed this while grepping for somthing unrelated and
I want to build kvm kernel module for powerpc using cross compiler. I
downloaded kernel source code from
http://www.linux-kvm.org/page/PowerPC_440_Host_Kernel. Inside that
kvm_source folder when I do make ARCH=powerpc menuconfig, inside
virtualization menu, option kvm is not present. I have
On Thu, Jan 6, 2011 at 10:39 AM, Dushyant Bansal
cs5070...@cse.iitd.ac.in wrote:
I want to build kvm kernel module for powerpc using cross compiler. I
downloaded kernel source code from
http://www.linux-kvm.org/page/PowerPC_440_Host_Kernel. Inside that
kvm_source folder when I do make
Hi,
Thanks for the response.
My aim is to install kvm on a powerpc system. I will give a detailed
description of the environment.
Host arch: x86
kernel: 2.6.32.25 (ubuntu 10.04 32 bit)
I have emulated powerpc using qemu-system-ppc and installed debian on
top of this.
guest os:
101 - 136 of 136 matches
Mail list logo
