RE: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent

2016-09-16 Thread KY Srinivasan
.com> > Subject: Re: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs > persistent > > Vitaly Kuznetsov <vkuzn...@redhat.com> writes: > > > Bus ids for VMBus devices in /sys/bus/vmbus/devices/ are not guaranteed > > to be persistent across reboot or

RE: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent

2016-09-16 Thread KY Srinivasan
> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Friday, September 16, 2016 4:53 PM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; Haiyang > Zhang > Subject: Re: [PATCH v2 0/2] Drivers: hv

Re: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent

2016-09-16 Thread Vitaly Kuznetsov
Vitaly Kuznetsov writes: > Bus ids for VMBus devices in /sys/bus/vmbus/devices/ are not guaranteed > to be persistent across reboot or kernel restart and this causes problems > for some tools. E.g. kexec tools use these ids to identify NIC on kdump. > Fix the issue by using

Re: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent

2016-09-16 Thread Vitaly Kuznetsov
Vitaly Kuznetsov writes: > Bus ids for VMBus devices in /sys/bus/vmbus/devices/ are not guaranteed > to be persistent across reboot or kernel restart and this causes problems > for some tools. E.g. kexec tools use these ids to identify NIC on kdump. > Fix the issue by using if_instance from