linux-kernel - Re: [RFC PATCH 1/2] KVM: x86: Introduce KVM_{G, S}ET_ONE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b4829ed2-5a34-4b5c-8770-3571a9381b19@amazon.de>
Date: Wed, 11 Sep 2024 16:48:07 +0200
From: Nikolas Wipper <nikwip@...zon.de>
To: Sean Christopherson <seanjc@...gle.com>
CC: Yang Weijiang <weijiang.yang@...el.com>, <pbonzini@...hat.com>,
	<mlevitsk@...hat.com>, <kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 1/2] KVM: x86: Introduce KVM_{G, S}ET_ONE_REG uAPIs support

On Wed Sep 11, 2024 at 04:36 PM UTC+0200, Sean Christopherson wrote:
> On Wed, Sep 11, 2024, Nikolas Wipper wrote:
>> Having this API, and specifically having a definite kvm_one_reg structure
>> for x86 registers, would be interesting for register pinning/intercepts.
>> With one_reg for x86 the API could be platform agnostic and possible even
>> replace MSR filters for x86.
> 
> I don't follow.  MSR filters let userspace intercept accesses for a variety of
> reasons, these APIs simply provide a way to read/write a register value that is
> stored in KVM.  I don't see how this could replace MSR filters.

Nope, that would be an entirely different API, but if that uses one reg IDs it
could be unified to cover CRs and MSRs all in one.




Amazon Web Services Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597