From: Richard Henderson <rth@twiddle.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, Gerd Hoffmann <kraxel@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 3/5] exec: Support 64-bit operations in address_space_rw
Date: Wed, 17 Jul 2013 06:23:45 -0700 [thread overview]
Message-ID: <51E69AE1.1060809@twiddle.net> (raw)
In-Reply-To: <51E67B7A.8000800@redhat.com>
On 07/17/2013 04:09 AM, Paolo Bonzini wrote:
>>
>> Fails for me:
>>
>> qemu-system-x86_64: /work/armbru/qemu/exec.c:1927: memory_access_size: Assertion `l >= access_size_min' failed.
>
> This:
>
> unsigned access_size_min = mr->ops->impl.min_access_size;
> unsigned access_size_max = mr->ops->impl.max_access_size;
>
> must be respectively:
>
> unsigned access_size_min = 1;
> unsigned access_size_max = mr->ops->valid.max_access_size;
>
> access_size_min can be 1 because erroneous accesses must not crash
> QEMU, they should trigger exceptions in the guest or just return
> garbage (depending on the CPU). I'm not sure I understand the comment,
> placing a 4-byte field at the last byte of a region makes no sense
> (unless impl.unaligned is true).
>
> access_size_max can be mr->ops->valid.max_access_size because memory.c
> can and will still break accesses bigger than
> mr->ops->impl.max_access_size.
>
> Markus, can you try the minimal patch above? Or this one that also
> does the consequent simplifications.
NAK.
If you remove the check here, you're just trading it for one in the device.
The device told you that it can't support a 1 byte read. (Either that, or the
device incorrectly reported what it can actually do.)
The proper fix is to change the interface of memory_access_size such that it
can report errors. Indeed, very likely we should change it and its callers to
also support over-sized reads, like access_with_adjusted_size in memory.c.
r~
next prev parent reply other threads:[~2013-07-17 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-14 22:16 [Qemu-devel] [PULL 0/5] alpha-softmmu fixes Richard Henderson
2013-07-14 22:16 ` [Qemu-devel] [PULL 1/5] hw/alpha: Don't use get_system_io Richard Henderson
2013-07-14 22:16 ` [Qemu-devel] [PULL 2/5] hw/alpha: Don't machine check on missing pci i/o Richard Henderson
2013-07-14 22:16 ` [Qemu-devel] [PULL 3/5] exec: Support 64-bit operations in address_space_rw Richard Henderson
2013-07-17 9:50 ` Markus Armbruster
2013-07-17 11:09 ` Paolo Bonzini
2013-07-17 13:23 ` Richard Henderson [this message]
2013-07-17 13:45 ` Paolo Bonzini
2013-07-17 14:29 ` Richard Henderson
2013-07-17 14:41 ` Paolo Bonzini
2013-07-17 15:50 ` Anthony Liguori
2013-07-17 17:32 ` Paolo Bonzini
2013-07-17 18:26 ` Richard Henderson
2013-07-17 18:57 ` Paolo Bonzini
2013-07-17 19:28 ` Richard Henderson
2013-07-17 19:56 ` Paolo Bonzini
2013-07-17 20:05 ` Richard Henderson
2013-07-17 18:28 ` Anthony Liguori
2013-07-14 22:16 ` [Qemu-devel] [PULL 4/5] hw/alpha: Drop latch_tmp hack Richard Henderson
2013-07-14 22:16 ` [Qemu-devel] [PULL 5/5] hw/alpha: Use SRM epoch 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=51E69AE1.1060809@twiddle.net \
--to=rth@twiddle.net \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).