On 1/21/25 07:26, Akihiko Odaki wrote: ... >>> I feel the dependency information for virglrenderer and Mesa are more >>> suited for the Mesa documentation as they are not specific to QEMU and >>> potentially useful also for e.g., libkrun and crosvm. >> >> I think while everything is in so much flux it doesn't hurt to include >> in our docs. I don't know if mesa currently has a dedicated page for GPU >> virtualisation. > > Mesa has pages for VirGL and Venus, which can be linked from the > respective parts of this documentation. gfxstream is not documented but > I think most people will use it only for Android anyway. A documentation > for DRM native context will be a nice addition for Mesa. I will not > object if you put this information to QEMU documentation though.
Adding native context doc to Mesa indeed will be a good move, as well as adding links to the Mesa virgl/venus pages in QEMU. RE requirements documentation, it's also a valid point that stuff like build flags should belong to the relevant projects. On the other hand, it's a common headache for a newcoming people to figure everything out from scratch and having more centralized documentation helps. The build requirements aren't cleanly documented anywhere AFAICT, and the requirements also differ based on VMM. I'll update and keep this patch in v6, the requirements info should stay actual for a next couple years IMO. Let's discuss it further in v6 if more objections will arise. -- Best regards, Dmitry
