From: "Pavel Dovgalyuk" <dovgaluk@ispras.ru>
To: <qemu-devel@nongnu.org>
Cc: kwolf@redhat.com, jsnow@redhat.com, pavel.dovgaluk@ispras.ru,
mreitz@redhat.com
Subject: RE: [PATCH v2] icount: make dma reads deterministic
Date: Wed, 11 Mar 2020 15:42:48 +0300 [thread overview]
Message-ID: <004001d5f7a2$9297eb50$b7c7c1f0$@ru> (raw)
In-Reply-To: <158323839655.22833.2201521760155801620.stgit@pasha-Precision-3630-Tower>
Ping.
Pavel Dovgalyuk
> -----Original Message-----
> From: Pavel Dovgalyuk [mailto:pavel.dovgaluk@gmail.com]
> Sent: Tuesday, March 03, 2020 3:27 PM
> To: qemu-devel@nongnu.org
> Cc: kwolf@redhat.com; jsnow@redhat.com; dovgaluk@ispras.ru; pavel.dovgaluk@ispras.ru;
> mreitz@redhat.com
> Subject: [PATCH v2] icount: make dma reads deterministic
>
> Windows guest sometimes makes DMA requests with overlapping
> target addresses. This leads to the following structure of iov for
> the block driver:
>
> addr size1
> addr size2
> addr size3
>
> It means that three adjacent disk blocks should be read into the same
> memory buffer. Windows does not expects anything from these bytes
> (should it be data from the first block, or the last one, or some mix),
> but uses them somehow. It leads to non-determinism of the guest execution,
> because block driver does not preserve any order of reading.
>
> This situation was discusses in the mailing list at least twice:
> https://lists.gnu.org/archive/html/qemu-devel/2010-09/msg01996.html
> https://lists.gnu.org/archive/html/qemu-devel/2020-02/msg05185.html
>
> This patch makes such disk reads deterministic in icount mode.
> It splits the whole request into several parts. Parts may overlap,
> but SGs inside one part do not overlap.
> Parts that are processed later overwrite the prior ones in case
> of overlapping.
>
> Examples for different SG part sequences:
>
> 1)
> A1 1000
> A2 1000
> A1 1000
> A3 1000
> ->
> One request is split into two.
> A1 1000
> A2 1000
> --
> A1 1000
> A3 1000
>
> 2)
> A1 800
> A2 1000
> A1 1000
> ->
> A1 800
> A2 1000
> --
> A1 1000
>
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
>
> --
>
> v2:
> - Rewritten the loop to split the request instead of skipping the parts
> (suggested by Kevin Wolf)
> ---
> dma-helpers.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/dma-helpers.c b/dma-helpers.c
> index e8a26e81e1..959e114595 100644
> --- a/dma-helpers.c
> +++ b/dma-helpers.c
> @@ -13,6 +13,8 @@
> #include "trace-root.h"
> #include "qemu/thread.h"
> #include "qemu/main-loop.h"
> +#include "sysemu/cpus.h"
> +#include "qemu/range.h"
>
> /* #define DEBUG_IOMMU */
>
> @@ -142,6 +144,23 @@ static void dma_blk_cb(void *opaque, int ret)
> cur_addr = dbs->sg->sg[dbs->sg_cur_index].base + dbs->sg_cur_byte;
> cur_len = dbs->sg->sg[dbs->sg_cur_index].len - dbs->sg_cur_byte;
> mem = dma_memory_map(dbs->sg->as, cur_addr, &cur_len, dbs->dir);
> + /*
> + * Make reads deterministic in icount mode. Windows sometimes issues
> + * disk read requests with overlapping SGs. It leads
> + * to non-determinism, because resulting buffer contents may be mixed
> + * from several sectors. This code splits all SGs into several
> + * groups. SGs in every group do not overlap.
> + */
> + if (use_icount && dbs->dir == DMA_DIRECTION_FROM_DEVICE) {
> + int i;
> + for (i = 0 ; i < dbs->iov.niov ; ++i) {
> + if (ranges_overlap((intptr_t)dbs->iov.iov[i].iov_base, dbs-
> >iov.iov[i].iov_len,
> + (intptr_t)mem, cur_len)) {
> + mem = NULL;
> + break;
> + }
> + }
> + }
> if (!mem)
> break;
> qemu_iovec_add(&dbs->iov, mem, cur_len);
next prev parent reply other threads:[~2020-03-11 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 12:26 [PATCH v2] icount: make dma reads deterministic Pavel Dovgalyuk
2020-03-11 12:42 ` Pavel Dovgalyuk [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-30 9:02 Pavel Dovgalyuk
2020-06-01 10:36 ` Pavel Dovgalyuk
2020-06-02 15:54 ` Kevin Wolf
2020-06-03 5:57 ` Pavel Dovgalyuk
2020-06-03 8:15 ` Kevin Wolf
2020-06-03 8:56 ` Pavel Dovgalyuk
2020-06-03 9:37 ` Pavel Dovgalyuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004001d5f7a2$9297eb50$b7c7c1f0$@ru' \
--to=dovgaluk@ispras.ru \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).