Re: qemu/kvm has limited pci config space exposed to guest device driver to access

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alex, thanks.

Yes, I'm talking about the pci device assignment. What about the vfio
performance, close to the pci pass-through performance?

Currently I'm trying to understand what's the behind thinking about
the limited config space, security or sth else?

Thx, Xuekun

On Fri, Dec 13, 2013 at 10:55 AM, Alex Williamson
<alex.williamson@xxxxxxxxxx> wrote:
> On Fri, 2013-12-13 at 10:34 +0800, Xuekun Hu wrote:
>> Hi, All
>>
>> I found qemu/kvm has limited pci config space exposed to guest device
>> driver to access. I’m wondering is there any reason why not expose the
>> whole pci config space to guest, since some kind of devices has
>> special register in that area.
>
> If you're talking about device assignment, vfio allows access to all of
> config space.  Legacy KVM device assignment is deprecated.  Thanks,
>
> Alex
>
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux