From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
linuxarm@openeuler.org, "Michael S . Tsirkin" <mst@redhat.com>,
Vishal Verma <vishal.l.verma@intel.com>,
f.fangjian@huawei.com, Chris Browy <cbrowy@avery-design.com>,
qemu-devel@nongnu.org, f4bug@amsat.org, jcm@redhat.com,
Prashant V Agarwal <agpr123@gmail.com>,
Igor Mammedov <imammedo@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Richard Henderson <richard.henderson@linaro.org>,
alex.bennee@linaro.org
Subject: Re: [RFC PATCH 3/3] hw/cxl/cxl-device-utils: Allow incorrect read lengths
Date: Wed, 3 Feb 2021 17:26:37 +0000 [thread overview]
Message-ID: <20210203172637.00006141@Huawei.com> (raw)
In-Reply-To: <20210203161032.ifusdstess7i3ni3@mail.bwidawsk.net>
On Wed, 3 Feb 2021 08:10:32 -0800
Ben Widawsky <ben@bwidawsk.net> wrote:
> On 21-02-01 23:26:55, Jonathan Cameron wrote:
> > This is currently needed to avoid an issue in the Linux RFC
> > in which a read is issued that is not a multiple of DW.
> > On arm64 that results in byte reads being issued and a bus
> > error returned.
> >
> > It is not yet obvious at what level this should be fixed,
> > so paper over it to get things working.
> >
> > Not-signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > ---
> > hw/cxl/cxl-device-utils.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/cxl/cxl-device-utils.c b/hw/cxl/cxl-device-utils.c
> > index d0d0a47122..52dd03384a 100644
> > --- a/hw/cxl/cxl-device-utils.c
> > +++ b/hw/cxl/cxl-device-utils.c
> > @@ -181,11 +181,11 @@ static const MemoryRegionOps mailbox_ops = {
> > .write = mailbox_reg_write,
> > .endianness = DEVICE_LITTLE_ENDIAN,
> > .valid = {
> > - .min_access_size = 4,
> > + .min_access_size = 1,
> > .max_access_size = 8,
> > },
> > .impl = {
> > - .min_access_size = 4,
> > + .min_access_size = 1,
> > .max_access_size = 8,
> > },
> > };
>
> I think this is now addressed in my v3. I'm happy to carry these patches around
> in my branch if it helps.
That would be great if you don't mind.
Thanks!
>
> They all lgtm
prev parent reply other threads:[~2021-02-03 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 15:26 [RFC PATCH 0/3] hw/arm/virt: CXL enablement including gpex-acpi Jonathan Cameron
2021-02-01 15:26 ` [RFC PATCH 1/3] hw/pci-host/gpex-acpi: Add support for dsdt construction for pxb-cxl Jonathan Cameron
2021-02-01 15:26 ` [RFC PATCH 2/3] hw/arm/virt: Basic CXL enablement on pci_expander_bridge instances pxb-cxl Jonathan Cameron
2021-02-01 15:26 ` [RFC PATCH 3/3] hw/cxl/cxl-device-utils: Allow incorrect read lengths Jonathan Cameron
2021-02-03 16:10 ` Ben Widawsky
2021-02-03 17:26 ` Jonathan Cameron [this message]
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=20210203172637.00006141@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=agpr123@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=ben@bwidawsk.net \
--cc=cbrowy@avery-design.com \
--cc=dan.j.williams@intel.com \
--cc=f.fangjian@huawei.com \
--cc=f4bug@amsat.org \
--cc=imammedo@redhat.com \
--cc=jcm@redhat.com \
--cc=linuxarm@openeuler.org \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=vishal.l.verma@intel.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).