On Fri, Jun 5, 2020 at 5:16 PM Corey Minyard <[email protected]> wrote:
>
> On Fri, Jun 05, 2020 at 07:55:37PM +0000, Stewart Hildebrand wrote:
> > + Corey
> >
> > On Friday, June 5, 2020 3:19 PM, Bruce Ashfield wrote:
> > >On Fri, Jun 5, 2020 at 3:12 PM Stewart Hildebrand wrote:
> > >> On Thursday, June 4, 2020 5:13 PM, Christopher Clark wrote:
> > >> > Hello Siddhartha,
> > >> >
> > >> > I am also interested in running Xen on the Raspberry Pi 4. I hope to 
> > >> > have time next week to be able to look into it.
> > >> >
> > >> > Christopher
> > >> >
> > >> >
> > >> >> On Jun 4, 2020, at 5:05 AM, Siddhartha V wrote:
> > >> >>
> > >> >> Hello dear meta-virtualization team,
> > >> >> I am building the xen minimal image using yocto warrior ("bitbake 
> > >> >> xen-image-minimal") by giving the target machine as
> > >"raspberrypi4".
> > >>
> > >> Corey Minyard created a layer for Xen on Raspberry Pi 4 here 
> > >> https://github.com/MontaVista-OpenSourceTechnology/meta-
> > >raspberrypi-xen
> > >>
> > >
> > >Someone needs to lean on them to get patches submitted to meta-virt.
> >
> > Corey: you are hereby encouraged to submit patches to meta-virtualization.
>
> Ok.  The layer has the following basic pieces:
>
> 1 The xen patches for the Pi4, just a few patches.  As the Xen group
>   fixes things, I keep adding :).
> 2 Hacks for getting the Pi4 kernel config right for xen.  This should go
>   away if you don't use the kernel from the Pi4 yocto layer, as it
>   doesn't work like most kernels in yocto.

I should take a look at the configs and see if I can create a fragment
or two, but I can take care of that.

> 3 The addition of xen-tools.  This seems somewhat controversial from a
>   naming point of view, at least.  But all the major distros seem to
>   have it, and it does make things easier.  It brings along a boatload
>   of perl recipes.
> 4 Something to make bridges easier to manage.  Distros have another tool
>   to do this (bridge-utils), but that ties into systemd/initd and would
>   have been rather complex to integrate into yocto.  Plus it requires
>   rebooting to change anything.  The one I created is far simpler and
>   works just as well, maybe better.
> 5 A few Pi-specific hacks for config and u-boot.
>
> 1 is a no brainer, and 2 shouldn't matter in the future.  I guess the
> questionable ones are 3 and 4.

Christopher might have a better idea about #3, but if the
functionality is useful, I'm all for having it close to the other Xen
components.

We've put similar things like #4 into the layer before. Witness
cgroups-lite and some of the other semi-custom and more lightweight
things. But yah, just a judgement call if they may or may not be
useful in other scenarios.

#5 does sound like BSP stuff. Is any of it destined for the rpi layers
? Or is it both rpi AND xen specific, so doesn't really make sense
there either ?

Thanks for the info, most appreciated.

Bruce

>
> -corey
>
> >
> > >Having a layer like that, with fixes missing from meta-virt, makes no 
> > >sense.
> > >
> > >Bruce
> >
> > meta-virtualization seems to be using Xen 4.12 at the moment.
> >
> > Corey's meta-raspberrypi-xen layer uses Xen 4.13. The Xen patches are based 
> > on Xen 4.13. Between Xen 4.12 and 4.13 there are a few additional patches 
> > that are required for running on Raspberry Pi 4.
> >
> > Would you rather uprev meta-virtualization to Xen 4.13, or backport the 
> > patches and identify additional backports required for running Xen 4.12 on 
> > Raspberry Pi 4?
> >
> > Stew



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5393): 
https://lists.yoctoproject.org/g/meta-virtualization/message/5393
Mute This Topic: https://lists.yoctoproject.org/mt/74701134/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to