From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Michael Tsirkin <mst@redhat.com>,
qemu-devel@nongnu.org
Cc: linuxarm@huawei.com, Fan Ni <fan.ni@samsung.com>,
Dave Jiang <dave.jiang@intel.com>,
linux-cxl@vger.kernel.org
Subject: Re: [RESEND PATCH 1/2] hw/cxl: Fix endian handling for decoder commit.
Date: Wed, 22 Mar 2023 11:34:34 +0100 [thread overview]
Message-ID: <366919e9-e7ca-28bf-f61a-813634c4a115@linaro.org> (raw)
In-Reply-To: <20230322102731.4219-2-Jonathan.Cameron@huawei.com>
On 22/3/23 11:27, Jonathan Cameron via wrote:
> Not a real problem yet as all supported architectures are
> little endian, but continue to tidy these up when touching
> code for other reasons.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> hw/cxl/cxl-component-utils.c | 10 ++++------
> hw/mem/cxl_type3.c | 9 ++++++---
> 2 files changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/hw/cxl/cxl-component-utils.c b/hw/cxl/cxl-component-utils.c
> index b665d4f565..a3e6cf75cf 100644
> --- a/hw/cxl/cxl-component-utils.c
> +++ b/hw/cxl/cxl-component-utils.c
> @@ -47,14 +47,12 @@ static void dumb_hdm_handler(CXLComponentState *cxl_cstate, hwaddr offset,
> break;
> }
>
> - memory_region_transaction_begin();
> - stl_le_p((uint8_t *)cache_mem + offset, value);
> if (should_commit) {
> - ARRAY_FIELD_DP32(cache_mem, CXL_HDM_DECODER0_CTRL, COMMIT, 0);
> - ARRAY_FIELD_DP32(cache_mem, CXL_HDM_DECODER0_CTRL, ERR, 0);
> - ARRAY_FIELD_DP32(cache_mem, CXL_HDM_DECODER0_CTRL, COMMITTED, 1);
> + value = FIELD_DP32(value, CXL_HDM_DECODER0_CTRL, COMMIT, 0);
> + value = FIELD_DP32(value, CXL_HDM_DECODER0_CTRL, ERR, 0);
> + value = FIELD_DP32(value, CXL_HDM_DECODER0_CTRL, COMMITTED, 1);
> }
> - memory_region_transaction_commit();
Indeed the memory_region_transaction guard seems pointless here,
but it is a different change, so should go in a preliminary patch IMHO.
Conditional to this patch being split:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> + stl_le_p((uint8_t *)cache_mem + offset, value);
> }
next prev parent reply other threads:[~2023-03-22 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 10:27 [RESEND PATCH 0/2] hw/cxl: Fix decoder commit and uncommit handling Jonathan Cameron via
2023-03-22 10:27 ` [RESEND PATCH 1/2] hw/cxl: Fix endian handling for decoder commit Jonathan Cameron via
2023-03-22 10:34 ` Philippe Mathieu-Daudé [this message]
2023-03-22 10:27 ` [RESEND PATCH 2/2] hw/cxl: Fix incorrect reset of commit and associated clearing of committed Jonathan Cameron via
2023-03-22 10:33 ` Jonathan Cameron via
2023-03-22 16:21 ` Fan Ni
2023-03-24 14:01 ` Jonathan Cameron via
2023-03-24 17:05 ` Dave Jiang
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=366919e9-e7ca-28bf-f61a-813634c4a115@linaro.org \
--to=philmd@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=dave.jiang@intel.com \
--cc=fan.ni@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mst@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).