| commit | 82c45371ba698ff63e9d3d4792a34593f73e54d8 | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Thu, 22 Sep 2022 08:48:59 +0000 (22 10:48 +0200) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Fri, 7 Oct 2022 10:11:40 +0000 (7 12:11 +0200) | ||
| tree | 3cf6225992027e8afa81dac92a6a8ca2ee565a70 | treesnapshot (tar.gz zip) |
| parent | ef770f8101f6a3f4fb38a4fa693dfe68a0ac6bf2 | commitdiff |
block/nvme: separate nvme_get_free_req cases for coroutine/non-coroutine context
nvme_get_free_req has very difference semantics when called in
coroutine context (where it waits) and in non-coroutine context
(where it doesn't). Split the two cases to make it clear what
is being requested.
Cc: qemu-block@nongnu.org
Reviewed-by: Alberto Faria <afaria@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20220922084924.201610-2-pbonzini@redhat.com>
[kwolf: Fixed up coding style]
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
nvme_get_free_req has very difference semantics when called in
coroutine context (where it waits) and in non-coroutine context
(where it doesn't). Split the two cases to make it clear what
is being requested.
Cc: qemu-block@nongnu.org
Reviewed-by: Alberto Faria <afaria@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20220922084924.201610-2-pbonzini@redhat.com>
[kwolf: Fixed up coding style]
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| block/nvme.c | diffblobblamehistory |