Single zImage and KVM
michael.hope at linaro.org
Mon Mar 5 20:47:44 UTC 2012
On Tue, Mar 6, 2012 at 12:45 AM, Alexander Sack <asac at linaro.org> wrote:
> On Sun, Mar 4, 2012 at 11:02 PM, Michael Hope <michael.hope at linaro.org>
>> I'd like to have one KVM kernel image which is suitable for the real
>> hardware host and the virtio based guest. The single zImage plus
>> Device Tree work seem like a great way to do this.
>> We're currently using the vexpress-a15 on a Fast Model as the host and
>> a vexpress-a15 as the guest. Device Tree support is required to
>> describe the virtio-mmio devices. As a bonus, the vexpress-a9 and
>> vexpress-a15 are the same hardware with a different memory map and can
>> help demonstrate the Device Tree support.
>> What are the plans for single zImage? Where does the vexpress-a15 fit
>> in with that? Could I bump it to the front of the list?
> single zImage is already used for describing our final goal of having a
> single zImage for all boards... I think there is some way to go for that
> (especially since we do not yet have a single source tree). For stuff that
> can be tweaked through DT right now, I don't see why we couldn't have a
> single zImage ... e.g. like in your case having ability to boot vexpress-a15
> in two different setups through different device tree...
> Most likely would require some platform plumming to ship two or more DTs for
> one kernel.
> What do we need for that? I guess we need a way to have two different device
> trees produced into the same image/hwpack and make it easy to decide at
> deploy time what u-boot is supposed to select?
Good point on Device Tree. We'll do the same as x86 when starting the
guest which is to pass the kernel, initrd, and (now) Device Tree
directly to QEMU.
We'll still need a vexpress-a15 hardware pack. This is mainly for
testing and won't be released so a name like 'vexpress-kvm' might be
better to prevent confusion - it's not coming from a Linaro tree and
isn't supported on the real vexpress-a15.
More information about the linaro-dev