Re: [Qemu-devel] QEMU event loop optimizations

2019-04-08 Thread Paolo Bonzini
On 05/04/19 18:33, Sergio Lopez wrote: >> - qemu_bh_schedule_nested should not be necessary since we have >> ctx->notify_me to also avoid the event_notifier_set call. However, it >> is possible to avoid the smp_mb at the beginning of aio_notify, since >> atomic_xchg already implies it. Maybe

Re: [Qemu-devel] QEMU event loop optimizations

2019-04-08 Thread Stefan Hajnoczi
On Fri, Apr 05, 2019 at 06:29:49PM +0200, Sergio Lopez wrote: > > Stefan Hajnoczi writes: > > > Hi Sergio, > > Here are the forgotten event loop optimizations I mentioned: > > > > https://github.com/stefanha/qemu/commits/event-loop-optimizations > > > > The goal was to eliminate or reorder

Re: [Qemu-devel] QEMU event loop optimizations

2019-04-05 Thread Sergio Lopez
Paolo Bonzini writes: > On 26/03/19 14:18, Stefan Hajnoczi wrote: >> Hi Sergio, >> Here are the forgotten event loop optimizations I mentioned: >> >> https://github.com/stefanha/qemu/commits/event-loop-optimizations >> >> The goal was to eliminate or reorder syscalls so that useful work

Re: [Qemu-devel] QEMU event loop optimizations

2019-04-05 Thread Sergio Lopez
Stefan Hajnoczi writes: > Hi Sergio, > Here are the forgotten event loop optimizations I mentioned: > > https://github.com/stefanha/qemu/commits/event-loop-optimizations > > The goal was to eliminate or reorder syscalls so that useful work (like > executing BHs) occurs as soon as possible

Re: [Qemu-devel] QEMU event loop optimizations

2019-04-02 Thread Paolo Bonzini
On 02/04/19 18:18, Kevin Wolf wrote: > Am 26.03.2019 um 15:11 hat Paolo Bonzini geschrieben: >> - but actually (and a precursor to using IOCB_CMD_POLL) it should be >> possible to have just one LinuxAioState per AioContext, and then >> it can simply share the AioContext's EventNotifier. This

Re: [Qemu-devel] QEMU event loop optimizations

2019-04-02 Thread Kevin Wolf
Am 26.03.2019 um 15:11 hat Paolo Bonzini geschrieben: > - but actually (and a precursor to using IOCB_CMD_POLL) it should be > possible to have just one LinuxAioState per AioContext, and then > it can simply share the AioContext's EventNotifier. This removes > the need to do the

Re: [Qemu-devel] QEMU event loop optimizations

2019-03-27 Thread Stefan Hajnoczi
On Tue, Mar 26, 2019 at 02:37:35PM +0100, Paolo Bonzini wrote: > On 26/03/19 14:18, Stefan Hajnoczi wrote: > > Hi Sergio, > > Here are the forgotten event loop optimizations I mentioned: > > > > https://github.com/stefanha/qemu/commits/event-loop-optimizations > > > > The goal was to eliminate

Re: [Qemu-devel] QEMU event loop optimizations

2019-03-26 Thread Paolo Bonzini
On 26/03/19 14:18, Stefan Hajnoczi wrote: > Hi Sergio, > Here are the forgotten event loop optimizations I mentioned: > > https://github.com/stefanha/qemu/commits/event-loop-optimizations > > The goal was to eliminate or reorder syscalls so that useful work (like > executing BHs) occurs as

Re: [Qemu-devel] QEMU event loop optimizations

2019-03-26 Thread Paolo Bonzini
On 26/03/19 14:18, Stefan Hajnoczi wrote: > Hi Sergio, > Here are the forgotten event loop optimizations I mentioned: > > https://github.com/stefanha/qemu/commits/event-loop-optimizations > > The goal was to eliminate or reorder syscalls so that useful work (like > executing BHs) occurs as

[Qemu-devel] QEMU event loop optimizations

2019-03-26 Thread Stefan Hajnoczi
Hi Sergio, Here are the forgotten event loop optimizations I mentioned: https://github.com/stefanha/qemu/commits/event-loop-optimizations The goal was to eliminate or reorder syscalls so that useful work (like executing BHs) occurs as soon as possible after an event is detected. I remember