[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19bba1a0-8fb7-2aae-a65a-1111e29b92d3@redhat.com>
Date: Mon, 20 Jun 2022 14:03:58 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.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>
Cc: 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@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
kvm-riscv@...ts.infradead.org, linux-riscv@...ts.infradead.org,
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 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...
Paolo
Powered by blists - more mailing lists