Re: [PATCH 2/8] block-backend: enable_write_cache should be atomic

2022-11-11 Thread Emanuele Giuseppe Esposito
Am 08/11/2022 um 22:19 schrieb Stefan Hajnoczi: > From: Emanuele Giuseppe Esposito > > It is read from IO_CODE and written with BQL held, > so setting it as atomic should be enough. > > Also remove the aiocontext lock that was sporadically > taken around the set. > > Signed-off-by: Emanuele

[PATCH 2/8] block-backend: enable_write_cache should be atomic

2022-11-08 Thread Stefan Hajnoczi
From: Emanuele Giuseppe Esposito It is read from IO_CODE and written with BQL held, so setting it as atomic should be enough. Also remove the aiocontext lock that was sporadically taken around the set. Signed-off-by: Emanuele Giuseppe Esposito Reviewed-by: Stefan Hajnoczi Signed-off-by:

Re: [PATCH 2/8] block-backend: enable_write_cache should be atomic

2022-07-05 Thread Stefan Hajnoczi
On Thu, Jun 09, 2022 at 10:37:21AM -0400, Emanuele Giuseppe Esposito wrote: > It is read from IO_CODE and written with BQL held, > so setting it as atomic should be enough. > > Also remove the aiocontext lock that was sporadically > taken around the set. > > Signed-off-by: Emanuele Giuseppe

[PATCH 2/8] block-backend: enable_write_cache should be atomic

2022-06-09 Thread Emanuele Giuseppe Esposito
It is read from IO_CODE and written with BQL held, so setting it as atomic should be enough. Also remove the aiocontext lock that was sporadically taken around the set. Signed-off-by: Emanuele Giuseppe Esposito --- block/block-backend.c | 6 +++--- hw/block/virtio-blk.c | 4 2 files