Re: The madness of ad hoc special IDs (was: [PATCH] machine: do not crash if default RAM backend name has been stollen)

2023-05-23 Thread Thomas Huth
On 23/05/2023 14.31, Markus Armbruster wrote: ... To stop creating more moles, we need to reserve IDs for the system's use, and let the system pick only reserved IDs going forward. Just something to add here: We already have a function for generating internal IDs, the id_generate() function in

Re: The madness of ad hoc special IDs (was: [PATCH] machine: do not crash if default RAM backend name has been stollen)

2023-05-23 Thread Igor Mammedov
On Tue, 23 May 2023 14:31:30 +0200 Markus Armbruster wrote: > Igor Mammedov writes: > > > QEMU aborts when default RAM backend should be used (i.e. no > > explicit '-machine memory-backend=' specified) but user > > has created an object which 'id' equals to default RAM backend > > name used by

The madness of ad hoc special IDs (was: [PATCH] machine: do not crash if default RAM backend name has been stollen)

2023-05-23 Thread Markus Armbruster
Igor Mammedov writes: > QEMU aborts when default RAM backend should be used (i.e. no > explicit '-machine memory-backend=' specified) but user > has created an object which 'id' equals to default RAM backend > name used by board. > > $QEMU -machine pc \ >-object memory-backend-ram,id=pc.