qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [RFC PATCH 0/2] exec: Fix (too) short device accesses
@ 2020-05-17 11:38 Philippe Mathieu-Daudé
  2020-05-17 11:38 ` [RFC PATCH 1/2] exec: Let memory_access_size() consider minimum valid access size Philippe Mathieu-Daudé
                   ` (3 more replies)
  0 siblings, 4 replies; 6+ messages in thread
From: Philippe Mathieu-Daudé @ 2020-05-17 11:38 UTC (permalink / raw)
  To: qemu-devel
  Cc: Peter Maydell, Li Zhijian, Tony Nguyen, Alexey Kardashevskiy,
	Julia Suvorova, Philippe Mathieu-Daudé, Peter Xu,
	Alexander Bulekov, Paolo Bonzini, Richard Henderson,
	Stefano Garzarella

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



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-05-17 15:51 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-05-17 11:38 [RFC PATCH 0/2] exec: Fix (too) short device accesses Philippe Mathieu-Daudé
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

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).