Re: [PATCH v4 0/3] Allow user space to restrict and augment MSR emulation

On Wed, Aug 19, 2020 at 3:09 PM Jim Mattson wrote: > > On Wed, Aug 19, 2020 at 2:46 PM Graf (AWS), Alexander 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

Re: [PATCH v4 0/3] Allow user space to restrict and augment MSR emulation

On Wed, Aug 19, 2020 at 2:46 PM Graf (AWS), Alexander 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?

Re: [PATCH v4 0/3] Allow user space to restrict and augment MSR emulation

> Am 19.08.2020 um 23:27 schrieb Jim Mattson : > >> On Mon, Aug 3, 2020 at 2:14 PM Alexander Graf wrote: >> >> While tying to add support for the MSR_CORE_THREAD_COUNT MSR in KVM, >> I realized that we were still in a world where user space has no control >> over what happens with MSR emulati

Re: [PATCH v4 0/3] Allow user space to restrict and augment MSR emulation

On Mon, Aug 3, 2020 at 2:14 PM Alexander Graf wrote: > > While tying to add support for the MSR_CORE_THREAD_COUNT MSR in KVM, > I realized that we were still in a world where user space has no control > over what happens with MSR emulation in KVM. > > That is bad for multiple reasons. In my case,