From: Thomas Huth <thuth@redhat.com>
To: jeuk20.kim@samsung.com
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"hreitz@redhat.com" <hreitz@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"marcel.apfelbaum@gmail.com" <marcel.apfelbaum@gmail.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"marcandre.lureau@redhat.com" <marcandre.lureau@redhat.com>,
"berrange@redhat.com" <berrange@redhat.com>,
"philmd@linaro.org" <philmd@linaro.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
Klaus Birkelund Jensen <k.jensen@samsung.com>
Subject: Re: [PATCH 1/3] hw/ufs: Initial commit for emulated Universal-Flash-Storage
Date: Tue, 30 May 2023 07:39:41 +0200 [thread overview]
Message-ID: <432e800a-9499-a7e5-bac8-2f8877ae1a46@redhat.com> (raw)
In-Reply-To: <20230530013646epcms2p392066e0dcbd6613d06977974a4f81c1d@epcms2p3>
On 30/05/2023 03.36, Jeuk Kim wrote:
> On 26/05/2023 15:37, Thomas Huth wrote:
>> On 26/05/2023 07.05, Jeuk Kim wrote:
>>> Universal Flash Storage (UFS) is a high-performance mass storage device
>>> with a serial interface. It is primarily used as a high-performance
>>> data storage device for embedded applications.
>>>
>>> This commit contains code for UFS device to be recognized
>>> as a UFS PCI device.
>>> Patches to handle UFS logical unit and Transfer Request will follow.
>>>
>>> Signed-off-by: Jeuk Kim <jeuk20.kim@samsung.com>
>>> ---
>>> MAINTAINERS | 6 +
>>> hw/Kconfig | 1 +
>>> hw/meson.build | 1 +
>>> hw/ufs/Kconfig | 4 +
>>> hw/ufs/meson.build | 1 +
>>> hw/ufs/trace-events | 33 +
>>> hw/ufs/trace.h | 1 +
>>> hw/ufs/ufs.c | 305 ++++++++++
>>> hw/ufs/ufs.h | 42 ++
>>> include/block/ufs.h | 1251 ++++++++++++++++++++++++++++++++++++++
>>> include/hw/pci/pci.h | 1 +
>>> include/hw/pci/pci_ids.h | 1 +
>>> meson.build | 1 +
>>
>> Do you expect lots of additional files to be added to the hw/ufs/ folder? If
>> the answer is no, then it's maybe a little bit overkill to introduce a
>> separate folder for this. Wouldn't hw/block/ be a good fit for this as well?
>> Or maybe we could introduce hw/flash/ or so and also move the contents of
>> hw/nvme there?
>
> Yes. I plan to add more files to UFS for different functions (UICCMD, MQ, zoned, etc.) like nvme.
> So personally, I think it would be good to keep the hw/ufs/ directory.
Ok, fair. Then start with hw/ufs/ first and we'll see how it goes. We can
still move the files later if necessary.
Thomas
next prev parent reply other threads:[~2023-05-30 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230526050555epcms2p287be772002cd941cc79226968c319036@epcms2p2>
2023-05-26 5:05 ` [PATCH 1/3] hw/ufs: Initial commit for emulated Universal-Flash-Storage Jeuk Kim
2023-05-26 6:37 ` Thomas Huth
[not found] ` <CGME20230526050555epcms2p287be772002cd941cc79226968c319036@epcms2p3>
2023-05-30 1:36 ` Jeuk Kim
2023-05-30 5:39 ` Thomas Huth [this message]
2023-05-30 10:17 ` Philippe Mathieu-Daudé
[not found] ` <CGME20230526050555epcms2p287be772002cd941cc79226968c319036@epcms2p1>
2023-06-01 0:11 ` Jeuk Kim
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=432e800a-9499-a7e5-bac8-2f8877ae1a46@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--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 \
/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).