From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: David Windsor <dwindsor@gmail.com>, kvm@vger.kernel.org
Subject: Re: [RFC] allow userspace to set MSR no-ops
Date: Wed, 04 Nov 2009 11:10:29 +0200 [thread overview]
Message-ID: <4AF14505.3030503@redhat.com> (raw)
In-Reply-To: <20091103151203.GA10990@amt.cnet>
On 11/03/2009 05:12 PM, Marcelo Tosatti wrote:
> On Wed, Oct 28, 2009 at 01:23:07PM -0400, David Windsor wrote:
>
>> Hi,
>>
>> I've encountered a situation in which I would like to allow userspace
>> to set the MSRs which KVM should not emulate and instead implement
>> these as no-ops.
>>
>> I have not seen any work in this space, furthermore there is an item
>> on the KVM TODO that is very similar to what I'm trying to do.
>>
>> The userspace interface is an extension of kvm_vcpu_ioctl, adding the
>> KVM_SET_MSRS_NOOP flag. It takes a struct kvm_msrs as a list of which
>> MSRs should be no-ops and adds the field noop to struct kvm_msr_entry.
>> This patch only affects vmx, but if the approach is sane, I can
>> extend it to support svm as well.
>>
> Does the ignore_msrs kvm.ko parameter achieve what you want?
>
>
Ah, I forgot all about that.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-04 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 17:23 [RFC] allow userspace to set MSR no-ops David Windsor
2009-10-28 18:31 ` Richard Winthers
[not found] ` <944f46790910281128j345c13adre8d0dc533bc4abb1@mail.gmail.com>
2009-10-28 21:04 ` David Windsor
2009-11-03 15:12 ` Marcelo Tosatti
2009-11-04 9:10 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-28 18:06 David Windsor
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=4AF14505.3030503@redhat.com \
--to=avi@redhat.com \
--cc=dwindsor@gmail.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.