| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 7 May 2013 13:19:46 +0100 From: Peter Maydell <peter.maydell@...aro.org> To: Rusty Russell <rusty@...tcorp.com.au> Cc: Alexander Graf <agraf@...e.de>, Pranavkumar Sawargaonkar <pranavkumar@...aro.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>, "patches@...aro.org" <patches@...aro.org>, "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>, "kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>, Amit Shah <amit.shah@...hat.com> Subject: Re: [PATCH 0/2] Early printk support for virtio console devices. On 7 May 2013 05:46, Rusty Russell <rusty@...tcorp.com.au> wrote: > Peter Maydell <peter.maydell@...aro.org> writes: >> That all looks like sensible QEMU implementation possibilities >> but it seems to be a bit of a non-sequitur from "how do we >> tell the kernel to actually use this?" > > You enable the feature in the virtio console device, and a kernel > compiled with EARLY_PRINTK will use it? Well, at the moment EARLY_PRINTK is hardcoded to "use some specific UART or equivalent selected at compile time". So the equivalent presumably would be to hard-compile "use virtio-console", but then how does that code know where the virtio-console is in the address space? -- PMM -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists