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
| ||
|
Date: Fri, 15 Jul 2022 13:32:06 -0600 From: Peter Gonda <pgonda@...gle.com> To: Sean Christopherson <seanjc@...gle.com> Cc: Paolo Bonzini <pbonzini@...hat.com>, Marc Zyngier <maz@...nel.org>, Anup Patel <anup@...infault.org>, Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>, Christian Borntraeger <borntraeger@...ux.ibm.com>, Janosch Frank <frankja@...ux.ibm.com>, Claudio Imbrenda <imbrenda@...ux.ibm.com>, James Morse <james.morse@....com>, Alexandru Elisei <alexandru.elisei@....com>, Suzuki K Poulose <suzuki.poulose@....com>, Atish Patra <atishp@...shpatra.org>, David Hildenbrand <david@...hat.com>, kvm list <kvm@...r.kernel.org>, linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu, kvm-riscv@...ts.infradead.org, linux-riscv@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>, Colton Lewis <coltonlewis@...gle.com>, Andrew Jones <drjones@...hat.com> Subject: Re: [PATCH 0/3] KVM: selftests: Consolidate ucall code On Tue, Jun 21, 2022 at 8:55 AM Sean Christopherson <seanjc@...gle.com> wrote: > > On Mon, Jun 20, 2022, Paolo Bonzini wrote: > > On 6/18/22 02:16, Sean Christopherson wrote: > > > Consolidate the code for making and getting ucalls. All architectures pass > > > the ucall struct via memory, so filling and copying the struct is 100% > > > generic. The only per-arch code is sending and receiving the address of > > > said struct. > > > > > > Tested on x86 and arm, compile tested on s390 and RISC-V. > > > > I'm not sure about doing this yet. The SEV tests added multiple > > implementations of the ucalls in one architecture. I have rebased those > > recently (not the SEV part) to get more familiar with the new kvm_vcpu API > > for selftests, and was going to look at your old review next... > > I had forgotten about that code. My idea of a per-VM list[*] would fit nicely on > top, though maybe drop the last patch from this series. > > [*] https://lore.kernel.org/all/Yc4gcJdhxthBKUUd@google.com I just sent an RFC of SEV selftesting using Sean's suggestion built on the first 2 patches in this series. I think they work well with the encrypted VMs ucalling. https://lore.kernel.org/all/20220715192956.1873315-1-pgonda@google.com/
Powered by blists - more mailing lists