Hi
Please send in any agenda items you are interested in covering.
Later, Juan.
--
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
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/x86/include/asm/kvm_host.h |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index bd69c93..4610166 100644
---
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/x86/kvm/mmu.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 71819c0..7570992 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -946,7
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/x86/kvm/mmu.c | 26 +-
arch/x86/kvm/mmu_audit.c |4 ++--
2 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 7570992..844fcce
On Sun, Jan 15, 2012 at 02:17:22PM +0200, Gleb Natapov wrote:
Return to behaviour perf MSR had before introducing vPMU in case vPMU
is disabled. Some guests access those registers unconditionally and do
not expect it to fail.
Signed-off-by: Gleb Natapov g...@redhat.com
Applied, thanks.
--
On Sun, Jan 15, 2012 at 03:18:14PM +0100, Jan Kiszka wrote:
Nothing useful remaining there.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Done, thanks.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info
On Sun, Jan 15, 2012 at 12:06:12PM +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
Remove this divergence from upstream. It is practically unused today as
the default mode is in-kernel irqchip. We keep the command line switch
for now, adding a warning that there is no effect
On Sun, Jan 15, 2012 at 04:17:31PM +0200, Avi Kivity wrote:
Otherwise, the dirty log information is lost in the kernel forever.
Fixes opensuse-12.1 boot screen, which changes the vga windows rapidly.
Signed-off-by: Avi Kivity a...@redhat.com
---
This patch gives me a deja vu - I'm sure
On Tue, Jan 17, 2012 at 10:28:11AM +0800, Xiao Guangrong wrote:
On 01/16/2012 05:38 PM, Avi Kivity wrote:
On 01/16/2012 11:32 AM, Xiao Guangrong wrote:
- trace vcpu_id for these events
We can infer the vcpu id from the kvm_entry tracepoints, no?
Thanks for your review, Avi!
On Mon, Jan 16, 2012 at 10:08:40AM +, Stefan Hajnoczi wrote:
On Mon, Jan 16, 2012 at 9:32 AM, Xiao Guangrong
xiaoguangr...@linux.vnet.ibm.com wrote:
+DESCRIPTION
+---
+You can analyze some crucial events and statistics with this
+'perf kvm-events' command.
This line is
On Mon, Jan 16, 2012 at 03:08:43PM +0200, Avi Kivity wrote:
movsx/movzx destination operands currently have a hack for the operand size.
Add OpMem8 and use it to remove the hack.
I'll wait with this until Nadav's more direct fix is in.
Avi Kivity (2):
KVM: x86 emulator: add 8-bit memory
On 2012-01-17 12:25, Marcelo Tosatti wrote:
On Sun, Jan 15, 2012 at 04:17:31PM +0200, Avi Kivity wrote:
Otherwise, the dirty log information is lost in the kernel forever.
Fixes opensuse-12.1 boot screen, which changes the vga windows rapidly.
Signed-off-by: Avi Kivity a...@redhat.com
---
On 2012-01-16 18:11, Alex Williamson wrote:
The core PCI code sets the multifunction bit in the header before
calling the device initfn. For device assignment, we're blasting
that value with the actual hardware value, so nobody sees the
additional functions if the devices isn't physically
From: Davidlohr Bueso d...@gnu.org
Also use true instead of 1 for enabling by default.
Signed-off-by: Davidlohr Bueso d...@gnu.org
---
arch/x86/kvm/svm.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index fce3ba0..7bbd17c
- Original Message -
On 2012-01-16 18:11, Alex Williamson wrote:
The core PCI code sets the multifunction bit in the header before
calling the device initfn. For device assignment, we're blasting
that value with the actual hardware value, so nobody sees the
additional functions
Juan Quintela quint...@redhat.com wrote:
Hi
Please send in any agenda items you are interested in covering.
Hi
THere is nothing for the agenda today (I asked really late for it
though, so apologies for that).
Today call gets cancelled.
Happy hacking, Juan.
Later, Juan.
--
To unsubscribe
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/virt/virt_vm.py | 27 +++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/client/virt/virt_vm.py b/client/virt/virt_vm.py
index 32593c1..c2b6586 100644
--- a/client/virt/virt_vm.py
+++
There is migration_control.srv which work with old version of kvm config
files (tests.cfg, subtest.cfg, etc..). Because config files was changed
this control code stopped working. This patch repairs this problem and
add new configuration file tests-config.cfg which separate autotest's
And additional reduce memory usage of cpu flags test stress
because there is problem with link bandwith during migration.
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/tests/kvm/tests.cfg.sample| 43 +-
client/tests/kvm/tests/cpuflags.py | 292
On 01/17/2012 04:55 AM, Marcelo Tosatti wrote:
On Tue, Jan 17, 2012 at 10:28:11AM +0800, Xiao Guangrong wrote:
On 01/16/2012 05:38 PM, Avi Kivity wrote:
On 01/16/2012 11:32 AM, Xiao Guangrong wrote:
- trace vcpu_id for these events
We can infer the vcpu id from the kvm_entry tracepoints,
Changes from V8:
Make KVM_GUEST_PAUSED a per vm ioctl instead of per vcpu
Changes from V7:
Define KVM_CAP_GUEST_PAUSED and support check
Call mark_page_dirty () after setting PVCLOCK_GUEST_STOPPED
Changes from V6:
Use __this_cpu_and when clearing the PVCLOCK_GUEST_STOPPED flag
Changes from V5:
A suspended VM can cause spurious soft lockup warnings. To avoid these, the
watchdog now checks if the kernel knows it was stopped by the host and skips
the warning if so. When the watchdog is reset successfully, clear the guest
paused flag.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc:
Now that we have a flag that will tell the guest it was suspended, create an
interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc:
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 2012-01-17 19:07, 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 2012-01-17 19:04, Eric B Munson wrote:
Now that we have a flag that will tell the guest it was suspended, create an
interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: ry...@linux.vnet.ibm.com
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
Now that we have a flag that will tell the guest it was suspended, create an
interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc:
When a host stops or suspends a VM it will set a flag to show this. The
watchdog will use these functions to determine if a softlockup is real, or the
result of a suspended VM.
Signed-off-by: Eric B Munson emun...@mgebm.net
asm-generic changes Acked-by: Arnd Bergmann a...@arndb.de
Cc:
This flag will be used to check if the vm was stopped by the host when a soft
lockup was detected. The host will set the flag when it stops the guest. On
resume, the guest will check this flag if a soft lockup is detected and skip
issuing the warning.
Signed-off-by: Eric B Munson
A suspended VM can cause spurious soft lockup warnings. To avoid these, the
watchdog now checks if the kernel knows it was stopped by the host and skips
the warning if so. When the watchdog is reset successfully, clear the guest
paused flag.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc:
On 01/18/2012 01:31 AM, David Ahern wrote:
Relying on the existing tracepoints will make the tool work on older
kernels.
We can drop all new events, but unfortunately, the information of the origin
tracepoints is not enough, at least vcpu_id need be traced in theses events
to match its
3.2.0-rc7-20120117-0605 #1 Bochs
Bochs
EIP: 0060:[c14069ae] EFLAGS: 00010086 CPU: 0
EIP is at nmi_cpu_setup.clone.6+0x2e/0xb0
EAX: EBX: df89894c ECX: c0010005 EDX:
ESI: 0001 EDI: c168e5c0 EBP: df8addf4 ESP: df8adde4
DS: 007b ES: 007b FS: GS: 0033 SS: 0068
Process
included all all parties that
I
thought may be relevant.
I'm getting the following error from my guest kernel when running
oprofile within qemu-kvm:
general protection fault: [#1]
Modules linked in:
Pid: 896, comm: oprofiled Not tainted 3.2.0-rc7-20120117-0605 #1
Bochs
Bochs
EIP: 0060
On 01/17/2012 07:32 PM, Xiao Guangrong wrote:
There is an ongoing 'discussion' about modifying existing tracepoints
which your proposed patch violates. This is the start of it:
Hmm, i think we can still add completed tracepoints in the new version kernel,
if old version kernel is used, we
On 17.01.2012, at 06:56, Paul Mackerras pau...@samba.org wrote:
On Mon, Jan 16, 2012 at 02:04:29PM +0100, Alexander Graf wrote:
On 20.12.2011, at 11:22, Paul Mackerras wrote:
@@ -152,6 +152,8 @@ static unsigned long do_h_register_vpa(struct kvm_vcpu
*vcpu,
flags = 7;
if (flags
On Tue, Jan 17, 2012 at 10:27:26AM +0100, Alexander Graf wrote:
The thing I was getting at was not the map during the lifetime, but
the map during registration. Currently we have:
1) Set VPA to x
2) Assign feature y to VPA
3) Use VPA
1 and 2 are the slow path, 3 occurs more frequently.
On 17.01.2012, at 12:31, Paul Mackerras wrote:
On Tue, Jan 17, 2012 at 10:27:26AM +0100, Alexander Graf wrote:
The thing I was getting at was not the map during the lifetime, but
the map during registration. Currently we have:
1) Set VPA to x
2) Assign feature y to VPA
3) Use VPA
1
38 matches
Mail list logo
