On Fri, 15 Jan 2021 10:02:04 +
Peter Maydell wrote:
> On Thu, 14 Jan 2021 at 23:48, Igor Mammedov wrote:
> >
> > Add documentation for '-machine memory-backend' CLI option and
> > how to use it.
> >
> > And document that x-use-canonical-path-for-ramblock-id,
> > is considered to be stable
On Fri, 15 Jan 2021 10:36:05 +0100
Michal Privoznik wrote:
> On 1/15/21 12:46 AM, Igor Mammedov wrote:
> > Add documentation for '-machine memory-backend' CLI option and
> > how to use it.
> >
> > And document that x-use-canonical-path-for-ramblock-id,
> > is considered to be stable to make
On Fri, Jan 15, 2021 at 11:43:10 +0100, Peter Krempa wrote:
> On Fri, Jan 15, 2021 at 10:02:04 +, Peter Maydell wrote:
> > On Thu, 14 Jan 2021 at 23:48, Igor Mammedov wrote:
[...]
> Removing the 'x-' will fix it only starting with qemu-6.0 and any
> downstream which backports the removal of
On Fri, Jan 15, 2021 at 10:02:04 +, Peter Maydell wrote:
> On Thu, 14 Jan 2021 at 23:48, Igor Mammedov wrote:
> >
> > Add documentation for '-machine memory-backend' CLI option and
> > how to use it.
> >
> > And document that x-use-canonical-path-for-ramblock-id,
> > is considered to be
On Thu, 14 Jan 2021 at 23:48, Igor Mammedov wrote:
>
> Add documentation for '-machine memory-backend' CLI option and
> how to use it.
>
> And document that x-use-canonical-path-for-ramblock-id,
> is considered to be stable to make sure it won't go away by accident.
That's not what the x- prefix
On 1/15/21 12:46 AM, Igor Mammedov wrote:
Add documentation for '-machine memory-backend' CLI option and
how to use it.
And document that x-use-canonical-path-for-ramblock-id,
is considered to be stable to make sure it won't go away by accident.
Signed-off-by: Igor Mammedov
---
v2:
- add
Add documentation for '-machine memory-backend' CLI option and
how to use it.
And document that x-use-canonical-path-for-ramblock-id,
is considered to be stable to make sure it won't go away by accident.
Signed-off-by: Igor Mammedov
---
v2:
- add doc that x-use-canonical-path-for-ramblock-id
