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?
-- Michael
On Sun, Mar 4, 2012 at 11:02 PM, Michael Hope michael.hope@linaro.orgwrote:
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?
On Tue, Mar 6, 2012 at 12:45 AM, Alexander Sack asac@linaro.org wrote:
On Sun, Mar 4, 2012 at 11:02 PM, Michael Hope michael.hope@linaro.org 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.
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.
-- Michael
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.
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.
Rob
On Tue, 2012-03-06 at 08:50 -0600, Rob Herring wrote:
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.
Linaro's Android release for VExpress as be using Pawel's device tree patches for several months to provide a single image which works on A9, A15 and A5 CoreTiles. We haven't do this yet for Ubuntu because hardware pack and media create tools don't yet support this.
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.
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.
Where are the Device Trees hosted?
-- Michael
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
On Wed, 2012-03-07 at 08:23 +1300, Michael Hope wrote:
On Wed, Mar 7, 2012 at 3:50 AM, Rob Herring robherring2@gmail.com wrote:
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.
They should go in Linus 3.4 (though I can't find them in the arm-soc branch). The author's git repo is at: http://linux-arm.org/git?p=arm-dts.git%3Ba=tree%3Bh=refs/heads/master%3Bhb=m...
The ARM Landing Team also have versions of these patches in their trees.
Where are the Device Trees hosted?
Device trees for real hardware A5, A9 and A15 are in the same patches which submit device tree support. The above repo additionall has a device tree for RTSM.
On Wed, 2012-03-07 at 06:42 +0000, Jon Medhurst (Tixy) wrote:
On Wed, 2012-03-07 at 08:23 +1300, Michael Hope wrote:
On Wed, Mar 7, 2012 at 3:50 AM, Rob Herring robherring2@gmail.com wrote:
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.
They should go in Linus 3.4 (though I can't find them in the arm-soc branch).
VExpress device trees _are_ in the arm-soc tree ready for 3.4... http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git%3Ba=commit%3Bh=fdc...
Dnia 2012-03-06, wto o godzinie 14:50 +0000, Rob Herring pisze:
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.
Yes - the DT4VE will be (hopefully :-) merged in 3.4, but is already available in LT kernel and in arm-soc repo. Single zImage can be used to boot V2P-CA9, V2P-CA5s, V2P-CA15 (this platform is a bit unstable though, and I haven't tried LPAE configuration yet), FPGA board with A7 setup and RTSM_VE-AEMv7 model. The coretile DTSes are available in kernel, the rest live in our http://linux-arm.org/git?p=arm-dts.git DTS repo (there will be more as I get them working on other models).
The current main problem is CLCD driver DT support, or rather lack of it, but this is the first thing I'll take care of as soon as I can (I'm out of office this week, so I may replay to emails with substantial delay)
Cheers!
Paweł
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-
Alexander Sack -
Jon Medhurst (Tixy) -
Michael Hope -
Pawel Moll -
Rob Herring