[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] kexec: allow relaxed placement specification via command line

>>> On 31.05.16 at 12:24, <andrew.cooper3@xxxxxxxxxx> wrote:
> On 30/05/16 14:48, Jan Beulich wrote:
>> Rather than just allowing a fixed address or fully automatic placement,
>> also allow for specifying an upper bound. Especially on EFI systems,
>> where firmware memory use is commonly less predictable than on legacy
>> BIOS ones, this makes success of the reservation more likely when
>> automatic placement is not an option (e.g. because of special DMA
>> restrictions of devices involved in actually carrying out the dump).
>> Also take the opportunity to actually add text to the "crashkernel"
>> entry in the command line option doc.
>> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
>> --- a/docs/misc/xen-command-line.markdown
>> +++ b/docs/misc/xen-command-line.markdown
>> @@ -458,7 +458,18 @@ Specify the maximum address to allocate
>>  combination with the `low_crashinfo` command line option.
>>  ### crashkernel
>> -> `= <ramsize-range>:<size>[,...][@<offset>]`
>> +> `= <ramsize-range>:<size>[,...][{@,<}<offset>]`
>> +> `= <size>[{@,<}<offset>]`
>> +
>> +Specify sizes and optionally placement of the kexec reservation area.
>> +The `<ramsize-range>:<size>' pairs indicate how much memory to set
> For markdown, you need to use matching ` ` pairs for formatting the
> containing text as monospace.

Oh, okay. I meant to copy what was there, and now I see that
I didn't look right. Fixed.

> Other than this, Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

Thanks, Jan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.