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>,
	"kwolf@redhat.com" <kwolf@redhat.com>,
	"hreitz@redhat.com" <hreitz@redhat.com>,
	"farosas@suse.de" <farosas@suse.de>,
	"lvivier@redhat.com" <lvivier@redhat.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
	Jinyoung Choi <j-young.choi@samsung.com>
Subject: Re: [PATCH 0/2] hw/ufs: Add temperature event support and test cases
Date: Tue, 4 Mar 2025 09:55:48 +0900	[thread overview]
Message-ID: <929a3460-6ad7-4028-a6a2-01a33884c41b@gmail.com> (raw)
In-Reply-To: <20250225064001epcms2p81497a6cf84a0c06e54cbce0360053bf8@epcms2p8>


On 2/25/2025 3:40 PM, Keoseong Park wrote:
> This patch series introduces temperature event notification support in
> the UFS emulation and adds corresponding test cases to validate the feature.
>
> The first patch enables the UFS emulation to generate temperature-related
> events, including high and low temperature notifications, following the
> UFS specification. This feature allows UFS drivers to handle temperature
> exception events during testing and development, improving validation and
> debugging capabilities for thermal event handling.
>
> The second patch adds test cases to verify the correctness of query
> attribute results related to the temperature feature. These tests ensure
> that querying temperature attributes returns expected values, helping
> to validate the implementation and maintain correctness in
> temperature-related operations.
>
> Keoseong Park (2):
>    hw/ufs: Add temperature event notification support
>    tests/qtest/ufs-test: Add test code for the temperature feature
>
>   hw/ufs/ufs.c           | 78 +++++++++++++++++++++++++++++++++++++++++-
>   hw/ufs/ufs.h           |  2 ++
>   include/block/ufs.h    | 13 ++++++-
>   tests/qtest/ufs-test.c | 24 +++++++++++++
>   4 files changed, 115 insertions(+), 2 deletions(-)


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



  parent reply	other threads:[~2025-03-04  0:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250225064001epcms2p81497a6cf84a0c06e54cbce0360053bf8@epcms2p8>
2025-02-25  6:40 ` [PATCH 0/2] hw/ufs: Add temperature event support and test cases Keoseong Park
     [not found]   ` <CGME20250225064001epcms2p81497a6cf84a0c06e54cbce0360053bf8@epcms2p5>
2025-02-25  6:41     ` [PATCH 1/2] hw/ufs: Add temperature event notification support Keoseong Park
2025-03-04  0:55   ` Jeuk Kim [this message]
2025-03-05  1:14   ` [PATCH 0/2] hw/ufs: Add temperature event support and test cases Philippe Mathieu-Daudé
2025-02-25  6:42 ` [PATCH 2/2] tests/qtest/ufs-test: Add test code for the temperature feature Keoseong Park
2025-02-28 15:13   ` Fabiano Rosas

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=929a3460-6ad7-4028-a6a2-01a33884c41b@gmail.com \
    --to=jeuk20.kim@gmail.com \
    --cc=farosas@suse.de \
    --cc=hreitz@redhat.com \
    --cc=j-young.choi@samsung.com \
    --cc=jeuk20.kim@samsung.com \
    --cc=keosung.park@samsung.com \
    --cc=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.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).