Re: making a qdev bus available from a (non-qtree?) device

2021-05-21 Thread Klaus Jensen
On May 21 09:33, Markus Armbruster wrote: I'm about to drop off for two weeks of much-needed vacation. I meant to study your explanation and give design advice before I leave, but I'm out of time. Regrettable. I hope Stefan can help you. Or perhaps Paolo. If you still have questions when

Re: making a qdev bus available from a (non-qtree?) device

2021-05-21 Thread Markus Armbruster
I'm about to drop off for two weeks of much-needed vacation. I meant to study your explanation and give design advice before I leave, but I'm out of time. Regrettable. I hope Stefan can help you. Or perhaps Paolo. If you still have questions when I'm back, feel free to contact me again.

Re: making a qdev bus available from a (non-qtree?) device

2021-05-17 Thread Stefan Hajnoczi
On Mon, May 17, 2021 at 08:55:50AM +0200, Klaus Jensen wrote: > On May 13 15:02, Stefan Hajnoczi wrote: > > On Wed, May 12, 2021 at 02:02:50PM +0200, Markus Armbruster wrote: > > > Klaus Jensen writes: > > > > I can then call `qdev_set_parent_bus()` and set the parent bus to the > > > > bus

Re: making a qdev bus available from a (non-qtree?) device

2021-05-17 Thread Klaus Jensen
On May 13 15:02, Stefan Hajnoczi wrote: On Wed, May 12, 2021 at 02:02:50PM +0200, Markus Armbruster wrote: Klaus Jensen writes: > I can then call `qdev_set_parent_bus()` and set the parent bus to the > bus creates in the nvme-subsys device. This solves the problem since > the namespaces are

Re: making a qdev bus available from a (non-qtree?) device

2021-05-17 Thread Klaus Jensen
On May 12 14:02, Markus Armbruster wrote: Klaus Jensen writes: Hi all, I need some help with grok'ing qdev busses. Stefan, Michael - David suggested on IRC that I CC'ed you guys since you might have solved a similar issue with virtio devices. I've tried to study how that works, but I'm not

Re: making a qdev bus available from a (non-qtree?) device

2021-05-13 Thread Stefan Hajnoczi
On Wed, May 12, 2021 at 02:02:50PM +0200, Markus Armbruster wrote: > Klaus Jensen writes: > > I can then call `qdev_set_parent_bus()` and set the parent bus to the > > bus creates in the nvme-subsys device. This solves the problem since > > the namespaces are not "garbage collected" when the nvme

Re: making a qdev bus available from a (non-qtree?) device

2021-05-12 Thread Markus Armbruster
Klaus Jensen writes: > Hi all, > > I need some help with grok'ing qdev busses. Stefan, Michael - David > suggested on IRC that I CC'ed you guys since you might have solved a > similar issue with virtio devices. I've tried to study how that works, > but I'm not exactly sure how to apply it to

Re: making a qdev bus available from a (non-qtree?) device

2021-05-12 Thread Peter Maydell
On Wed, 12 May 2021 at 04:39, Philippe Mathieu-Daudé wrote: > IIUC, while we can have unattached drives, we can't (by design) have > qdev unattached to qbus. You can (and we do), but it is a bit of a problem because a device not attached to a qbus will not get automatically reset, and so you

Re: making a qdev bus available from a (non-qtree?) device

2021-05-11 Thread Philippe Mathieu-Daudé
On 5/11/21 8:17 PM, Klaus Jensen wrote: > Hi all, > > I need some help with grok'ing qdev busses. Stefan, Michael - David > suggested on IRC that I CC'ed you guys since you might have solved a > similar issue with virtio devices. I've tried to study how that works, > but I'm not exactly sure how

making a qdev bus available from a (non-qtree?) device

2021-05-11 Thread Klaus Jensen
Hi all, I need some help with grok'ing qdev busses. Stefan, Michael - David suggested on IRC that I CC'ed you guys since you might have solved a similar issue with virtio devices. I've tried to study how that works, but I'm not exactly sure how to apply it to the issue I'm having.