From: Mark Brown <broonie@kernel.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will.deacon@arm.com, arnd@arndb.de, mingo@redhat.com,
rostedt@goodmis.org, akpm@linux-foundation.org
Subject: Re: [RFC PATCH 3/3] arm64: add a new config option KTEST_RUNNABLE
Date: Thu, 13 Dec 2018 15:18:23 +0000 [thread overview]
Message-ID: <20181213151823.GK10669@sirena.org.uk> (raw)
In-Reply-To: <20181213122910.24193-4-anders.roxell@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
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).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-13 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 12:29 [RFC PATCH 0/3] Make allmodconfig boot in qemu-arm64 Anders Roxell
2018-12-13 12:29 ` [RFC PATCH 1/3] config: provide a fragment to enable gdb for qemu Anders Roxell
2018-12-13 12:40 ` Mark Brown
2018-12-18 8:45 ` Anders Roxell
2018-12-18 9:07 ` Arnd Bergmann
2018-12-18 13:29 ` Mark Brown
2018-12-13 12:29 ` [RFC PATCH 2/3] lib/ubsan: default UBSAN_ALIGNMENT to not set Anders Roxell
2018-12-13 12:29 ` [RFC PATCH 3/3] arm64: add a new config option KTEST_RUNNABLE Anders Roxell
2018-12-13 15:18 ` Mark Brown [this message]
2019-01-07 14:39 ` Mark Rutland
2019-01-07 14:43 ` Mark Rutland
2019-01-07 17:55 ` Mark Brown
2019-01-07 17:59 ` Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181213151823.GK10669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®