On Wed, Jan 30, 2019 at 06:20:10PM +0000, Will Deacon wrote: > On Fri, Jan 25, 2019 at 03:43:08PM +0000, Andre Przywara wrote: > > When loading a firmware instead of a kernel, we can still pass on any > > *user-provided* command line, as /chosen/bootargs is a generic device tree > > feature. We just need to make sure to not pass our mangled-for-Linux > > version. > > > > This allows to run "firmware" images which make use of a command line, > > still are not Linux kernels, like kvm-unit-tests. > > > > Signed-off-by: Andre Przywara <andre.przywara@xxxxxxx> > > --- > > Hi Will, > > > > this goes on top of Julien's firmware series (which did not yet appear > > on kernel.org?) > > This fixes an issue with some kvm-unit-tests support. [1] > > Does kvm-unit-tests break if we pass the modified command line? I'm wary of > passing something different depending on whether the payload is firmware or > kernel, because there's a pretty fine line between the two (and the firmware > may even just forward the thing on to the kernel it loads). > kvm-unit-tests assumes the user or unit test run scripts completely control the kernel command line. The kernel command line is then turned into the command line of the test's main() function, plus the addition of the program name at argv[0]. The unit tests then parse these command line parameters to determine what to do when testing. If additional options are passed we need to teach the tests to ignore them, and there's also risk that something passed in might accidentally match a unit test parameter. Thanks, drew
