Thank you for commenting on my patch set.
(2012/11/14 11:31), Steven Rostedt wrote:
On Tue, 2012-11-13 at 18:03 -0800, David Sharp wrote:
On Tue, Nov 13, 2012 at 6:00 PM, Steven Rostedt wrote:
On Wed, 2012-11-14 at 10:36 +0900, Yoshihiro YUNOMAE wrote:
To merge the data like previous patter
于 2012年11月14日 05:22, Marcelo Tosatti 写道:
> On Thu, Nov 01, 2012 at 01:55:04PM +0800, zhangyanfei wrote:
>> 于 2012年10月31日 17:01, Hatayama, Daisuke 写道:
>>>
>>>
-Original Message-
From: kexec-boun...@lists.infradead.org
[mailto:kexec-boun...@lists.infradead.org] On Behalf Of zha
Currently, kdump just makes all the logical processors leave VMX operation by
executing VMXOFF instruction, so any VMCSs active on the logical processors may
be corrupted. But, sometimes, we need the VMCSs to debug guest images contained
in the host vmcore. To prevent the corruption, we should VMCL
crash_clear_loaded_vmcss is added to VMCLEAR vmcss loaded on all
cpus. And when loading kvm_intel module, the function pointer will be
made valid.
The percpu variable vmclear_skipped is added to flag the case that
if loaded_vmcss_on_cpu list is being modified while the machine crashes
and doing kdu
Signed-off-by: Zhang Yanfei
---
arch/x86/kvm/vmx.c | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 4ff0ab9..029ec7b 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -41,6 +41,7 @@
#i
On Wed, Oct 31, 2012 at 08:47:06PM -0200, Marcelo Tosatti wrote:
> Improve performance of time system calls when using Linux pvclock,
> by reading time info from fixmap visible copy of pvclock data.
>
> Originally from Jeremy Fitzhardinge.
>
> Signed-off-by: Marcelo Tosatti
>
> Index: vsyscall
On Tue, Nov 13, 2012 at 04:26:16PM +0800, Xiao Guangrong wrote:
> Hi Marcelo,
>
> On 11/13/2012 07:10 AM, Marcelo Tosatti wrote:
> > On Mon, Nov 05, 2012 at 05:59:26PM +0800, Xiao Guangrong wrote:
> >> Do not drop large spte until it can be insteaded by small pages so that
> >> the guest can happl
On Wed, Nov 14, 2012 at 12:33:50AM +0900, Takuya Yoshikawa wrote:
> Ccing live migration developers who should be interested in this work,
>
> On Mon, 12 Nov 2012 21:10:32 -0200
> Marcelo Tosatti wrote:
>
> > On Mon, Nov 05, 2012 at 05:59:26PM +0800, Xiao Guangrong wrote:
> > > Do not drop large
Alex Williamson writes:
> Hi Anthony,
>
> Please pull the tag below. I posted the linux-headers update
> separately on Oct-15; since it hasn't been applied and should be
> non-controversial, I include it again here. Thanks,
>
> Alex
>
Pulled. Thanks.
Regards,
Anthony Liguori
> The following
On Wed, Nov 14, 2012 at 05:46:45PM +0100, emdel wrote:
> On Tue, Nov 13, 2012 at 10:29 AM, Gleb Natapov wrote:
>
> > KVM does not implement VT-d spec if this is your question. Any help with
> > this will be appreciated.
> >
>
> Hello everybody,
> following this link [1] it looks like that we can
On Wed, Nov 14, 2012 at 06:31:30PM +0100, emdel wrote:
> On Wed, Nov 14, 2012 at 6:06 PM, Gleb Natapov wrote:
>
> > KVM uses VT-d on a host for device assignment. Guest running inside KVM
> > will not see VT-d though since KVM does not emulate it.
> >
>
> So another question comes up in my mind:
On Nov 1, 2012, at 11:18 AM, Avi Kivity wrote:
>> +
>> +/* Set the appropriate status bits based on host CPU features, before
>> we hit the scheduler */
>> +kvm_mips_set_c0_status();
>> +
>> +local_irq_enable();
>
> Ah, so you handle exits with interrupts enabled. But that's not ho
On Wed, Nov 14, 2012 at 12:42:48PM +0200, Gleb Natapov wrote:
> On Wed, Oct 31, 2012 at 08:47:06PM -0200, Marcelo Tosatti wrote:
> > Improve performance of time system calls when using Linux pvclock,
> > by reading time info from fixmap visible copy of pvclock data.
> >
> > Originally from Jeremy
On 11/14/2012 10:37 PM, Marcelo Tosatti wrote:
> On Tue, Nov 13, 2012 at 04:26:16PM +0800, Xiao Guangrong wrote:
>> Hi Marcelo,
>>
>> On 11/13/2012 07:10 AM, Marcelo Tosatti wrote:
>>> On Mon, Nov 05, 2012 at 05:59:26PM +0800, Xiao Guangrong wrote:
Do not drop large spte until it can be instea
On 11/14/2012 10:44 PM, Marcelo Tosatti wrote:
> On Wed, Nov 14, 2012 at 12:33:50AM +0900, Takuya Yoshikawa wrote:
>> Ccing live migration developers who should be interested in this work,
>>
>> On Mon, 12 Nov 2012 21:10:32 -0200
>> Marcelo Tosatti wrote:
>>
>>> On Mon, Nov 05, 2012 at 05:59:26PM
On 11/14/2012 11:45 AM, Blower, Melanie wrote:
[1.] gcc -O0 assembly arch/x86/kvm/emulate.c gets compilation failure --
incorrect register restrictions
[2.] Full description of the problem/report:
I'm trying to compile this file at -O0, but gcc chokes in register allocation
at the inline assemb
The following changes since commit ce34cf72fe508b27a78f83c184142e8d1e6a048a:
Merge remote-tracking branch 'awilliam/tags/vfio-pci-for-qemu-1.3.0-rc0' into
staging (2012-11-14 08:53:40 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
Improve performance of time system calls when using Linux pvclock,
by reading time info from fixmap visible copy of pvclock data.
Originally from Jeremy Fitzhardinge.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/vdso/vclock_gettime.c
=
As noted by Gleb, not advertising SSE2 support implies
no RDTSC barriers.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/include/asm/pvclock.h
===
--- vsyscall.orig/arch/x86/include/asm/pvclock.h
+++ vsyscall/arch/x86/inclu
Originally from Jeremy Fitzhardinge.
Introduce generic, non hypervisor specific, pvclock initialization
routines.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kernel/pvclock.c
===
--- vsyscall.orig/arch/x86/kernel/pvclo
From: Jan Kiszka
So far we only removed them from the guest, leaving its states in the
list. This made it impossible for gdb to re-enable breakpoints on the
same address after re-attaching.
Signed-off-by: Jan Kiszka
Signed-off-by: Marcelo Tosatti
---
kvm-all.c |2 ++
1 files changed, 2 in
This patchset, based on earlier work by Jeremy Fitzhardinge, implements
paravirtual clock vsyscall support.
It should be possible to implement Xen support relatively easily.
It reduces clock_gettime from 500 cycles to 200 cycles
on my testbox.
Please review.
v4:
- remove aligned_pvti structure
Originally from Jeremy Fitzhardinge.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/include/linux/sched.h
===
--- vsyscall.orig/include/linux/sched.h
+++ vsyscall/include/linux/sched.h
@@ -107,6 +107,14 @@ extern unsigned long this_
KVM added a global variable to guarantee monotonicity in the guest.
One of the reasons for that is that the time between
1. ktime_get_ts(×pec);
2. rdtscll(tsc);
Is variable. That is, given a host with stable TSC, suppose that
two VCPUs read the same time via ktime_get_ts() above.
As suggested by John, export time data similarly to how its
done by vsyscall support. This allows KVM to retrieve necessary
information to implement vsyscall support in KVM guests.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/include/linux/pvclock_gtod.h
===
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kernel/pvclock.c
===
--- vsyscall.orig/arch/x86/kernel/pvclock.c
+++ vsyscall/arch/x86/kernel/pvclock.c
@@ -45,6 +45,19 @@ void pvclock_resume(void)
atomic64_set(&last_
We want to expose the pvclock shared memory areas, which
the hypervisor periodically updates, to userspace.
For a linear mapping from userspace, it is necessary that
entire page sized regions are used for array of pvclock
structures.
There is no such guarantee with per cpu areas, therefore move
With master clock, a pvclock clock read calculates:
ret = system_timestamp + [ (rdtsc + tsc_offset) - tsc_timestamp ]
Where 'rdtsc' is the host TSC.
system_timestamp and tsc_timestamp are unique, one tuple
per VM: the "master clock".
Given a host with synchronized TSCs, its obvious that
guest
TSC initialization will soon make use of online_vcpus.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/ia64/kvm/kvm-ia64.c
===
--- vsyscall.orig/arch/ia64/kvm/kvm-ia64.c
+++ vsyscall/arch/ia64/kvm/kvm-ia64.c
@@ -1330,6 +1330,11
Originally from Jeremy Fitzhardinge.
We can copy the information directly from "struct pvclock_vcpu_time_info",
remove pvclock_shadow_time.
Reviewed-by: Glauber Costa
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kernel/pvclock.c
=
Hook into generic pvclock vsyscall code, with the aim to
allow userspace to have visibility into pvclock data.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kernel/kvmclock.c
===
--- vsyscall.orig/arch/x86/kernel/kvmclock
As requested by Glauber, do not update kvmclock area on vcpu->pcpu
migration, in case the host has stable TSC.
This is to reduce cacheline bouncing.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kvm/x86.c
===
--- vsysca
Otherwise its possible for an unrelated KVM_REQ_UPDATE_CLOCK (such as due to CPU
migration) to clear the bit.
Noticed by Paolo Bonzini.
Reviewed-by: Gleb Natapov
Reviewed-by: Glauber Costa
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kvm/x86.c
==
Allow the caller to pass host tsc value to kvm_x86_ops->read_l1_tsc().
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/include/asm/kvm_host.h
===
--- vsyscall.orig/arch/x86/include/asm/kvm_host.h
+++ vsyscall/arch/x86/includ
Register a notifier for clocksource change event. In case
the host switches to clock other than TSC, disable master
clock usage.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kvm/x86.c
===
--- vsyscall.orig/arch/x86/kvm/x8
On 11/14/2012 04:08 PM, Marcelo Tosatti wrote:
As suggested by John, export time data similarly to how its
done by vsyscall support. This allows KVM to retrieve necessary
information to implement vsyscall support in KVM guests.
Signed-off-by: Marcelo Tosatti
Thanks for the updates here. The no
Migrate 16 bytes for en/sts fields (which is the correct size),
increase version to 3, and document how to support incoming
migration from qemu-kvm 1.2.
Acked-by: Paolo Bonzini
Signed-off-by: Marcelo Tosatti
---
hw/acpi_piix4.c | 50 ++
1 files
Originally from Jeremy Fitzhardinge.
pvclock_get_time_values, which contains the memory barriers
will be removed by next patch.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kernel/pvclock.c
===
--- vsyscall.orig/arch/x86
Originally from Jeremy Fitzhardinge.
So code can be reused.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/kernel/pvclock.c
===
--- vsyscall.orig/arch/x86/kernel/pvclock.c
+++ vsyscall/arch/x86/kernel/pvclock.c
@@ -26,13 +
CCing Peter and Ingo.
On Wed, Nov 14, 2012 at 10:08:31PM -0200, Marcelo Tosatti wrote:
> Originally from Jeremy Fitzhardinge.
>
> Signed-off-by: Marcelo Tosatti
>
> Index: vsyscall/include/linux/sched.h
> ===
> --- vsyscall.orig/in
40 matches
Mail list logo
