Re: [PATCH v4 0/6] VFIO mdev aggregated resources handling

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

 



On 2018.11.27 14:44:30 +1100, Alexey Kardashevskiy wrote:
> >> On 26/11/2018 19:48, Zhenyu Wang wrote:
> >>> Hi,
> >>>
> >>> This is respin of previous sending from https://www.spinics.net/lists/kvm/msg176447.html
> >>>
> >>> Current mdev device create interface depends on fixed mdev type, which get uuid
> >>> from user to create instance of mdev device. If user wants to use customized
> >>> number of resource for mdev device, then only can create new mdev type for that
> >>
> >> I have a dumb question - what is the resource in this context? Usually
> >> it would be something like a PCI BAR but here it yet another virtual GPU
> >> instance? Thanks.
> >>
> > 
> > It's device specific defined by mdev type for each instance, e.g for
> > current virtual GPU, it's like GPU mem.
> 
> What does aggregate=10 mean for a vGPU? 10 frame buffers? 10 of what? :)

It's applied to GPU mem for KVMGT in this series, e.g applies to 10x
memory size defined by mdev type. For current free formatted mdev type
"description", no formal way to get exact info. I'm not sure if we
want some keyword, or "aggregation" attribute reading should return
exact type of resource for aggregation along with maxium count as
indicator?

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

Attachment: signature.asc
Description: PGP signature


[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