On Wed, Nov 13, 2013 at 06:46:47PM +0100, Paolo Bonzini wrote:
The whitespace in this patch is corrupted. For this time I applied it;
next time however please use "git send-email".
Ok, I'll use it.
Thank you !
Anthoine
1
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
t
On Wed, Nov 13, 2013 at 10:22:54PM -0500, Binh Q. Pham wrote:
> Hi Gleb,
> Thanks for the suggestion, but I just tried to specify the cpu type
> to QEMU: -cpu host and I got the same output.
>
Which QEMU version are you using, what is the output of "cat
/proc/cpuinfo" in the guest and attach guest
Am 14.11.2013 00:09, schrieb Peter Maydell:
> Fix build failures with clang when KVM is not enabled by
> providing a stub version of kvm_arch_get_supported_cpuid().
> We retain the compile time check that this function isn't
> called when CONFIG_KVM is not set by guarding the stub with
> ifndef __O
Hi Marcelo,
On 11/14/2013 08:36 AM, Marcelo Tosatti wrote:
>
> Any code location which reads the writable bit in the spte and assumes if its
> not
> set, that the translation which the spte refers to is not cached in a
> remote CPU's TLB can become buggy. (*)
>
> It might be the case that now
Hi Gleb,
Thanks for the suggestion, but I just tried to specify the cpu type to
QEMU: -cpu host and I got the same output.
Binh
On 11/13/2013 12:54 PM, Gleb Natapov wrote:
On Wed, Nov 13, 2013 at 11:52:01AM -0500, Binh Q. Pham wrote:
Hi all,
I just started using kvm and want to use linux 'pe
On Wed, Oct 23, 2013 at 09:29:22PM +0800, Xiao Guangrong wrote:
> Now we can flush all the TLBs out of the mmu lock without TLB corruption when
> write-proect the sptes, it is because:
> - we have marked large sptes readonly instead of dropping them that means we
> just change the spte from writa
Fix build failures with clang when KVM is not enabled by
providing a stub version of kvm_arch_get_supported_cpuid().
We retain the compile time check that this function isn't
called when CONFIG_KVM is not set by guarding the stub with
ifndef __OPTIMIZE__ (we assume that an optimizing build will
do
On 13 November 2013 07:25, Paolo Bonzini wrote:
> Il 13/11/2013 03:27, Richard Henderson ha scritto:
>> I think it's also worthwhile to implement the kvm api in kvm-stub.c,
>> unnecessary or not. If you really want compile-time feedback on those that
>> ought to have been removed by optimization,
https://bugzilla.kernel.org/show_bug.cgi?id=55711
Alan changed:
What|Removed |Added
CC||a...@lxorguk.ukuu.org.uk
Component|ARM
https://bugzilla.kernel.org/show_bug.cgi?id=58921
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=58941
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=58941
Alan changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=58921
Alan changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=60629
Alan changed:
What|Removed |Added
CC||a...@lxorguk.ukuu.org.uk
--- Comment #1 from Alan
On Wed, Nov 13, 2013 at 11:52:01AM -0500, Binh Q. Pham wrote:
> Hi all,
>
> I just started using kvm and want to use linux 'perf' tool inside
> the virtual machine to get some information about the hardware
> performance counters. I noticed in kvm source, there is pmu.c and
> pmu-stubs.c, so I ass
Il 13/11/2013 11:45, Anthoine Bourgeois ha scritto:
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 2b2fce1..e33cadf 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -6627,6 +6627,9 @@ static bool nested_vmx_exit_handled(struct
> kvm_vcpu *vcpu)
> ret
Hi all,
I just started using kvm and want to use linux 'perf' tool inside the
virtual machine to get some information about the hardware performance
counters. I noticed in kvm source, there is pmu.c and pmu-stubs.c, so I
assume they provide support for PMU. However, when I ran 'perf stat' in
https://bugzilla.kernel.org/show_bug.cgi?id=60652
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=60652
Alan changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=60833
Alan changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=60833
Alan changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
hi Freddie,
Am 12.11.2013 um 19:19 schrieb Freddie Cash :
>
> AFAIK, the limit for virtio network devices (using vhost-net kernel module)
> is "as fast as the CPU can pump data through the PCIe bus to the NIC".
> Meaning, the NIC is the bottleneck, not the virtio device.
that was, what I wa
If a nested guest does a NM fault but its CR0 doesn't contain the TS
flag (because it was already cleared by the guest with L1 aid) then we
have to activate FPU ourselves in L0 and then continue to L2. If TS flag
is set then we fallback on the previous behavior, forward the fault to
L1 if it asked
13.11.2013 11:48, Gleb Natapov пишет:
resulted command line is
0:18 /usr/libexec/qemu-kvm -name lubsan -S -M rhel6.4.0 -cpu
Penryn,+osxsave,+xsave,+dca,+pdcm,+xtpr,+tm2,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
-no-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -uuid
Why no-
24 matches
Mail list logo
