From: Jason Yan <yanaijie@huawei.com>
To: John Garry <john.garry@huawei.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Xiang Chen <chenxiang66@hisilicon.com>
Subject: Re: [PATCH] scsi: hisi_sas: display correct proc_name in sysfs
Date: Tue, 12 May 2020 19:29:07 +0800 [thread overview]
Message-ID: <628c3185-e120-53c9-9971-1eecf9c097f9@huawei.com> (raw)
In-Reply-To: <a0ff79dd-d00e-a938-39c2-0ab281c7f795@huawei.com>
在 2020/5/12 19:07, John Garry 写道:
> On 12/05/2020 11:30, Jason Yan wrote:
>>
>>
>> 在 2020/5/12 18:00, John Garry 写道:
>>> On 12/05/2020 10:35, Jason Yan wrote:
>>>>
>>>>
>>>> 在 2020/5/12 16:23, John Garry 写道:
>>>>> On 12/05/2020 07:33, Jason Yan wrote:
>>>>>> The 'proc_name' entry in sysfs for hisi_sas is 'null' now becuase
>>>>>> it is
>>>>>> not initialized in scsi_host_template. It looks like:
>>>>>>
>>>>>> [root@localhost ~]# cat /sys/class/scsi_host/host2/proc_name
>>>>>> (null)
>>>>>>
>>>>>
>>>>> hmmm.. it would be good to tell us what this buys us, apart from
>>>>> the proc_name file.
>>>>>
>>>>
>>>> When there is more than one storage cards(or controllers) in the
>>>> system, I'm tring to find out which host is belong to which card.
>>>> And then I found this in scsi_host in sysfs but the output is
>>>> '(null)' which is odd.
>>>
>>> "dmesg | grep host" would give this info, like:
>>>
>>> root@(none)$ dmesg | grep host0
>>> [ 8.877245] scsi host0: hisi_sas_v2_hw
>>>
>>
>> NO, if long time after the system boot, dmesg cannot get this
>> infomation. It is flushed by other logs.
>
>
> ok, so I don't see any other way to currently do this, even though using
> proc_name is a bit suspect, so:
>
> Acked-by: John Garry <john.garry@huawei.com>
>
> And the $subject is not right. It should be simply "display proc_name in
> sysfs".
>
Thanks, will send v2 with right $subject.
Jason
> Thanks,
> John
>
> .
prev parent reply other threads:[~2020-05-12 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 6:33 Jason Yan
2020-05-12 8:23 ` John Garry
2020-05-12 9:35 ` Jason Yan
2020-05-12 10:00 ` John Garry
2020-05-12 10:30 ` Jason Yan
2020-05-12 11:07 ` John Garry
2020-05-12 11:29 ` Jason Yan [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=628c3185-e120-53c9-9971-1eecf9c097f9@huawei.com \
--to=yanaijie@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.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
all inboxes | Powered by JetHome®