All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH] kvm-amd: Auto-load on CPUs with SVM.
Date: Thu, 29 Mar 2012 10:33:25 +0400	[thread overview]
Message-ID: <4F740235.7090508@msgid.tls.msk.ru> (raw)
In-Reply-To: <20120328183228.GA24889@leaf>

On 28.03.2012 22:32, Josh Triplett wrote:
> Enable x86 feature-based autoloading for the kvm-amd module on CPUs
> with X86_FEATURE_SVM.
> 
> Signed-off-by: Josh Triplett <josh@joshtriplett.org>

It appears to work fine on my amd boxen.  The only problem
is that I've no idea when it will be possible to finally
disable the init script (shipped in Debian and other distros)
to load the module based on /proc/cpuinfo contents.  It will
do nothing on kernels with this (or kvm-intel) change applied,
but we still need to support older kernels without that feature... :)

Josh, and I'm sure you will be the first who'll file a bugreport
against qemu-kvm in Debian requesting the startup script to be
removed!.. ;))

Thanks,

/mjt

  reply	other threads:[~2012-03-29  6:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21  6:33 [PATCH] kvm-intel: Auto-load on CPUs with VMX Josh Triplett
2012-03-21 13:41 ` Avi Kivity
2012-03-27 12:25   ` Kay Sievers
2012-03-28 11:26 ` Avi Kivity
2012-03-28 18:32   ` [PATCH] kvm-amd: Auto-load on CPUs with SVM Josh Triplett
2012-03-29  6:33     ` Michael Tokarev [this message]
2012-03-29  7:03       ` Josh Triplett
2012-04-12  1:15     ` Marcelo Tosatti

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=4F740235.7090508@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=avi@redhat.com \
    --cc=hpa@zytor.com \
    --cc=josh@joshtriplett.org \
    --cc=kay.sievers@vrfy.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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.