From: Alex Williamson <alex.williamson@redhat.com>
To: Nan Xiao <xiaonan830818@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: A question about "CONFIG_KVM_DEVICE_ASSIGNMENT" configuration
Date: Thu, 10 Sep 2015 09:08:36 -0600 [thread overview]
Message-ID: <1441897716.20355.565.camel@redhat.com> (raw)
In-Reply-To: <CA+MhoaNEtdOc9+m8E5OSG93CH+swH7XdmnX902z=M8H8XD8oFw@mail.gmail.com>
On Thu, 2015-09-10 at 18:22 +0800, Nan Xiao wrote:
> Hi all,
>
> When building kernel, it prompts "CONFIG_KVM_DEVICE_ASSIGNMENT" is "deprecated".
> But it is still used in kernel code. E.g.:
> "kvm_vm_ioctl_check_extension" function:
> {
> ...
> #ifdef CONFIG_KVM_DEVICE_ASSIGNMENT
> case KVM_CAP_ASSIGN_DEV_IRQ:
> case KVM_CAP_PCI_2_3:
> #endif
> r = 1;
> break;
> ...
> #ifdef CONFIG_KVM_DEVICE_ASSIGNMENT
> case KVM_CAP_IOMMU:
> r = iommu_present(&pci_bus_type);
> break;
> #endif
> ...
> }
>
> If not configure this option, the following code will execute failed:
>
> ret = ioctl(dev, KVM_CHECK_EXTENSION, KVM_CAP_IOMMU);
>
> So does it mean to use KVM assigned device feature, the
> "CONFIG_KVM_DEVICE_ASSIGNMENT"
> is not "deprecated"?
Legacy KVM device assignment is deprecated, it is fully replaced by
VFIO-based device assignment. The intention is to deprecate legacy KVM
device assignment now, so all users can transition away from it and at
some point remove it from the kernel. When using QEMU and libvirt, the
default is already to use VFIO instead of legacy KVM device assignment.
Thanks,
Alex
next prev parent reply other threads:[~2015-09-10 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 10:22 A question about "CONFIG_KVM_DEVICE_ASSIGNMENT" configuration Nan Xiao
2015-09-10 15:08 ` Alex Williamson [this message]
2015-09-10 23:58 ` Nan Xiao
2015-09-11 0:18 ` Alex Williamson
2015-09-11 0:42 ` Nan Xiao
2015-09-11 0:55 ` Chen, Tiejun
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=1441897716.20355.565.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=xiaonan830818@gmail.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.