Re: [PATCH] machine: do not crash if default RAM backend name has been stollen

2023-06-10 Thread Thomas Huth
On 09/06/2023 16.06, Igor Mammedov wrote: On Mon, 22 May 2023 15:17:17 +0200 Igor Mammedov wrote: Paolo, can you pick it up? It's merged already (commit a37531f2381c4e294e48b14170894741283) Cheers, Thomas

Re: [PATCH] machine: do not crash if default RAM backend name has been stollen

2023-06-09 Thread Igor Mammedov
On Mon, 22 May 2023 15:17:17 +0200 Igor Mammedov wrote: Paolo, can you pick it up? > 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. > >

Re: [PATCH] machine: do not crash if default RAM backend name has been stollen

2023-05-23 Thread Thomas Huth
s/stollen/stolen/ in the subject On 22/05/2023 15.17, Igor Mammedov wrote: 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

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

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

Re: [PATCH] machine: do not crash if default RAM backend name has been stollen

2023-05-23 Thread Shaoqin Huang
With the patch, qemu exits normally instead of Aborted. On 5/22/23 21:17, Igor Mammedov wrote: 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.

Re: [PATCH] machine: do not crash if default RAM backend name has been stollen

2023-05-22 Thread Philippe Mathieu-Daudé
On 22/5/23 15:17, Igor Mammedov wrote: 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

[PATCH] machine: do not crash if default RAM backend name has been stollen

2023-05-22 Thread Igor Mammedov
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.ram,size=4294967296 Actual