Re: [PATCH 2/3] drm/i915/gvt: make gvt oblivious of kvmgt data structures

2020-01-09 Thread Jani Nikula
On Wed, 08 Jan 2020, Julian Stecklina wrote: > On Wed, 2020-01-08 at 12:24 +0200, Jani Nikula wrote: >> On Mon, 06 Jan 2020, Julian Stecklina >> >> wrote: > [...] >> > + /* Hypervisor-specific device state. */ >> > + void *vdev; >> >> I have no clue about the relative merits of the patch, bu

Re: [PATCH 2/3] drm/i915/gvt: make gvt oblivious of kvmgt data structures

2020-01-08 Thread Julian Stecklina
On Wed, 2020-01-08 at 12:24 +0200, Jani Nikula wrote: > On Mon, 06 Jan 2020, Julian Stecklina > wrote: [...] > > + /* Hypervisor-specific device state. */ > > + void *vdev; > > I have no clue about the relative merits of the patch, but you can use > the actual type for the pointer with a forw

Re: [PATCH 2/3] drm/i915/gvt: make gvt oblivious of kvmgt data structures

2020-01-08 Thread Jani Nikula
On Mon, 06 Jan 2020, Julian Stecklina wrote: > Instead of defining KVMGT per-device state in struct intel_vgpu > directly, add an indirection. This makes the GVT code oblivious of > what state KVMGT needs to keep. > > The intention here is to eventually make it possible to build > hypervisor back

[PATCH 2/3] drm/i915/gvt: make gvt oblivious of kvmgt data structures

2020-01-06 Thread Julian Stecklina
Instead of defining KVMGT per-device state in struct intel_vgpu directly, add an indirection. This makes the GVT code oblivious of what state KVMGT needs to keep. The intention here is to eventually make it possible to build hypervisor backends for the mediator, without having to touch the mediato