From: Paolo Bonzini <pbonzini@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] KVM: SVM: fix trashing of MSR_TSC_AUX
Date: Wed, 6 Jul 2016 16:29:35 +0200 [thread overview]
Message-ID: <361b792f-87ce-863d-5098-9a18aadd6379@redhat.com> (raw)
In-Reply-To: <20160706141847.GF7300@pd.tnic>
On 06/07/2016 16:18, Borislav Petkov wrote:
> Something's still missing. I have a small program which does RDTSCP in
> the guest:
>
> $ taskset -c 3 ./rdtscp
> aux1: 0x0
> aux2: 0x0
> p1: 195514968442, p2: 195515255582, 287140
>
> and the aux things which are %ecx, are 0 (should be 3 in that case).
Ok, I'll take a look at it tomorrow.
Can you test this in the meanwhile:
git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
cd kvm-unit-tests
./configure
make
./x86/run x86/tsc.flat -cpu kvm64,+rdtscp
On Intel I see:
enabling apic
rdtsc latency 18
rdtsc after wrtsc(0): 727124155
rdtsc after wrtsc(100000000000): 100000001759
PASS: Test RDTSCP 0
PASS: Test RDTSCP 10
PASS: Test RDTSCP 256
SUMMARY: 3 tests
> It did work with my patch with the RDTSCP intercept:
>
> $ taskset -c 3 ./rdtscp
> aux1: 0x3
> aux2: 0x3
> p1: 157117003683, p2: 157119280794, 2277111
>
> Btw, just for my own understanding: if we don't intercept RDTSCP, does
> it get emulated? Where does the TSC value come from, qemu?
It comes from the processor's TSC + the TSC offset field in the VMCB.
Paolo
>
> Here's the program.
>
> ---
>
> #include <stdio.h>
> #include <stdlib.h>
> #include <unistd.h>
>
> typedef unsigned long long u64;
>
> #define DECLARE_ARGS(val, low, high) unsigned low, high
> #define EAX_EDX_VAL(val, low, high) ((low) | ((u64)(high) << 32))
> #define EAX_EDX_ARGS(val, low, high) "a" (low), "d" (high)
> #define EAX_EDX_RET(val, low, high) "=a" (low), "=d" (high)
>
> static __always_inline unsigned long long rdtscp(unsigned int *aux)
> {
> unsigned int lo, hi;
>
> asm volatile("rdtscp" : "=a" (lo), "=d" (hi), "=c" (*aux));
>
> return EAX_EDX_VAL(0, lo, hi);
> }
>
> int main()
> {
> unsigned long long p1, p2;
> unsigned int aux;
>
> p1 = rdtscp(&aux);
> printf("aux1: 0x%x\n", aux);
> p2 = rdtscp(&aux);
> printf("aux2: 0x%x\n", aux);
>
> printf("p1: %llu, p2: %llu, %lld\n", p1, p2, p2 - p1);
>
> return 0;
> }
>
next prev parent reply other threads:[~2016-07-06 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 13:43 [PATCH] KVM: SVM: fix trashing of MSR_TSC_AUX Paolo Bonzini
2016-07-06 14:18 ` Borislav Petkov
2016-07-06 14:29 ` Paolo Bonzini [this message]
2016-07-07 10:41 ` Borislav Petkov
2016-07-07 11:01 ` Paolo Bonzini
2016-07-07 11:47 ` Borislav Petkov
2016-07-07 12:28 ` Paolo Bonzini
2016-07-07 12:47 ` Borislav Petkov
2016-07-07 13:16 ` Paolo Bonzini
2016-07-07 16:01 ` Borislav Petkov
2016-07-07 16:17 ` Paolo Bonzini
2016-07-07 16:27 ` Eduardo Habkost
2016-07-07 17:04 ` Borislav Petkov
2016-07-07 17:43 ` Eduardo Habkost
2016-07-08 11:09 ` Borislav Petkov
2016-07-08 11:15 ` Paolo Bonzini
2016-07-08 12:55 ` Borislav Petkov
2016-07-06 15:00 ` kbuild test robot
2016-07-15 12:15 ` Radim Krčmář
2016-07-15 12:30 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=361b792f-87ce-863d-5098-9a18aadd6379@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox