On Tue, 25 Nov 2025 at 14:56, Alex Bennée <[email protected]> wrote: > > Peter Maydell <[email protected]> writes: > > @@ -85,6 +84,10 @@ shown below: > > The memory address where the file should be loaded. This is required > > for raw images and ignored for non-raw files. > > > > + Note that as usual with QEMU numeric option values, the default is to > > + treat the argument as decimal. To specify a value in hex, prefix it > > + with '0x'. > > + > > ``<cpu-num>`` > > This specifies the CPU that should be used. This is an > > optional argument with two effects: > > @@ -104,10 +107,6 @@ shown below: > > This can be used to load supported executable formats as if they > > were raw. > > > > -All values are parsed using the standard QemuOpts parsing. This allows the > > user > > -to specify any values in any format supported. By default the values > > -will be parsed as decimal. To use hex values the user should prefix the > > number > > -with a '0x'. > > > > An example of loading an ELF file which CPU0 will boot is shown below:: > > This isn't wrong but I wonder if there is a way to avoid so much > repetition? Is there a way to have common footnotes we could apply > anywhere we are discussing QEMU's numeric parsing?
Mmm, I wasn't thrilled by the repetition, but at least this way the info is in the user's face where they'll see it when they're looking at how to set the address, rather than tucked away at the bottom or behind a footnote link where they might not read it. In a lot of cases it's not something we need to mention at all -- nobody expects the argument to "-smp" to be hex, for instance :-) -- PMM
