[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190107143924.GA46743@lakrids.cambridge.arm.com>
Date: Mon, 7 Jan 2019 14:39:24 +0000
From: Mark Rutland <mark.rutland@....com>
To: Mark Brown <broonie@...nel.org>
Cc: Anders Roxell <anders.roxell@...aro.org>,
linux-kernel@...r.kernel.org, catalin.marinas@....com,
will.deacon@....com, arnd@...db.de, mingo@...hat.com,
rostedt@...dmis.org, akpm@...ux-foundation.org
Subject: Re: [RFC PATCH 3/3] arm64: add a new config option KTEST_RUNNABLE
On Thu, Dec 13, 2018 at 03:18:23PM +0000, Mark Brown wrote:
> On Thu, Dec 13, 2018 at 01:29:10PM +0100, Anders Roxell wrote:
>
> > With this new config option, we can boot a allmodconfig kernel in qemu.
> > Config options SERIAL_AMBA_PL011, SERIAL_AMBA_PL011_CONSOLE, UNIX needs
> > to be enabled in order to get a console. Options like CPU_BIG_ENDIAN,
> > CMDLINE_FORCE, CMDLINE_OVERRIDE and HVC_DCC needs to be disabled.
>
> Does ktest really not run with BIG_ENDIAN?
>
> > +config KTEST_RUNNABLE
> > + bool "Test build kernels that run in qemu for ktest"
> > + select SERIAL_AMBA_PL011
> > + select SERIAL_AMBA_PL011_CONSOLE
> > + select UNIX
>
> The opposite angle for my question on patch 1 I guess but is this really
> a generic thing for running ktest? It seems like it's specific to qemu
> (and other systems which have the PL011 as the console serial port).
This is definitely platform-specific rather than ktest specific.
If I wanted to run ktest in a kvmtool VM, I would not need PL011 at all,
since that uses 8250 and virtio-console.
Thanks,
Mark.
Powered by blists - more mailing lists