From: "Cédric Le Goater" <clg@redhat.com>
To: Tomoyuki HIROSE <tomoyuki.hirose@igel.co.jp>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 1/2] system/memory.c: support unaligned access
Date: Mon, 11 Dec 2023 14:31:08 +0100 [thread overview]
Message-ID: <0d11ec9c-ca9f-4135-b723-8155d7d7279c@redhat.com> (raw)
In-Reply-To: <20231211071204.30156-2-tomoyuki.hirose@igel.co.jp>
Hello,
On 12/11/23 08:12, Tomoyuki HIROSE wrote:
> The previous code ignored 'impl.unaligned' and handled unaligned accesses
> as is. But this implementation cannot emulate specific registers of some
> devices that allow unaligned access such as xHCI Host Controller Capability
> Registers.
> This commit checks 'impl.unaligned' and if it is false, QEMU emulates
> unaligned access with multiple aligned access.
>
> Signed-off-by: Tomoyuki HIROSE <tomoyuki.hirose@igel.co.jp>
FWIW, there has been a previous proposal for unaligned accesses support [1].
Thanks,
C.
[1] https://lore.kernel.org/qemu-devel/20170630030058.28943-1-andrew@aj.id.au/
> ---
> system/memory.c | 22 ++++++++++++++++------
> 1 file changed, 16 insertions(+), 6 deletions(-)
>
> diff --git a/system/memory.c b/system/memory.c
> index 798b6c0a17..b0caa90fef 100644
> --- a/system/memory.c
> +++ b/system/memory.c
> @@ -539,6 +539,9 @@ static MemTxResult access_with_adjusted_size(hwaddr addr,
> unsigned i;
> MemTxResult r = MEMTX_OK;
> bool reentrancy_guard_applied = false;
> + hwaddr aligned_addr;
> + unsigned corrected_size = size;
> + signed align_diff = 0;
>
> if (!access_size_min) {
> access_size_min = 1;
> @@ -560,18 +563,25 @@ static MemTxResult access_with_adjusted_size(hwaddr addr,
> reentrancy_guard_applied = true;
> }
>
> - /* FIXME: support unaligned access? */
> access_size = MAX(MIN(size, access_size_max), access_size_min);
> access_mask = MAKE_64BIT_MASK(0, access_size * 8);
> + if (!mr->ops->impl.unaligned) {
> + aligned_addr = addr & ~(access_size - 1);
> + align_diff = addr - aligned_addr;
> + corrected_size = size < access_size ? access_size :
> + size + (align_diff > 0 ? access_size : 0);
> + addr = aligned_addr;
> + }
> if (memory_region_big_endian(mr)) {
> - for (i = 0; i < size; i += access_size) {
> + for (i = 0; i < corrected_size; i += access_size) {
> r |= access_fn(mr, addr + i, value, access_size,
> - (size - access_size - i) * 8, access_mask, attrs);
> + (size - access_size - i + align_diff) * 8,
> + access_mask, attrs);
> }
> } else {
> - for (i = 0; i < size; i += access_size) {
> - r |= access_fn(mr, addr + i, value, access_size, i * 8,
> - access_mask, attrs);
> + for (i = 0; i < corrected_size; i += access_size) {
> + r |= access_fn(mr, addr + i, value, access_size,
> + ((signed)i - align_diff) * 8, access_mask, attrs);
> }
> }
> if (mr->dev && reentrancy_guard_applied) {
next prev parent reply other threads:[~2023-12-11 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 7:12 [PATCH 0/2] support unaligned access for some xHCI registers Tomoyuki HIROSE
2023-12-11 7:12 ` [PATCH 1/2] system/memory.c: support unaligned access Tomoyuki HIROSE
2023-12-11 13:31 ` Cédric Le Goater [this message]
2023-12-15 0:11 ` Tomoyuki Hirose
2024-01-12 15:48 ` Peter Maydell
2024-01-18 6:43 ` Tomoyuki Hirose
2023-12-11 7:12 ` [PATCH 2/2] hw/usb/hcd-xhci.c: allow unaligned access to Capability Registers Tomoyuki HIROSE
2023-12-11 13:57 ` Peter Maydell
2023-12-12 1:43 ` Tomoyuki Hirose
2023-12-12 10:25 ` Peter Maydell
2023-12-18 9:50 ` Tomoyuki Hirose
2024-03-18 16:18 ` Peter Xu
2023-12-19 4:48 ` [PATCH 0/2] support unaligned access for some xHCI registers Tomoyuki Hirose
2023-12-19 11:26 ` Peter Maydell
2023-12-20 1:11 ` Tomoyuki Hirose
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=0d11ec9c-ca9f-4135-b723-8155d7d7279c@redhat.com \
--to=clg@redhat.com \
--cc=david@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tomoyuki.hirose@igel.co.jp \
/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).