On 7 May 2013 16:52, Christopher Covington <cov@xxxxxxxxxxxxxx> wrote: > On 05/07/2013 08:19 AM, Peter Maydell wrote: >> 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? > > arm64 uses a kernel argument. This mixes up "information that the user provides to the kernel" (ie configuration) with "information that QEMU or kvmtool should provide to the kernel" (ie hardware description), and would require QEMU/kvmtool to parse the user's commandline tool to figure out if they needed to override it or edit it (or alternatively, would require the user to know internal details of QEMU/kvmtool's address map for the guest). I think it would be nicer to keep them separate. thanks -- PMM _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
