qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, alex.bennee@linaro.org, stefanha@redhat.com,
	david@redhat.com
Subject: [Qemu-devel] [RFC v2 0/5] Move notdirty handling to cputlb
Date: Wed, 18 Sep 2019 11:02:46 -0700	[thread overview]
Message-ID: <20190918180251.32003-1-richard.henderson@linaro.org> (raw)

RFC because it *still* doesn't work, just like v1.

However this time the changes are extremely minimal, and now
I really *really* don't understand why they don't work, because
as far as I can tell the new locking is *identical* with the
current i/o path.

In particular, the actual access happens between _prepare
and _complete, just like before.  Indeed, since this doesn't
work as-is, then I can't believe the atomic path works either.

I have included the TLB_BSWAP stuff just so that the
patch set is self-contained.

I did experiment with qemu_ram_addr_from_host_nofail(), but
an assertion for equality with addr + iotlbentry->addr does
not trigger.  As expected, really, since that's what the i/o
path uses.  One more cleanup for the atomics path...

Ideas?


r~


Richard Henderson (5):
  cputlb: Disable __always_inline__ without optimization
  cputlb: Replace switches in load/store_helper with callback
  cputlb: Introduce TLB_BSWAP
  exec: Adjust notdirty tracing
  cputlb: Move NOTDIRTY handling from I/O path to TLB path

 include/exec/cpu-all.h    |   2 +
 include/exec/cpu-common.h |   1 -
 include/qemu/compiler.h   |  11 ++
 accel/tcg/cputlb.c        | 243 +++++++++++++++++++++-----------------
 exec.c                    |  57 +--------
 memory.c                  |  20 ----
 trace-events              |   4 +-
 7 files changed, 157 insertions(+), 181 deletions(-)

-- 
2.17.1



             reply	other threads:[~2019-09-18 18:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 18:02 Richard Henderson [this message]
2019-09-18 18:02 ` [Qemu-devel] [RFC v2 1/5] cputlb: Disable __always_inline__ without optimization Richard Henderson
2019-09-19 14:36   ` David Hildenbrand
2019-09-18 18:02 ` [Qemu-devel] [RFC v2 2/5] cputlb: Replace switches in load/store_helper with callback Richard Henderson
2019-09-19 14:53   ` David Hildenbrand
2019-09-19 15:10     ` Richard Henderson
2019-09-18 18:02 ` [Qemu-devel] [RFC v2 3/5] cputlb: Introduce TLB_BSWAP Richard Henderson
2019-09-19 15:09   ` David Hildenbrand
2019-09-19 15:13     ` Richard Henderson
2019-09-18 18:02 ` [Qemu-devel] [RFC v2 4/5] exec: Adjust notdirty tracing Richard Henderson
2019-09-19 15:40   ` David Hildenbrand
2019-09-18 18:02 ` [Qemu-devel] [RFC v2 5/5] cputlb: Move NOTDIRTY handling from I/O path to TLB path Richard Henderson
2019-09-19 10:27 ` [Qemu-devel] [RFC v2 0/5] Move notdirty handling to cputlb no-reply
2019-09-19 12:19 ` no-reply
2019-09-19 12:22 ` no-reply
2019-09-21 22:21 ` Richard Henderson

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=20190918180251.32003-1-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=david@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).