From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Mikhail Tyutin <m.tyutin@yadro.com>, <qemu-devel@nongnu.org>,
<pbonzini@redhat.com>, <alex.bennee@linaro.org>,
<peter.maydell@linaro.org>, Dmitriy Solovev <d.solovev@yadro.com>
Subject: Re: [PATCH v3] Fix SEGFAULT on getting physical address of MMIO region.
Date: Thu, 10 Aug 2023 14:18:50 +0100 [thread overview]
Message-ID: <20230810141850.000069c9@Huawei.com> (raw)
In-Reply-To: <7d785fc0-06d9-3e4e-b1d2-53ee77fd8ab4@linaro.org>
On Fri, 4 Aug 2023 09:15:13 -0700
Richard Henderson <richard.henderson@linaro.org> wrote:
> On 8/4/23 04:09, Mikhail Tyutin wrote:
> > Apply save_iotlb_data() to io_readx() as well as to io_writex(). This fixes
> > SEGFAULT on qemu_plugin_hwaddr_phys_addr() call plugins for addresses inside of
> > MMIO region.
> >
> > Signed-off-by: Dmitriy Solovev<d.solovev@yadro.com>
> > Signed-off-by: Mikhail Tyutin<m.tyutin@yadro.com>
> > Reviewed-by: Richard Henderson<richard.henderson@linaro.org>
> > ---
> > v3:
> > - commit wording update
> >
> >
> > accel/tcg/cputlb.c | 36 +++++++++++++++++++++---------------
> > 1 file changed, 21 insertions(+), 15 deletions(-)
>
> Queued to tcg-next.
I'm not 100% sure it's related but with qemu/master as of a few hours ago
I'm getting a segfault with backtrace (can't copy from relevant machine)
indicating that
io_writex () is calling memory_region_dispatch_write() and getting
a segfault on
if (mr->alias)
mr has very suspect content of 0x13001300130013
The segfault is intermittent (otherwise I get hang later in boot) and
I can only get it to trigger with multiple cpus.
x86 max cpu and q35 machine.
Jonathan
>
>
> r~
>
next prev parent reply other threads:[~2023-08-10 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 11:09 [PATCH v3] Fix SEGFAULT on getting physical address of MMIO region Mikhail Tyutin
2023-08-04 16:15 ` Richard Henderson
2023-08-10 13:18 ` Jonathan Cameron via [this message]
2023-08-29 10:47 ` Jonathan Cameron via
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=20230810141850.000069c9@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alex.bennee@linaro.org \
--cc=d.solovev@yadro.com \
--cc=m.tyutin@yadro.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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 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).