From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, Richard Henderson <rth@twiddle.net>,
Stuart Monteith <stuart.monteith@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2 for-2.11 0/2] Fix TCG atomic writes to nondirty pages
Date: Mon, 20 Nov 2017 21:54:37 +0100 [thread overview]
Message-ID: <f5cc649a-8b33-fc0c-4a9c-559a33cda86b@redhat.com> (raw)
In-Reply-To: <1511201308-23580-1-git-send-email-peter.maydell@linaro.org>
On 20/11/2017 19:08, Peter Maydell wrote:
> To do a write to memory that is marked as notdirty, we need
> to invalidate any TBs we have cached for that memory, and
> update the cpu physical memory dirty flags for VGA and migration.
> The slowpath code in notdirty_mem_write() does all this correctly,
> but the new atomic handling code in atomic_mmu_lookup() doesn't
> do anything at all, it just clears the dirty bit in the TLB.
>
> The effect of this bug is that if the first write to a notdirty
> page for which we have cached TBs is by a guest atomic access,
> we fail to invalidate the TBs and subsequently will execute
> incorrect code. This can be seen by trying to run 'javac' on AArch64.
>
> The first patch here refactors notdirty_mem_write() to pull out
> the "correctly handle dirty bit updates" parts of the code into
> two new functions memory_notdirty_write_prepare() and
> memory_notdirty_write_complete(). The second patch then uses
> those functions to fix the atomic helpers.
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Thanks!
Paolo
> Changes v1->v2:
> * add the 'bool active;' flag to NotDirtyInfo in patch 1
> * change the comment on NotDirtyInfo in patch 1 to document
> the active flag (and to fix incorrect references to function
> names that I forgot to update when I decided on the names for
> the prepare/complete functions)
> * in patch 2, don't call prepare unless the TLB was notdirty
> * in patch 2, use the active flag to track whether we need to
> call complete or not
>
> thanks
> -- PMM
>
> Peter Maydell (2):
> exec.c: Factor out before/after actions for notdirty memory writes
> accel/tcg: Handle atomic accesses to notdirty memory correctly
>
> accel/tcg/atomic_template.h | 12 ++++++++
> include/exec/memory-internal.h | 62 ++++++++++++++++++++++++++++++++++++++++
> accel/tcg/cputlb.c | 38 +++++++++++++++---------
> accel/tcg/user-exec.c | 1 +
> exec.c | 65 ++++++++++++++++++++++++++++--------------
> 5 files changed, 144 insertions(+), 34 deletions(-)
>
next prev parent reply other threads:[~2017-11-20 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 18:08 [Qemu-devel] [PATCH v2 for-2.11 0/2] Fix TCG atomic writes to nondirty pages Peter Maydell
2017-11-20 18:08 ` [Qemu-devel] [PATCH v2 for-2.11 1/2] exec.c: Factor out before/after actions for notdirty memory writes Peter Maydell
2017-11-20 18:08 ` [Qemu-devel] [PATCH v2 for-2.11 2/2] accel/tcg: Handle atomic accesses to notdirty memory correctly Peter Maydell
2017-11-20 21:30 ` Richard Henderson
2017-11-20 20:54 ` Paolo Bonzini [this message]
2017-11-21 12:47 ` [Qemu-devel] [PATCH v2 for-2.11 0/2] Fix TCG atomic writes to nondirty pages Peter Maydell
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=f5cc649a-8b33-fc0c-4a9c-559a33cda86b@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=rth@twiddle.net \
--cc=stuart.monteith@linaro.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).