From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Li Zhijian" <lizhijian@cn.fujitsu.com>,
"Tony Nguyen" <tony.nguyen@bt.com>,
"Alexey Kardashevskiy" <aik@ozlabs.ru>,
"Julia Suvorova" <jusual@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Peter Xu" <peterx@redhat.com>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Stefano Garzarella" <sgarzare@redhat.com>
Subject: [RFC PATCH 0/2] exec: Fix (too) short device accesses
Date: Sun, 17 May 2020 13:38:02 +0200 [thread overview]
Message-ID: <20200517113804.9063-1-f4bug@amsat.org> (raw)
Something noticed while debugging Alexander's bug report
"Hang with high CPU usage in sdhci_data_transfer":
https://bugs.launchpad.net/qemu/+bug/1878054
The flatview ignores the MemoryRegion minimum access size.
It seems related to a similar issue Julia had with PCI
devices.
Not sure it is safe enough, have performance penalties
and so on, so RFC.
Philippe Mathieu-Daudé (2):
exec: Let memory_access_size() consider minimum valid access size
exec: Do not let flatview_read/write_continue do (too) short accesses
exec.c | 42 +++++++++++++++++++++++++++++++-----------
1 file changed, 31 insertions(+), 11 deletions(-)
--
2.21.3
next reply other threads:[~2020-05-17 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 11:38 Philippe Mathieu-Daudé [this message]
2020-05-17 11:38 ` [RFC PATCH 1/2] exec: Let memory_access_size() consider minimum valid access size Philippe Mathieu-Daudé
2020-05-17 11:38 ` [RFC PATCH 2/2] exec: Do not let flatview_read/write_continue do (too) short accesses Philippe Mathieu-Daudé
2020-05-17 13:51 ` [RFC PATCH 0/2] exec: Fix (too) short device accesses no-reply
2020-05-17 15:50 ` Philippe Mathieu-Daudé
2020-05-17 14:20 ` no-reply
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=20200517113804.9063-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=aik@ozlabs.ru \
--cc=alxndr@bu.edu \
--cc=jusual@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sgarzare@redhat.com \
--cc=tony.nguyen@bt.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).