Searched hist:"6460440 f34c709461b84375cfd8a86b27d433225" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/include/block/ |
| H A D | block_int.h | diff 6460440f34c709461b84375cfd8a86b27d433225 Fri Dec 13 06:04:35 CST 2013 Kevin Wolf <kwolf@redhat.com> block: Allow wait_serialising_requests() at any point
We can only have a single wait_serialising_requests() call per request
because otherwise we can run into deadlocks where requests are waiting
for each other. The same is true when wait_serialising_requests() is not
at the very beginning of a request, so that other requests can be issued
between the start of the tracking and wait_serialising_requests().
Fix this by changing wait_serialising_requests() to ignore requests that
are already (directly or indirectly) waiting for the calling request.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Benoit Canet <benoit@irqsave.net>
|
| /openbmc/qemu/ |
| H A D | block.c | diff 6460440f34c709461b84375cfd8a86b27d433225 Fri Dec 13 06:04:35 CST 2013 Kevin Wolf <kwolf@redhat.com> block: Allow wait_serialising_requests() at any point
We can only have a single wait_serialising_requests() call per request
because otherwise we can run into deadlocks where requests are waiting
for each other. The same is true when wait_serialising_requests() is not
at the very beginning of a request, so that other requests can be issued
between the start of the tracking and wait_serialising_requests().
Fix this by changing wait_serialising_requests() to ignore requests that
are already (directly or indirectly) waiting for the calling request.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Benoit Canet <benoit@irqsave.net>
|