[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <173948e8-4c7a-6dc4-de17-99151bc56d91@amazon.com>
Date: Wed, 29 Jul 2020 11:09:26 +0200
From: Alexander Graf <graf@...zon.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>,
Jim Mattson <jmattson@...gle.com>
CC: Paolo Bonzini <pbonzini@...hat.com>,
Jonathan Corbet <corbet@....net>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Wanpeng Li <wanpengli@...cent.com>,
Joerg Roedel <joro@...tes.org>, kvm list <kvm@...r.kernel.org>,
<linux-doc@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
Aaron Lewis <aaronlewis@...gle.com>
Subject: Re: [PATCH] KVM: x86: Deflect unknown MSR accesses to user space
On 29.07.20 10:23, Vitaly Kuznetsov wrote:
>
>
>
> Jim Mattson <jmattson@...gle.com> writes:
>
>> On Tue, Jul 28, 2020 at 5:41 AM Alexander Graf <graf@...zon.com> wrote:
>>>
>
> ...
>
>>> While it does feel a bit overengineered, it would solve the problem that
>>> we're turning in-KVM handled MSRs into an ABI.
>>
>> It seems unlikely that userspace is going to know what to do with a
>> large number of MSRs. I suspect that a small enumerated list will
>> suffice.
>
> The list can also be 'wildcarded', i.e.
> {
> u32 index;
> u32 mask;
> ...
> }
>
> to make it really short.
I like the idea of wildcards, but I can't quite wrap my head around how
we would implement ignore_msrs in user space with them?
Alex
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
Powered by blists - more mailing lists