From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Marc Zyngier <maz@kernel.org>, Anup Patel <anup@brainfault.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org,
Colton Lewis <coltonlewis@google.com>,
kvm-riscv@lists.infradead.org,
Atish Patra <atishp@atishpatra.org>,
linux-riscv@lists.infradead.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] KVM: selftests: Consolidate ucall code
Date: Mon, 20 Jun 2022 14:03:58 +0200 [thread overview]
Message-ID: <19bba1a0-8fb7-2aae-a65a-1111e29b92d3@redhat.com> (raw)
In-Reply-To: <20220618001618.1840806-1-seanjc@google.com>
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
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Marc Zyngier <maz@kernel.org>, Anup Patel <anup@brainfault.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Atish Patra <atishp@atishpatra.org>,
David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Colton Lewis <coltonlewis@google.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH 0/3] KVM: selftests: Consolidate ucall code
Date: Mon, 20 Jun 2022 14:03:58 +0200 [thread overview]
Message-ID: <19bba1a0-8fb7-2aae-a65a-1111e29b92d3@redhat.com> (raw)
In-Reply-To: <20220618001618.1840806-1-seanjc@google.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Marc Zyngier <maz@kernel.org>, Anup Patel <anup@brainfault.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Atish Patra <atishp@atishpatra.org>,
David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Colton Lewis <coltonlewis@google.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH 0/3] KVM: selftests: Consolidate ucall code
Date: Mon, 20 Jun 2022 14:03:58 +0200 [thread overview]
Message-ID: <19bba1a0-8fb7-2aae-a65a-1111e29b92d3@redhat.com> (raw)
In-Reply-To: <20220618001618.1840806-1-seanjc@google.com>
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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Marc Zyngier <maz@kernel.org>, Anup Patel <anup@brainfault.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Atish Patra <atishp@atishpatra.org>,
David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Colton Lewis <coltonlewis@google.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH 0/3] KVM: selftests: Consolidate ucall code
Date: Mon, 20 Jun 2022 14:03:58 +0200 [thread overview]
Message-ID: <19bba1a0-8fb7-2aae-a65a-1111e29b92d3@redhat.com> (raw)
In-Reply-To: <20220618001618.1840806-1-seanjc@google.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-20 12:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 0:16 [PATCH 0/3] KVM: selftests: Consolidate ucall code Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` [PATCH 1/3] KVM: selftests: Consolidate common code for popuplating ucall struct Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-20 7:39 ` Christian Borntraeger
2022-06-20 7:39 ` Christian Borntraeger
2022-06-20 7:39 ` Christian Borntraeger
2022-06-20 7:39 ` Christian Borntraeger
2022-06-18 0:16 ` [PATCH 2/3] KVM: selftests: Consolidate boilerplate code in get_ucall() Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-19 10:36 ` Huang, Shaoqin
2022-06-19 10:36 ` Huang, Shaoqin
2022-06-19 10:36 ` Huang, Shaoqin
2022-06-19 10:36 ` Huang, Shaoqin
2022-06-21 14:41 ` Sean Christopherson
2022-06-21 14:41 ` Sean Christopherson
2022-06-21 14:41 ` Sean Christopherson
2022-06-21 14:41 ` Sean Christopherson
2022-06-18 0:16 ` [PATCH 3/3] KVM: selftest: Add __weak stubs for ucall_arch_(un)init() Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-18 0:16 ` Sean Christopherson
2022-06-20 7:33 ` [PATCH 0/3] KVM: selftests: Consolidate ucall code Andrew Jones
2022-06-20 7:33 ` Andrew Jones
2022-06-20 7:33 ` Andrew Jones
2022-06-20 7:33 ` Andrew Jones
2022-06-20 12:03 ` Paolo Bonzini [this message]
2022-06-20 12:03 ` Paolo Bonzini
2022-06-20 12:03 ` Paolo Bonzini
2022-06-20 12:03 ` Paolo Bonzini
2022-06-21 14:54 ` Sean Christopherson
2022-06-21 14:54 ` Sean Christopherson
2022-06-21 14:54 ` Sean Christopherson
2022-06-21 14:54 ` Sean Christopherson
2022-07-15 19:32 ` Peter Gonda
2022-07-15 19:32 ` Peter Gonda
2022-07-15 19:32 ` Peter Gonda
2022-07-15 19:32 ` Peter Gonda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19bba1a0-8fb7-2aae-a65a-1111e29b92d3@redhat.com \
--to=pbonzini@redhat.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=borntraeger@linux.ibm.com \
--cc=coltonlewis@google.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.