[]
I still want to point out my consernes about `unsigned long long long'
bloat.
[]
#v+
olecom@flower:/tmp$ grep '@offset' <extended-crashkernel-cmdline.mbox
crashkernel=<range1>:<size1>[,<range2>:<size2>,...][@offset]
- /* crashkernel=size@offset specifies the size to reserve for a crash
+While the "crashkernel=size[@offset]" syntax is sufficient for most
+ crashkernel=<range1>:<size1>[,<range2>:<size2>,...][@offset]
+ crashkernel=range1:size1[,range2:size2,...][@offset]
olecom@flower:/tmp$ grep '@base' <extended-crashkernel-cmdline.mbox
+ * crashkernel=size[@base]
olecom@flower:/tmp$ grep '@<base' <extended-crashkernel-cmdline.mbox
+ * crashkernel=<ramsize-range>:<size>[,...][@<base>]
olecom@flower:/tmp$ grep '@<offset' <extended-crashkernel-cmdline.mbox
olecom@flower:/tmp$
#v-
memparse(), as a wrapper for somple_strtoll(), always have a return value
(zero by default).
<http://article.gmane.org/gmane.linux.kernel/583426>
Consider coded error path now, please.
And why not to make overall result reliable? This is kernel after all.
I.e. if there's valid `crashkernel=' option, but some parsing errors, why
not to apply some heuristics with warning in syslog, if user have some
conf, bootloader (random) errors, but feature still works?
--
-o--=O`C
#oo'L O
<___=E M
-