Messages in this thread | | | From | KY Srinivasan <> | Subject | RE: [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on Hyper-V | Date | Tue, 15 Mar 2016 23:01:03 +0000 |
| |
> -----Original Message----- > From: Martin K. Petersen [mailto:martin.petersen@oracle.com] > Sent: Tuesday, March 15, 2016 2:25 PM > To: KY Srinivasan <kys@microsoft.com> > Cc: Christoph Hellwig <hch@infradead.org>; gregkh@linuxfoundation.org; > linux-kernel@vger.kernel.org; devel@linuxdriverproject.org; > ohering@suse.com; jbottomley@parallels.com; linux-scsi@vger.kernel.org; > apw@canonical.com; vkuznets@redhat.com; jasowang@redhat.com; > martin.petersen@oracle.com; hare@suse.de > Subject: Re: [PATCH 1/1] scsi: storvsc: Support manual scan of FC hosts on > Hyper-V > > >>>>> "KY" == KY Srinivasan <kys@microsoft.com> writes: > > KY> Till recently I had not. However, we do support publishing wwn in > KY> the guest and some customers wanted this. That is the reason I am > KY> attaching FC transport and working through the issues. With this > KY> change, I now have wwn names published in the guest and I can also > KY> issue manual scan. > > Why does it have to look like FC? Will a device identification VPD page > not do the trick?
How would I get the sysfs files under fc_host if I don't use the FC transport. The customer scripts expect these sysfs files.
Regards,
K. Y > > -- > Martin K. Petersen Oracle Linux Engineering
| |