qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tomoyuki Hirose <tomoyuki.hirose@igel.co.jp>
To: 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>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH 0/2] support unaligned access for some xHCI registers
Date: Tue, 19 Dec 2023 13:48:09 +0900	[thread overview]
Message-ID: <CAFS=EckTC5P8X4-cnyF3oB5K1sDCbAeBnwLwpy-aVrAJomt3sw@mail.gmail.com> (raw)
In-Reply-To: <20231211071204.30156-1-tomoyuki.hirose@igel.co.jp>

I would be grateful if you would any comments on my patch.

ping,

Tomoyuki HIROSE

On Mon, Dec 11, 2023 at 4:12 PM Tomoyuki HIROSE
<tomoyuki.hirose@igel.co.jp> wrote:
>
> According to xHCI spec rev 1.2, unaligned access to xHCI Host
> Controller Capability Registers are not prohibited. But current
> implementation does not support unaligned access to 'MemoryRegion'.
> These patches contain 2 changes:
> 1. support unaligned access to 'MemoryRegion'
> 2. allow unaligned access to Host Controller Capability Registers.
>
> Tomoyuki HIROSE (2):
>   system/memory.c: support unaligned access
>   hw/usb/hcd-xhci.c: allow unaligned access to Capability Registers
>
>  hw/usb/hcd-xhci.c |  4 +++-
>  system/memory.c   | 22 ++++++++++++++++------
>  2 files changed, 19 insertions(+), 7 deletions(-)
>
> --
> 2.39.2
>


  parent reply	other threads:[~2023-12-19  4:49 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
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 ` Tomoyuki Hirose [this message]
2023-12-19 11:26   ` [PATCH 0/2] support unaligned access for some xHCI registers 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='CAFS=EckTC5P8X4-cnyF3oB5K1sDCbAeBnwLwpy-aVrAJomt3sw@mail.gmail.com' \
    --to=tomoyuki.hirose@igel.co.jp \
    --cc=david@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --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).