Re: [Qemu-devel] [PATCH v4 17/24] memory-device: add class function get_device_id()

2018-10-01 Thread David Hildenbrand
On 30/09/2018 18:19, Auger Eric wrote: > Hi David, > > On 9/26/18 11:42 AM, David Hildenbrand wrote: >> When reporting the id of virtio-based memory devices, we always have to >> take the one of the proxy device (parent), not the one of the memory >> device directly. >> >> Let's generalize this by

Re: [Qemu-devel] [PATCH v4 17/24] memory-device: add class function get_device_id()

2018-09-30 Thread Auger Eric
Hi David, On 9/26/18 11:42 AM, David Hildenbrand wrote: > When reporting the id of virtio-based memory devices, we always have to > take the one of the proxy device (parent), not the one of the memory > device directly. > > Let's generalize this by allowing memory devices to specify an optional >

Re: [Qemu-devel] [PATCH v4 17/24] memory-device: add class function get_device_id()

2018-09-27 Thread Igor Mammedov
On Wed, 26 Sep 2018 11:42:12 +0200 David Hildenbrand wrote: > When reporting the id of virtio-based memory devices, we always have to > take the one of the proxy device (parent), not the one of the memory > device directly. > > Let's generalize this by allowing memory devices to specify an optio

[Qemu-devel] [PATCH v4 17/24] memory-device: add class function get_device_id()

2018-09-26 Thread David Hildenbrand
When reporting the id of virtio-based memory devices, we always have to take the one of the proxy device (parent), not the one of the memory device directly. Let's generalize this by allowing memory devices to specify an optional "get_device_id" function. This id can then be used to report errors