From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: Gleb Natapov <gleb@kernel.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] KVM: nVMX: Fully emulate preemption timer
Date: Fri, 07 Mar 2014 18:24:26 +0100 [thread overview]
Message-ID: <531A00CA.80504@redhat.com> (raw)
In-Reply-To: <20140307172035.GA30738@amt.cnet>
Il 07/03/2014 18:20, Marcelo Tosatti ha scritto:
> On Thu, Mar 06, 2014 at 06:33:58PM +0100, Jan Kiszka wrote:
>> > We cannot rely on the hardware-provided preemption timer support because
>> > we are holding L2 in HLT outside non-root mode.
>> > Furthermore, emulating
>> > the preemption will resolve tick rate errata on older Intel CPUs.
> Can you describe this in more detail please? Errata number?
AAT59 and AAK139. Basically the rate of the preemption timer is wrong
and unpredictable.
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5500-specification-update.pdf
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/core-mobile-spec-update.pdf
Paolo
next prev parent reply other threads:[~2014-03-07 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:33 [PATCH v3 0/3] KVM: x86: Pending nVMX fixes Jan Kiszka
2014-03-06 17:33 ` [PATCH v3 1/3] KVM: nVMX: Rework interception of IRQs and NMIs Jan Kiszka
2014-03-07 15:44 ` Paolo Bonzini
2014-03-07 16:29 ` Jan Kiszka
2014-03-07 16:46 ` Paolo Bonzini
2014-03-07 17:28 ` Jan Kiszka
2014-03-07 18:19 ` Jan Kiszka
2014-03-07 18:24 ` Paolo Bonzini
2014-03-07 18:26 ` Jan Kiszka
2014-03-07 19:45 ` Paolo Bonzini
2014-03-06 17:33 ` [PATCH v3 2/3] KVM: nVMX: Fully emulate preemption timer Jan Kiszka
2014-03-07 17:20 ` Marcelo Tosatti
2014-03-07 17:24 ` Paolo Bonzini [this message]
2014-03-06 17:33 ` [PATCH v3 3/3] KVM: nVMX: Do not inject NMI vmexits when L2 has a pending interrupt Jan Kiszka
2014-03-06 17:41 ` [PATCH v3 0/3] KVM: x86: Pending nVMX fixes 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=531A00CA.80504@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.