Re: [PATCH 6/8] virtio-blk: mark IO_CODE functions

2022-07-12 Thread Stefan Hajnoczi
On Fri, Jul 08, 2022 at 11:19:43AM +0200, Emanuele Giuseppe Esposito wrote: > > > Am 05/07/2022 um 16:39 schrieb Stefan Hajnoczi: > > On Thu, Jun 09, 2022 at 10:37:25AM -0400, Emanuele Giuseppe Esposito wrote: > >> Just as done in the block API, mark functions in virtio-blk > >> that are called

Re: [PATCH 6/8] virtio-blk: mark IO_CODE functions

2022-07-08 Thread Emanuele Giuseppe Esposito
Am 05/07/2022 um 16:39 schrieb Stefan Hajnoczi: > On Thu, Jun 09, 2022 at 10:37:25AM -0400, Emanuele Giuseppe Esposito wrote: >> Just as done in the block API, mark functions in virtio-blk >> that are called also from iothread(s). >> >> We know such functions are IO because many are blk_*

Re: [PATCH 6/8] virtio-blk: mark IO_CODE functions

2022-07-05 Thread Stefan Hajnoczi
On Thu, Jun 09, 2022 at 10:37:25AM -0400, Emanuele Giuseppe Esposito wrote: > Just as done in the block API, mark functions in virtio-blk > that are called also from iothread(s). > > We know such functions are IO because many are blk_* callbacks, > running always in the device iothread, and

[PATCH 6/8] virtio-blk: mark IO_CODE functions

2022-06-09 Thread Emanuele Giuseppe Esposito
Just as done in the block API, mark functions in virtio-blk that are called also from iothread(s). We know such functions are IO because many are blk_* callbacks, running always in the device iothread, and remaining are propagated from the leaf IO functions (if a function calls a IO_CODE