Hi, >> Something like the attached patch? Which is just the bare minimum I'll >> need for screendump. Basically a one-off bottom half with some monitor >> infrastructure (job id, error handling). So it isn't for big jobs, but >> for small jobs which have to wait for something before they execute >> (spice-server, guest action, whatever). > > I only skimmed over the patch, but you need QMP commands to cancel > and to query running jobs.
Sure, can easily go on top, just need to stuff the monitor_jobs into a list and allow ops on it. Just want to make sure the direction I'm heading to is fine. > Also, please move all this stuff to qmp.c > and do s/monitor/qmp rename. Will do. > Lastly, is it possible to have the block job QMP API on top of this > new QMP job API? Don't think so. As mentioned above this does short-running jobs as bottom half whereas block jobs are running in coroutines ... cheers, Gerd
