From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
pbonzini@redhat.com, Wei Wang <wei.w.wang@intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2] KVM: move KVM_CAP_DEVICE_CTRL to the generic check
Date: Thu, 30 Nov 2023 17:52:08 -0800 [thread overview]
Message-ID: <170137868908.667071.11420459240927661184.b4-ty@google.com> (raw)
In-Reply-To: <20230315101606.10636-1-wei.w.wang@intel.com>
On Wed, 15 Mar 2023 18:16:06 +0800, Wei Wang wrote:
> KVM_CAP_DEVICE_CTRL allows userspace to check if the kvm_device
> framework (e.g. KVM_CREATE_DEVICE) is supported by KVM. Move
> KVM_CAP_DEVICE_CTRL to the generic check for the two reasons:
> 1) it already supports arch agnostic usages (i.e. KVM_DEV_TYPE_VFIO).
> For example, userspace VFIO implementation may needs to create
> KVM_DEV_TYPE_VFIO on x86, riscv, or arm etc. It is simpler to have it
> checked at the generic code than at each arch's code.
> 2) KVM_CREATE_DEVICE has been added to the generic code.
>
> [...]
Applied to kvm-x86 generic, thanks!
[1/1] KVM: move KVM_CAP_DEVICE_CTRL to the generic check
https://github.com/kvm-x86/linux/commit/63912245c19d
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2023-12-01 1:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 10:16 [PATCH RESEND v2] KVM: move KVM_CAP_DEVICE_CTRL to the generic check Wei Wang
2023-06-13 21:16 ` Sean Christopherson
2023-06-13 21:16 ` Sean Christopherson
2023-06-13 21:16 ` Sean Christopherson
2023-06-13 21:16 ` Sean Christopherson
2023-06-14 12:23 ` Oliver Upton
2023-06-14 12:23 ` Oliver Upton
2023-06-14 12:23 ` Oliver Upton
2023-06-14 12:23 ` Oliver Upton
2023-06-15 3:48 ` Michael Ellerman
2023-06-15 5:49 ` Anup Patel
2023-12-01 1:52 ` Sean Christopherson [this message]
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=170137868908.667071.11420459240927661184.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wei.w.wang@intel.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.