From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Deacon Subject: Re: [PATCH kvmtool] arm: Allow command line for firmware Date: Wed, 30 Jan 2019 18:20:10 +0000 Message-ID: <20190130182010.GE18558@fuggles.cambridge.arm.com> References: <20190125154308.185131-1-andre.przywara@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org To: Andre Przywara Return-path: Content-Disposition: inline In-Reply-To: <20190125154308.185131-1-andre.przywara@arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu List-Id: kvm.vger.kernel.org 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 > --- > 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). Will