From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Bart Van Assche'" <bvanassche@acm.org>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>
Cc: <alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scsi: ufs: make sure scan sequence for multiple hosts
Date: Thu, 22 Oct 2020 13:59:20 +0900 [thread overview]
Message-ID: <008a01d6a830$1a109800$4e31c800$@samsung.com> (raw)
In-Reply-To: <0a5eb555-af2a-196a-2376-01dc4a92ae0c@acm.org>
> > Did you mean /dev/disk/by-[part]label/ symlink? It's quite reasonable to
> > use them by udev in userspace such as initramfs but some cases does not
> use
> > initramfs or initrd. In that case, we need to load the root
> > device(/dev/sda[N]) directly from kernel.
>
> Please use udev or systemd instead of adding code in the UFS driver that
> is
> not necessary when udev or systemd is used.
>
What I mentioned was how it can be handled when we mount rootfs directly from kernel.
1) kernel -> initramfs (mount root) -> systemd
2) kernel (mount root) -> systemd
-> In this case, we normally use root=/dev/sda1 from kernel commandline to mount the rootfs.
Like fstab can support legacy node mount, ufs driver also needs to provide an option for using the permanent legacy node. If you're really worry about adding a new codes for all UFS driver, we can put this as controller specific or optional feature.
Best Regards,
Chanho Park
next prev parent reply other threads:[~2020-10-22 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201020070519epcas2p27906d7db7c74e45f2acf8243ec2eae1d@epcas2p2.samsung.com>
2020-10-20 7:05 ` [PATCH] scsi: ufs: make sure scan sequence for multiple hosts Chanho Park
2020-10-21 3:15 ` Bart Van Assche
2020-10-21 4:23 ` chanho61.park
2020-10-22 0:29 ` Bart Van Assche
2020-10-22 4:59 ` Chanho Park [this message]
2020-10-22 6:52 ` Avri Altman
2020-10-26 11:20 ` Chanho Park
2020-10-23 15:27 ` Bart Van Assche
[not found] <CGME20201020084429epcas2p3685bcb89c3ab1cacefb183384dcb2b6e@epcas2p3.samsung.com>
2020-10-20 8:44 ` Chanho Park
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='008a01d6a830$1a109800$4e31c800$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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