From: Jim Mattson <jmattson@google.com>
To: "Graf (AWS), Alexander" <graf@amazon.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Joerg Roedel <joro@8bytes.org>,
"Raslan, KarimAllah" <karahmed@amazon.de>,
Aaron Lewis <aaronlewis@google.com>,
kvm list <kvm@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] Allow user space to restrict and augment MSR emulation
Date: Wed, 19 Aug 2020 15:09:04 -0700 [thread overview]
Message-ID: <CALMp9eS5+mV2SC-v4gusocrWtXpm-QzGoOTDGhFS9NEmuVNTDw@mail.gmail.com> (raw)
In-Reply-To: <B0FD5408-E2C1-444C-AFCE-7C622EA75F66@amazon.de>
On Wed, Aug 19, 2020 at 2:46 PM Graf (AWS), Alexander <graf@amazon.de> wrote:
> Special MSRs like EFER also irritate me a bit. We can't really trap on them - most code paths just know they're handled in kernel. Maybe I'll add some sanity checks as well...
Why can't we intercept EFER?
next prev parent reply other threads:[~2020-08-19 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 21:14 [PATCH v4 0/3] Allow user space to restrict and augment MSR emulation Alexander Graf
2020-08-03 21:14 ` [PATCH v4 1/3] KVM: x86: Deflect unknown MSR accesses to user space Alexander Graf
2020-08-03 21:14 ` [PATCH v4 2/3] KVM: x86: Introduce allow list for MSR emulation Alexander Graf
2020-08-19 22:49 ` Jim Mattson
2020-09-01 19:52 ` Alexander Graf
2020-08-03 21:14 ` [PATCH v4 3/3] KVM: selftests: Add test for user space MSR handling Alexander Graf
2020-08-19 21:25 ` [PATCH v4 0/3] Allow user space to restrict and augment MSR emulation Jim Mattson
2020-08-19 21:46 ` Graf (AWS), Alexander
2020-08-19 22:09 ` Jim Mattson [this message]
2020-08-20 2:47 ` Jim Mattson
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=CALMp9eS5+mV2SC-v4gusocrWtXpm-QzGoOTDGhFS9NEmuVNTDw@mail.gmail.com \
--to=jmattson@google.com \
--cc=aaronlewis@google.com \
--cc=corbet@lwn.net \
--cc=graf@amazon.de \
--cc=joro@8bytes.org \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).