On Mon, Aug 04, 2025 at 05:05:06PM +0100, Alex Bennée wrote: > Florian Hofhammer <florian.hofham...@epfl.ch> writes: > > > Hello, > > (Added the *-user MAINTAINERS to the CC) > > More specifically, the "vcpu_syscall_cb" and "vcpu_syscall_ret" > > callbacks already allow me to instrument syscall translation entry and > > exit points. While the register read/write APIs also allow me to > > modify register contents in my syscall callback implementations, there > > is currently no good way to emulate a syscall myself in the plugin or > > explicitly set the syscall return value (as it will be overwritten > > with the original syscall's return value again, even if I set the > > corresponding guest register). > > > > I was wondering whether the QEMU community would be open to extending > > the plugin API so that a plugin can fully emulate a syscall without > > the original syscall being executed by QEMU. > > I will defer to the *-user maintainers here. One thing we are keen to > avoid is plugins being used as a mechanism to work around the GPL > requirements of QEMU itself. It would be useful if you could outline the > use case for a plugin doing the emulation itself?
Yeah, this sounds like it is potentially going a step too far in enabling fully out of tree extension of core QEMU functionality. If something conceptually is in scope of the core QEMU codebase, then IMHO, our plugin system should aim to avoid enabling external implementations as far as is practical. That was easy when plugins were limited to observability, but the more we enable in terms of state modification the wider pandora's box is opened. Where to draw the line is a hard problem. Excluding some undesirable features, may well force us to exclude some potentially desirable plugin use cases at the same time, which may make it impossible to keep everyone satisfied. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
