On Tue, Apr 16, 2019 at 12:59:34PM +0200, Ján Tomko wrote:
On Mon, Apr 15, 2019 at 04:59:30PM +0200, Ján Tomko wrote:
On Mon, Apr 15, 2019 at 04:23:18PM +0200, Martin Kletzander wrote:
I'll fix other things you mentioned and send a v3 if you want, just let me know.
Depending on your
On Mon, Apr 15, 2019 at 04:59:30PM +0200, Ján Tomko wrote:
On Mon, Apr 15, 2019 at 04:23:18PM +0200, Martin Kletzander wrote:
I'll fix other things you mentioned and send a v3 if you want, just let me know.
Depending on your opinion on the refactor:
On Mon, Apr 15, 2019 at 04:23:18PM +0200, Martin Kletzander wrote:
On Mon, Apr 15, 2019 at 03:59:27PM +0200, Ján Tomko wrote:
On Mon, Apr 15, 2019 at 03:14:21PM +0200, Martin Kletzander wrote:
I/O threads and vCPU threads already support setting schedulers, but until now
it was impossible to
On Mon, Apr 15, 2019 at 03:59:27PM +0200, Ján Tomko wrote:
On Mon, Apr 15, 2019 at 03:14:21PM +0200, Martin Kletzander wrote:
I/O threads and vCPU threads already support setting schedulers, but until now
it was impossible to do so for the main QEMU thread (emulator thread in the
libvirt
On Mon, Apr 15, 2019 at 03:14:21PM +0200, Martin Kletzander wrote:
I/O threads and vCPU threads already support setting schedulers, but until now
it was impossible to do so for the main QEMU thread (emulator thread in the
libvirt naming). This is, however, requested for some very specific
I/O threads and vCPU threads already support setting schedulers, but until now
it was impossible to do so for the main QEMU thread (emulator thread in the
libvirt naming). This is, however, requested for some very specific scenarios,
for example when vCPU threads are running at such priority that
