>> Why 64-bit math here, but 128 bit math in the region_add path?
>
> Hm. Good question. It has been copied from the common VFIO code where it was
since 7532d3cbf1, back those days I did not even think of VFIO devices
hot(un)plugging
so
> region_del() was never executed so this seems to be a bug there and here.
Yet another patch is coming then
There are other things that aren't nearly as troublesome but it certainly
feels like another round of patches are forthcoming.
I didn't get a feeling from the patchset that this was functional, no
Tested-by: or Acked-by: either.
On Thu, May 12, 2016 at 1:11 PM, Serge Hallyn <email address hidden>
wrote:
I'd say we should hold off:
http:// lists.nongnu. org/archive/ html/qemu- devel/2016- 04/msg03092. html
Includes this bit:
>> Why 64-bit math here, but 128 bit math in the region_add path?
>
> Hm. Good question. It has been copied from the common VFIO code where it was
since 7532d3cbf1, back those days I did not even think of VFIO devices
hot(un)plugging
so
> region_del() was never executed so this seems to be a bug there and here.
Yet another patch is coming then
There are other things that aren't nearly as troublesome but it certainly
feels like another round of patches are forthcoming.
I didn't get a feeling from the patchset that this was functional, no
Tested-by: or Acked-by: either.
On Thu, May 12, 2016 at 1:11 PM, Serge Hallyn <email address hidden>
wrote:
> (Make that @raharper ^ ) /bugs.launchpad .net/bugs/ 1541902 /bugs.launchpad .net/ubuntu/ +source/ qemu/+bug/ 1541902/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu
> KVM
>
> To manage notifications about this bug go to:
> https:/
>