On 03/06/2012 01:23 PM, Michael Hope wrote:
On Wed, Mar 7, 2012 at 3:50 AM, Rob Herring robherring2@gmail.com wrote:
On 03/04/2012 04:02 PM, Michael Hope wrote:
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.
Except LPAE and non-LPAE will be 2 different builds... At least you will be able to run the same non-LPAE kernel build on both.
Hardware virtualisation requires LPAE and we're planning on LPAE in the guest to match.
Good, but both types of guests will be supported I presume.
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?
DT support for vexp A9 is going into 3.4 I believe. Pawel has been working on it and can probably give details on A15 support. A single kernel for these 2 platforms (and A7 as well) is much simpler than getting to a single zImage in general (i.e. omap plus i.mx). But we'll be a lot closer in 3.4.
Linus 3.4 or the Landing Team 3.4? From other emails it seems that the work may be more on the packaging side.
Linus 3.4. I don't follow Linaro kernels, but sounds like support is already there in the kernel at least.
Where are the Device Trees hosted?
Generally, in the kernel in arch/arm/boot/dts.
Rob