From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jeuk Kim <jeuk20.kim@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, berrange@redhat.com,
marcandre.lureau@redhat.com, marcel.apfelbaum@gmail.com,
mst@redhat.com, philmd@linaro.org, thuth@redhat.com,
lvivier@redhat.com, jeuk20.kim@samsung.com
Subject: Re: [PATCH v8 0/4] hw/ufs: Add Universal Flash Storage (UFS) support
Date: Thu, 27 Jul 2023 11:52:39 -0400 [thread overview]
Message-ID: <20230727155239.GA979354@fedora> (raw)
In-Reply-To: <cover.1690446561.git.jeuk20.kim@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 3789 bytes --]
On Thu, Jul 27, 2023 at 05:45:17PM +0900, Jeuk Kim wrote:
> Since v7:
> In ufs-test.c, make the following changes
> - Change TIMEOUT from 5 to 10 (Thomas's review comment)
> - Rename the temporary file to "qemu-ufs.XXXX" (Thomas's review comment)
> - Use "-blockdev" instead of "-drive" (Stefan's review comment)
>
> Since v6:
> - Add tests/qtest/ufs-test.c to test ufs initialisation and I/O
> - Add struct UtpTaskReqDesc to include/block/ufs.h
> - Fix ufs_log2() logic
> - Fix ufs-lu to use 4K as default block size to match the ufs spec
>
> Since I created a new file, tests/qtest/ufs-test.c, I added Laurent Vivier to the cc list.
> Thank you.
>
> Since v5:
> - Fix to print an error message instead of a segmentation fault
> when no drive property is specified for a ufs-lu device
>
> Since v4:
> Addressed review comment from Stefan Hajnoczi. The fixes are as
> follows.
> - Keep u->reg fields in host endian (Removed little-endian helper
> functions from MemoryRegionOps)
> - Remove unnecessary NULL checks for g_new and g_malloc0
> - Replace DEFINE_PROP_DRIVE_IOTHREAD -> DEFINE_PROP_DRIVE
>
> In case you were wondering, ufs and ufs-lu have been tested for the
> following behaviours.
> 1. Checked ufs device recognition in Windows10 environment
> 2. Verified ufs device recognition in Ubuntu 22.04 environment
> 3. Verified io behaviour via fio in Ubuntu 22.04 environment
> 4. Verified query request via ufs-tools in Ubuntu 22.04 environment
>
> Since v3:
> - Replace softmmu_ss -> system_ss in meson
>
> Since v2:
> Addressed review comment from Stefan Hajnoczi. The main fixes are as
> follows.
> - Use of SPDX licence identifiers
> - fixed endianness error
> - removed memory leak
> - fixed DMA error handling logic
>
> Since v1:
> - use macros of "hw/registerfields.h" (Addressed Philippe's review
> comments)
>
> This patch series adds support for a new PCI-based UFS device.
>
> The UFS pci device id (PCI_DEVICE_ID_REDHAT_UFS) is not registered
> in the Linux kernel yet, so it does not work right away, but I confirmed
> that it works with Linux when the UFS pci device id is registered.
>
> I have also verified that it works with Windows 10.
>
> Jeuk Kim (4):
> hw/ufs: Initial commit for emulated Universal-Flash-Storage
> hw/ufs: Support for Query Transfer Requests
> hw/ufs: Support for UFS logical unit
> tests/qtest: Introduce tests for UFS
>
> MAINTAINERS | 7 +
> docs/specs/pci-ids.rst | 2 +
> hw/Kconfig | 1 +
> hw/meson.build | 1 +
> hw/ufs/Kconfig | 4 +
> hw/ufs/lu.c | 1445 ++++++++++++++++++++++++++++++++++++
> hw/ufs/meson.build | 1 +
> hw/ufs/trace-events | 58 ++
> hw/ufs/trace.h | 1 +
> hw/ufs/ufs.c | 1494 ++++++++++++++++++++++++++++++++++++++
> hw/ufs/ufs.h | 131 ++++
> include/block/ufs.h | 1090 +++++++++++++++++++++++++++
> include/hw/pci/pci.h | 1 +
> include/hw/pci/pci_ids.h | 1 +
> include/scsi/constants.h | 1 +
> meson.build | 1 +
> tests/qtest/meson.build | 1 +
> tests/qtest/ufs-test.c | 573 +++++++++++++++
> 18 files changed, 4813 insertions(+)
> create mode 100644 hw/ufs/Kconfig
> create mode 100644 hw/ufs/lu.c
> create mode 100644 hw/ufs/meson.build
> create mode 100644 hw/ufs/trace-events
> create mode 100644 hw/ufs/trace.h
> create mode 100644 hw/ufs/ufs.c
> create mode 100644 hw/ufs/ufs.h
> create mode 100644 include/block/ufs.h
> create mode 100644 tests/qtest/ufs-test.c
>
> --
> 2.34.1
>
Thanks, applied to my block-next tree:
https://gitlab.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-27 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 8:45 [PATCH v8 0/4] hw/ufs: Add Universal Flash Storage (UFS) support Jeuk Kim
2023-07-27 8:45 ` [PATCH v8 1/4] hw/ufs: Initial commit for emulated Universal-Flash-Storage Jeuk Kim
2023-07-27 8:45 ` [PATCH v8 2/4] hw/ufs: Support for Query Transfer Requests Jeuk Kim
2023-07-27 8:45 ` [PATCH v8 3/4] hw/ufs: Support for UFS logical unit Jeuk Kim
2023-07-27 8:45 ` [PATCH v8 4/4] tests/qtest: Introduce tests for UFS Jeuk Kim
2023-07-27 15:52 ` Stefan Hajnoczi [this message]
2023-07-27 16:01 ` [PATCH v8 0/4] hw/ufs: Add Universal Flash Storage (UFS) support Stefan Hajnoczi
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=20230727155239.GA979354@fedora \
--to=stefanha@redhat.com \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jeuk20.kim@gmail.com \
--cc=jeuk20.kim@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kwolf@redhat.com \
--cc=lvivier@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=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).