Re: [Xen-devel] [PATCH] xen-blkfront: export backend vdev name via sysfs

2016-06-09 Thread Olaf Hering
On Thu, Jun 09, David Vrabel wrote: > Why don't you get the udev rule to read the xenstore key directly instead? Good point. Something like this does indeed work: c170:~ # cd -P /sys/block/xvda/device ; d=${PWD##*/} ; xenstore-read `xenstore-read device/${d/-/\/}/backend`/dev hda c170:/sys/devi

Re: [Xen-devel] [PATCH] xen-blkfront: export backend vdev name via sysfs

2016-06-09 Thread David Vrabel
On 09/06/16 17:43, Olaf Hering wrote: > From: Jeff Mahoney > > This patch creates a sysfs group to export blkfront attribute via sysfs. > For now, we just export the backend device name. > > This helps with migrating existing domU installation from a xenlinux > based kernel to a pvops based kern

Re: [Xen-devel] [PATCH] xen-blkfront: export backend vdev name via sysfs

2016-06-09 Thread Olaf Hering
On Thu, Jun 09, Olaf Hering wrote: > The value of "vdev" is cached to avoid the load caused by constant > rereading from the sysfs file. For some reason I sent an earlier variant of the patch without caching. If the approach is acceptable I will resend. Olaf

[Xen-devel] [PATCH] xen-blkfront: export backend vdev name via sysfs

2016-06-09 Thread Olaf Hering
From: Jeff Mahoney This patch creates a sysfs group to export blkfront attribute via sysfs. For now, we just export the backend device name. This helps with migrating existing domU installation from a xenlinux based kernel to a pvops based kernel. The old blkfront driver did respect the vdev=hd|