All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Richard Henderson <richard.henderson@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH 0/1] accel/tcg: Retry page_check_range() on itree.start inconsistency
Date: Mon,  6 Jul 2026 12:57:24 +0200	[thread overview]
Message-ID: <20260706110330.4150026-1-iii@linux.ibm.com> (raw)

Hi,

This is an attempt to improve the vma-pthread test situation sparked by
a bug report by wasmtime project. The patch doesn't fix all issues, but
it definitely makes things better and I think I understand what
particular thread interleaving leads to the issue (details are in the
commit message).

There is at least one other thing that I find suspicious about the
current code: page_check_range() fetches itree.last twice, and indeed,
using qatomic_read() there makes things even better, but still not
perfect, and I still cannot clearly elaborate what is the exact
interleaving with pageflags_set_clear() that causes a problem there, so
I'm not sending that one for now.

Best regards,
Ilya

Ilya Leoshkevich (1):
  accel/tcg: Retry page_check_range() on itree.start inconsistency

 accel/tcg/user-exec.c | 31 +++++++++++++++----------------
 1 file changed, 15 insertions(+), 16 deletions(-)

-- 
2.54.0



             reply	other threads:[~2026-07-06 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 10:57 Ilya Leoshkevich [this message]
2026-07-06 10:57 ` [PATCH 1/1] accel/tcg: Retry page_check_range() on itree.start inconsistency Ilya Leoshkevich

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=20260706110330.4150026-1-iii@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.