|
|
|
|
|
|
|
|
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] FW: IA-64 serial driver
> > How about using "xenconsole=" and "xencom2=" to differentiate
> > from the dom0 xenlinux command line parameters? Then there
> > won't be an ordering constraint (which as you point out could
> > lead to a common problem).
>
> The parameter names and the command-line parser are not
> arch-specific,
> so this would be quite hard to do.
I have to admit I am not familiar with the driver code, but
isn't it simply adding another string_param line (as an
alias for console= not a replacement) and an additional
strncmp test in init_console?
> An alternative might be to
> specify a
> shared command line in the form:
> "xen(<xen params here>) dom0(<dom0 params here>)"
> Then, in your ia64 start-of-day code you pull the shared command line
> out into two separate strings: the first you pass off to
> cmdline_parse() and the second you pass off to domain0.
>
> I think this is a cleaner format and will have a cleaner
> implementation.
Yes, I suppose you are right, though I shudder to think about
all the "my configuration doesn't work anymore" questions.
I guess those will happen regardless of how we do it.
Perhaps we could/should use
the "--" separator like grep (and getopts?) uses, e.g.
console=xxx com2=yyy -- console=zzz com2=www nomca
^ xen arguments ^ ^ dom0 arguments^
What do you think Kevin? Want to spin a patch for this?
Thanks,
Dan
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
|
|