Hi,
> > Unfortunately it's not the only one. Another example is, device-model
> > may want to write-protect a gfn (RAM). In case that this request goes
> > to VFIO .. how it is supposed to reach KVM MMU?
>
> Well, let's work through the problem. How is the GFN related to the
> device? Is this some sort of page table for device mappings with a base
> register in the vgpu hardware?
IIRC this is needed to make sure the guest can't bypass execbuffer
verification and works like this:
(1) guest submits execbuffer.
(2) host makes execbuffer readonly for the guest
(3) verify the buffer (make sure it only accesses resources owned by
the vm).
(4) pass on execbuffer to the hardware.
(5) when the gpu is done with it make the execbuffer writable again.
cheers,
Gerd
--
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
