From: Sergey Fedorov <serge.fdrv@gmail.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: wei@redhat.com, peter.maydell@linaro.org, drjones@redhat.com,
mdroth@linux.vnet.ibm.com, libvir-list@redhat.com,
armbru@redhat.com, abologna@redhat.com, qemu-arm@nongnu.org,
christoffer.dall@linaro.org
Subject: Re: [Qemu-devel] [PATCH v7 3/4] kvm: add kvm_device_supported() helper function
Date: Thu, 24 Mar 2016 12:14:48 +0300 [thread overview]
Message-ID: <56F3B008.7050207@gmail.com> (raw)
In-Reply-To: <1458788142-17509-4-git-send-email-peterx@redhat.com>
On 24/03/16 05:55, Peter Xu wrote:
> This can be used when probing whether KVM support specific device. Here,
> a raw vmfd is used.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Acked-by: Sergey Fedorov <serge.fdrv@gmail.com>
Kind regards,
Sergey
> ---
> include/sysemu/kvm.h | 9 +++++++++
> kvm-all.c | 15 +++++++++++++++
> 2 files changed, 24 insertions(+)
>
> diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
> index 6695fa7..0e18f15 100644
> --- a/include/sysemu/kvm.h
> +++ b/include/sysemu/kvm.h
> @@ -306,6 +306,15 @@ void kvm_device_access(int fd, int group, uint64_t attr,
> */
> int kvm_create_device(KVMState *s, uint64_t type, bool test);
>
> +/**
> + * kvm_device_supported - probe whether KVM supports specific device
> + *
> + * @vmfd: The fd handler for VM
> + * @type: type of device
> + *
> + * @return: true if supported, otherwise false.
> + */
> +bool kvm_device_supported(int vmfd, uint64_t type);
>
> /* Arch specific hooks */
>
> diff --git a/kvm-all.c b/kvm-all.c
> index 44c0464..e7b66df 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -2339,6 +2339,21 @@ int kvm_create_device(KVMState *s, uint64_t type, bool test)
> return test ? 0 : create_dev.fd;
> }
>
> +bool kvm_device_supported(int vmfd, uint64_t type)
> +{
> + struct kvm_create_device create_dev = {
> + .type = type,
> + .fd = -1,
> + .flags = KVM_CREATE_DEVICE_TEST,
> + };
> +
> + if (ioctl(vmfd, KVM_CHECK_EXTENSION, KVM_CAP_DEVICE_CTRL) <= 0) {
> + return false;
> + }
> +
> + return (ioctl(vmfd, KVM_CREATE_DEVICE, &create_dev) >= 0);
> +}
> +
> int kvm_set_one_reg(CPUState *cs, uint64_t id, void *source)
> {
> struct kvm_one_reg reg;
next prev parent reply other threads:[~2016-03-24 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 2:55 [Qemu-devel] [PATCH v7 0/4] ARM: add query-gic-capabilities QMP command Peter Xu
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 1/4] arm: qmp: add query-gic-capabilities interface Peter Xu
2016-03-30 1:50 ` Eric Blake
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 2/4] arm: enhance kvm_arm_create_scratch_host_vcpu Peter Xu
2016-03-24 9:13 ` Sergey Fedorov
2016-03-29 20:04 ` Peter Maydell
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 3/4] kvm: add kvm_device_supported() helper function Peter Xu
2016-03-24 9:14 ` Sergey Fedorov [this message]
2016-03-24 2:55 ` [Qemu-devel] [PATCH v7 4/4] arm: implement query-gic-capabilities Peter Xu
2016-03-24 9:16 ` Sergey Fedorov
2016-03-29 20:10 ` [Qemu-devel] [PATCH v7 0/4] ARM: add query-gic-capabilities QMP command Peter Maydell
2016-03-30 11:20 ` Andrea Bolognani
2016-03-30 14:53 ` Peter Maydell
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=56F3B008.7050207@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).