From: Jeuk Kim <jeuk20.kim@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Cc: Jeuk Kim <jeuk20.kim@samsung.com>, qemu-block@nongnu.org
Subject: Ping: Re: [PULL 4/5] hw/ufs: Support for UFS logical unit
Date: Wed, 4 Oct 2023 10:18:33 +0900 [thread overview]
Message-ID: <4642df53-6f67-c66a-4b22-270b3158b6fe@gmail.com> (raw)
In-Reply-To: <9a8f1e6e-edcf-416d-9508-8af666db4263@gmail.com>
Dear Paolo
This is a ping for the following.
If you don't mind, could you give me some feedback?
Thank you very much.
Jeuk
On 23. 9. 21. 17:38, Jeuk Kim wrote:
> Dear Paolo
>
> Hi. I've been looking into how ufs-lu can share code with scsi-hd.
>
> I have verified that ufs-lu can use scsi-hd's code, and I would like
> to modify it to do so.
>
> I've validated two possible fixes.
> I'd like to hear your thoughts.
>
> Option1.
> As you mentioned, using ufsbus, which inherits from scsibus, removes
> the ufs-lu device type and use scsi-hd. (like -device ufs,id=ufs0
> -device scsi-hd,bus=ufs0)
> I've verified that this method is implementable, except for one problem.
> Because we are using the scsi-hd type instead of the ufs-lu type, the
> ufs has to manage all the ufs-lu specific data (such as the unit
> descriptor).
> However, since there is no ufs_lu_realize() function, we need a way to
> notify the ufs when a new scsi-hd device is added.
> Would there be a way to let the ufs know that a new scsi-hd has been
> added at scsi_hd_realize() time?
>
> Option 2.
> Use qdev_new() & qdev_realize() to make ufs-lu have a virtual scsi bus
> and scsi-hd.
> The ufs-lu can pass through SCSI commands to the virtual scsi-hd.
> This is similar to the method used by the device "usb-storage".
>
> With this method, I can keep the ufs-lu device type (ufs_lu_realize()
> makes it convenient to manage ufs-lu related data) and avoid
> duplicating code with scsi-hd.
> So I prefer this approach, but the annotation for "usb-storage" is
> marked with a "Hack alert", so I'm not sure if this is the right way.
> The code can be found in usb_msd_storage_realize()
> (hw/usb/dev-storage-classic.c:51).
>
> I am wondering if you could give me some advice on this and your
> preferred direction for fixing it.
>
> Thank you so much.
>
> Jeuk
>
next prev parent reply other threads:[~2023-10-04 1:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 18:16 [PULL 0/5] Block patches Stefan Hajnoczi
2023-09-07 18:16 ` [PULL 1/5] iothread: Set the GSource "name" field Stefan Hajnoczi
2023-09-07 18:16 ` [PULL 2/5] hw/ufs: Initial commit for emulated Universal-Flash-Storage Stefan Hajnoczi
2023-09-07 18:16 ` [PULL 3/5] hw/ufs: Support for Query Transfer Requests Stefan Hajnoczi
2023-09-14 14:40 ` Peter Maydell
2023-09-14 22:28 ` Jeuk Kim
2023-09-07 18:16 ` [PULL 4/5] hw/ufs: Support for UFS logical unit Stefan Hajnoczi
2023-09-14 14:27 ` Peter Maydell
2023-09-14 14:47 ` Peter Maydell
2023-09-14 17:31 ` Paolo Bonzini
2023-09-14 22:19 ` Jeuk Kim
2023-09-15 7:59 ` Paolo Bonzini
2023-09-18 4:41 ` Jeuk Kim
2023-09-18 4:52 ` Jeuk Kim
2023-09-21 8:38 ` Jeuk Kim
2023-10-04 1:18 ` Jeuk Kim [this message]
2023-09-07 18:16 ` [PULL 5/5] tests/qtest: Introduce tests for UFS Stefan Hajnoczi
2023-09-08 15:55 ` [PULL 0/5] Block patches 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=4642df53-6f67-c66a-4b22-270b3158b6fe@gmail.com \
--to=jeuk20.kim@gmail.com \
--cc=jeuk20.kim@samsung.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).