Re: [RFC PATCH] Describe chosen modules for hypervisor booting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Mon, Apr 24, 2023 at 7:57 AM Alex Bennée <alex.bennee@xxxxxxxxxx> wrote:
>
>
> Rob Herring <robh@xxxxxxxxxx> writes:
>
> > On Fri, Apr 21, 2023 at 11:40 AM Alex Bennée <alex.bennee@xxxxxxxxxx> wrote:
> >>
> >> When booting something like a hypervisor there is need to communicate
> >> to it how the first guest will be loaded. Typically the firmware or
> >> boot loader will put the kernel and ramdisk in memory and pass the
> >> information to the hypervisors boot code. This mechanism currently
> >> works with Xen on the Arm platform and would be equally applicable to
> >> other such hypervisors.
> >
> > This is probably something to discuss on the boot-architecture list.
> >
> >>
> >> However this specification doesn't address the needs of a dom0less
> >> system (where there is no "root" guest to launch the others) so is
> >> currently very much an RFC.
> >
> > In the end, whatever you want to add will need a DT schema. Really,
> > just a schema would be fine. Much of /chosen is not in the spec.
>
> Where are these schema's stored?

Next door to the spec[1].

Rob

[1] https://github.com/devicetree-org/dt-schema




[Index of Archives]     [Device Tree]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Photos]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]

  Powered by Linux