qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeuk Kim <jeuk20.kim@gmail.com>
To: keosung.park@samsung.com, Jeuk Kim <jeuk20.kim@samsung.com>,
	"philmd@linaro.org" <philmd@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "farosas@suse.de" <farosas@suse.de>,
	"lvivier@redhat.com" <lvivier@redhat.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [PATCH v2] hw/ufs: Adjust value to match CPU's endian format
Date: Tue, 7 Jan 2025 18:17:30 +0900	[thread overview]
Message-ID: <a59dd0e0-12a6-4fb7-9494-23cfd653ade9@gmail.com> (raw)
In-Reply-To: <20250107084356epcms2p2af4d86432174d76ea57336933e46b4c3@epcms2p2>


On 1/7/2025 5:43 PM, Keoseong Park wrote:
> In ufs_write_attr_value(), the value parameter is handled in the CPU's
> endian format but provided in big-endian format by the caller. Thus, it
> is converted to the CPU's endian format. The related test code is also
> fixed to reflect this change.
>
> Fixes: 7c85332a2b3e ("hw/ufs: minor bug fixes related to ufs-test")
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Keoseong Park <keosung.park@samsung.com>
> ---
>   hw/ufs/ufs.c           | 2 +-
>   tests/qtest/ufs-test.c | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/ufs/ufs.c b/hw/ufs/ufs.c
> index 8d26d13791..428fe927ad 100644
> --- a/hw/ufs/ufs.c
> +++ b/hw/ufs/ufs.c
> @@ -1164,7 +1164,7 @@ static QueryRespCode ufs_exec_query_attr(UfsRequest *req, int op)
>           value = ufs_read_attr_value(u, idn);
>           ret = UFS_QUERY_RESULT_SUCCESS;
>       } else {
> -        value = req->req_upiu.qr.value;
> +        value = be32_to_cpu(req->req_upiu.qr.value);
>           ret = ufs_write_attr_value(u, idn, value);
>       }
>       req->rsp_upiu.qr.value = cpu_to_be32(value);
> diff --git a/tests/qtest/ufs-test.c b/tests/qtest/ufs-test.c
> index 60199abbee..1f860b41c0 100644
> --- a/tests/qtest/ufs-test.c
> +++ b/tests/qtest/ufs-test.c
> @@ -145,7 +145,7 @@ static void ufs_send_query(QUfs *ufs, uint8_t slot, uint8_t query_function,
>       req_upiu.qr.idn = idn;
>       req_upiu.qr.index = index;
>       req_upiu.qr.selector = selector;
> -    req_upiu.qr.value = attr_value;
> +    req_upiu.qr.value = cpu_to_be32(attr_value);
>       req_upiu.qr.length = UFS_QUERY_DESC_MAX_SIZE;
>       qtest_memwrite(ufs->dev.bus->qts, req_upiu_addr, &req_upiu,
>                      sizeof(req_upiu));


Thank you for your contribution.

Reviewed-by: Jeuk Kim <jeuk20.kim@samsung.com>


  reply	other threads:[~2025-01-07  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250107084356epcms2p2af4d86432174d76ea57336933e46b4c3@epcms2p2>
2025-01-07  8:43 ` [PATCH v2] hw/ufs: Adjust value to match CPU's endian format Keoseong Park
2025-01-07  9:17   ` Jeuk Kim [this message]
2025-01-09 14:47   ` Philippe Mathieu-Daudé
2025-01-15 12:53   ` Michael Tokarev
2025-01-15 13:03     ` Philippe Mathieu-Daudé

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=a59dd0e0-12a6-4fb7-9494-23cfd653ade9@gmail.com \
    --to=jeuk20.kim@gmail.com \
    --cc=farosas@suse.de \
    --cc=jeuk20.kim@samsung.com \
    --cc=keosung.park@samsung.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@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).