Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>, KVM list <kvm@vger.kernel.org>
Subject: Re: Should KVM_GUEST stop depending on PARAVIRT?
Date: Mon, 27 Jul 2015 15:59:15 +0200	[thread overview]
Message-ID: <55B63933.4090702@redhat.com> (raw)
In-Reply-To: <CALCETrUWZn4vdTOjo5yB5+6Xx3-s4wrDbKeVSCnB0TBe_AUd=g@mail.gmail.com>



On 24/07/2015 19:33, Andy Lutomirski wrote:
> PARAVIRT adds a fair amount of bloat and, AFAICT, KVM_GUEST doesn't
> really need any of it.  Would it make sense to drop the dependency?

I think the main reason for PARAVIRT is that pv kernels have by default

        .read_msr = native_read_msr_safe,
        .write_msr = native_write_msr_safe,

Unfortunately Intel adds a bunch of performance measurement features
saying that "they work with this cpuid family/model/stepping" and at the
same time attach them to some non-architectural MSRs that, in principle
could be reused for something else years down the road.  This is not a
huge problem for Windows, where only tools such as vTune use these MSRs,
but it is a problem for Linux.

The alternative is ignore_msrs, but that's a very big hammer too.

Paolo

  reply	other threads:[~2015-07-27 13:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 17:33 Should KVM_GUEST stop depending on PARAVIRT? Andy Lutomirski
2015-07-27 13:59 ` Paolo Bonzini [this message]
2015-07-27 15:56   ` Andy Lutomirski
2015-07-27 17:49     ` Paolo Bonzini
2015-07-27 17:51       ` Andy Lutomirski
2015-07-27 18:30         ` Paolo Bonzini
2015-07-27 18:45           ` Andy Lutomirski
2015-07-27 19:04             ` Arjan van de Ven
2015-07-28  9:57             ` Paolo Bonzini
2015-07-29  0:23               ` Andy Lutomirski
2015-07-29  4:49                 ` Venkatesh Srinivas
2015-07-29  8:27                   ` Paolo Bonzini
2015-07-29  9:19                 ` Peter Zijlstra
2015-07-29  9:24                   ` Paolo Bonzini
2015-07-29  9:40                     ` Peter Zijlstra
2015-07-29  9:41                       ` Paolo Bonzini
2015-07-30  0:14                         ` Andy Lutomirski

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=55B63933.4090702@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=luto@amacapital.net \
    /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