From: Jeuk Kim <jeuk20.kim@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, fam@euphon.net, hreitz@redhat.com,
k.jensen@samsung.com, kwolf@redhat.com, pbonzini@redhat.com,
qemu-block@nongnu.org, stefanha@redhat.com, berrange@redhat.com,
marcandre.lureau@redhat.com, marcel.apfelbaum@gmail.com,
mst@redhat.com, philmd@linaro.org, thuth@redhat.com,
Jeuk Kim <jeuk20.kim@samsung.com>
Subject: Re: [PATCH v6 0/3] hw/ufs: Add Universal Flash Storage (UFS) support
Date: Sun, 23 Jul 2023 12:17:50 +0900 [thread overview]
Message-ID: <d8e08f78-e294-ec51-63d6-b4b3588660c0@gmail.com> (raw)
In-Reply-To: <CAJSP0QU6Y0rDjb8Uy5KeST0kLfrAk7Hh8BKkoTnQ3_YhWyWSpQ@mail.gmail.com>
On 7/21/2023 8:01 PM, Stefan Hajnoczi wrote:
> Is there a test case along the lines of tests/qtest/ahci-test.c that
> exercises this new code?
>
> It's important to have at least a basic test that initializes the
> device and performs a write followed by a read to verify that I/O is
> working. This will allow the CI system and anyone who modifies the UFS
> code to check that the basics are still working.
>
> Thanks,
> Stefan
Okay, I'll prepare patch v7 by adding tests related to ufs
initialisation and io tests.
Thanks,
Jeuk
prev parent reply other threads:[~2023-07-23 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 0:46 [PATCH v6 0/3] hw/ufs: Add Universal Flash Storage (UFS) support Jeuk Kim
2023-07-21 0:46 ` [PATCH v6 1/3] hw/ufs: Initial commit for emulated Universal-Flash-Storage Jeuk Kim
2023-07-21 0:46 ` [PATCH v6 2/3] hw/ufs: Support for Query Transfer Requests Jeuk Kim
2023-07-21 0:46 ` [PATCH v6 3/3] hw/ufs: Support for UFS logical unit Jeuk Kim
2023-07-21 11:01 ` [PATCH v6 0/3] hw/ufs: Add Universal Flash Storage (UFS) support Stefan Hajnoczi
2023-07-23 3:17 ` Jeuk Kim [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=d8e08f78-e294-ec51-63d6-b4b3588660c0@gmail.com \
--to=jeuk20.kim@gmail.com \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jeuk20.kim@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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).