On 12/01/2016 11:44, Knut Omang wrote:
> On Fri, 2016-01-01 at 23:37 +0100, Paolo Bonzini wrote:
>>
>> On 31/12/2015 19:13, Ilya Lesokhin wrote:
>>> I was able to overcome this issue by calling object_unparent on my
>>> device but I’m not sure that the correct way of fixing it.
>>
>> Yes, it's de
On Fri, 2016-01-01 at 23:37 +0100, Paolo Bonzini wrote:
>
> On 31/12/2015 19:13, Ilya Lesokhin wrote:
> > I was able to overcome this issue by calling object_unparent on my
> > device but I’m not sure that the correct way of fixing it.
>
> Yes, it's definitely the right way to fix it.
Sorry for
On 31/12/2015 19:13, Ilya Lesokhin wrote:
> I was able to overcome this issue by calling object_unparent on my
> device but I’m not sure that the correct way of fixing it.
Yes, it's definitely the right way to fix it.
Paolo
Hi,
I’m working on SRIOV support for VFIO and I’m suffering from a reference leak.
I’m using Knut Omang’s patches for SRIOV[1].
When the VF’s are enabled I call
pci_create(…) and then object_property_set_bool(OBJECT(&dev->qdev), true,
"realized", &local_err);
and when the VF’s are disabled I call
