[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH RFC 1/2] drivers/base: export lock_device_hotplug/unlock_device_hotplug
- To: David Hildenbrand <david@xxxxxxxxxx>
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Aug 2018 19:02:39 +0200
- Cc: Michal Hocko <mhocko@xxxxxxxx>, "Rafael J. Wysocki" <rafael@xxxxxxxxxx>, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, Heiko Carstens <heiko.carstens@xxxxxxxxxx>, Linux Memory Management List <linux-mm@xxxxxxxxx>, Paul Mackerras <paulus@xxxxxxxxx>, linux-s390@xxxxxxxxxxxxxxx, sthemmin@xxxxxxxxxxxxx, Pavel Tatashin <pasha.tatashin@xxxxxxxxxx>, ACPI Devel Maling List <linux-acpi@xxxxxxxxxxxxxxx>, David Rientjes <rientjes@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, Len Brown <lenb@xxxxxxxxxx>, haiyangz@xxxxxxxxxxxxx, Dan Williams <dan.j.williams@xxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Vlastimil Babka <vbabka@xxxxxxx>, osalvador@xxxxxxx, "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Martin Schwidefsky <schwidefsky@xxxxxxxxxx>, devel@xxxxxxxxxxxxxxxxxxxxxx, Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>, linuxppc-dev <linuxppc-dev@xxxxxxxxxxxxxxxx>
- Delivery-date: Fri, 17 Aug 2018 17:03:10 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Fri, Aug 17, 2018 at 01:56:35PM +0200, David Hildenbrand wrote:
> E.g. When adding the memory block devices, we know that there won't be a
> driver to attach to (as there are no drivers for the "memory" subsystem)
> - the bus_probe_device() function that takes the device_lock() could
> pretty much be avoided for that case. But burying such special cases
> down in core driver code definitely won't make locking related to memory
> hotplug easier.
You don't have to have a driver for a device if you don't want to, or
you can just have a default one for all memory devices if you somehow
need it. No reason to not do this if it makes things easier for you.
thanks,
greg k-h
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
