UM-Linux compilation on Android Common Kernels

UM-Linux compilation on Android Common Kernels

[Elliot Berman]

Hello there,

Qualcomm recently caught some build errors in UM-Linux on Android Common 
Kernel. Todd suggested that these errors might be catchable by 0day. Can 
UM-Linux compilation be enabled for Android Common Kernels?

ARCH=um SUBARCH=x86_64

Thanks,
Elliot

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

On Wed, Aug 17, 2022 at 10:51 AM Elliot Berman <quic_eberman@quicinc.com>
wrote:

> Hello there,
>
> Qualcomm recently caught some build errors in UM-Linux on Android Common
> Kernel. Todd suggested that these errors might be catchable by 0day. Can


I think in this context, I meant "catchable by kernelci".


>
> UM-Linux compilation be enabled for Android Common Kernels?
>
> ARCH=um SUBARCH=x86_64
>

I support this, can we add this test for android kernels? (could limit to
5.10 an higher).


>
> Thanks,
> Elliot
>

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

Ping. Is this possible?

On Wed, Aug 17, 2022 at 11:05 AM Todd Kjos <tkjos@google.com> wrote:
>
>
>
> On Wed, Aug 17, 2022 at 10:51 AM Elliot Berman <quic_eberman@quicinc.com> wrote:
>>
>> Hello there,
>>
>> Qualcomm recently caught some build errors in UM-Linux on Android Common
>> Kernel. Todd suggested that these errors might be catchable by 0day. Can
>
>
> I think in this context, I meant "catchable by kernelci".
>
>>
>>
>> UM-Linux compilation be enabled for Android Common Kernels?
>>
>> ARCH=um SUBARCH=x86_64
>
>
> I support this, can we add this test for android kernels? (could limit to 5.10 an higher).
>
>>
>>
>> Thanks,
>> Elliot

Re: UM-Linux compilation on Android Common Kernels

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

On Wed, Aug 31, 2022 at 11:21:28AM -0700, Todd Kjos via groups.io wrote:
> On Wed, Aug 17, 2022 at 11:05 AM Todd Kjos <tkjos@google.com> wrote:
> > On Wed, Aug 17, 2022 at 10:51 AM Elliot Berman <quic_eberman@quicinc.com> wrote:

> >> Qualcomm recently caught some build errors in UM-Linux on Android Common
> >> Kernel. Todd suggested that these errors might be catchable by 0day. Can

> > I think in this context, I meant "catchable by kernelci".

> >> UM-Linux compilation be enabled for Android Common Kernels?

> >> ARCH=um SUBARCH=x86_64

> > I support this, can we add this test for android kernels? (could limit to 5.10 an higher).

This is definitely technically doable, especially the build side, but
there'd be some work required to enable actually running the kernels and
tests on them.  We discussed this at the weekly meeting today, the main
issue would be finding someone who has the time to do the actual
w.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

Could we start by building but not testing? That at least prevents build
breakage (which is the case that motivated this).

On Thu, Sep 1, 2022 at 6:03 AM Mark Brown <broonie@kernel.org> wrote:

> On Wed, Aug 31, 2022 at 11:21:28AM -0700, Todd Kjos via groups.io wrote:
> > On Wed, Aug 17, 2022 at 11:05 AM Todd Kjos <tkjos@google.com> wrote:
> > > On Wed, Aug 17, 2022 at 10:51 AM Elliot Berman <
> quic_eberman@quicinc.com> wrote:
>
> > >> Qualcomm recently caught some build errors in UM-Linux on Android
> Common
> > >> Kernel. Todd suggested that these errors might be catchable by 0day.
> Can
>
> > > I think in this context, I meant "catchable by kernelci".
>
> > >> UM-Linux compilation be enabled for Android Common Kernels?
>
> > >> ARCH=um SUBARCH=x86_64
>
> > > I support this, can we add this test for android kernels? (could limit
> to 5.10 an higher).
>
> This is definitely technically doable, especially the build side, but
> there'd be some work required to enable actually running the kernels and
> tests on them.  We discussed this at the weekly meeting today, the main
> issue would be finding someone who has the time to do the actual
> w.
>

Re: UM-Linux compilation on Android Common Kernels

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 232 bytes --]

On Thu, Sep 01, 2022 at 08:44:25AM -0700, Todd Kjos wrote:
> Could we start by building but not testing? That at least prevents build
> breakage (which is the case that motivated this).

Yes, that's definitely an easier first step.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

Is there an ETA for at least doing the builds?

On Mon, Sep 5, 2022 at 4:59 AM Mark Brown <broonie@kernel.org> wrote:

> On Thu, Sep 01, 2022 at 08:44:25AM -0700, Todd Kjos wrote:
> > Could we start by building but not testing? That at least prevents build
> > breakage (which is the case that motivated this).
>
> Yes, that's definitely an easier first step.
>

Re: UM-Linux compilation on Android Common Kernels

[Guillaume Tucker]

Hi Todd,

On 14/09/2022 22:36, Todd Kjos via groups.io wrote:
> Is there an ETA for at least doing the builds?

I don't think anyone else is asking for user-mode builds, and
adding this new architecture with a new sub-architecture
parameter is not as trivial as adding a few lines of YAML config.
So unless someone on this list is interested, or someone wants to
run an internship topic around that, I think you'll have to go
and find someone to do the work.

KernelCI is starting to run KUnit which does involve UM-Linux
builds but that's all done "under the hood" by the KUnit
framework.  Still, I guess it would catch some build errors as a
side-effect.  So an alternative is to wait for that to be fully
in production (first half 2023) and we can consider enabling it
on some Android kernel trees.

Best wishes,
Guillaume

> On Mon, Sep 5, 2022 at 4:59 AM Mark Brown <broonie@kernel.org> wrote:
> 
>> On Thu, Sep 01, 2022 at 08:44:25AM -0700, Todd Kjos wrote:
>>> Could we start by building but not testing? That at least prevents build
>>> breakage (which is the case that motivated this).
>>
>> Yes, that's definitely an easier first step.
>>
> 
> 
> 
> 
> 

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

On Thu, Sep 15, 2022 at 9:23 AM Guillaume Tucker <
guillaume.tucker@collabora.com> wrote:

> Hi Todd,
>
> On 14/09/2022 22:36, Todd Kjos via groups.io wrote:
> > Is there an ETA for at least doing the builds?
>
> I don't think anyone else is asking for user-mode builds, and
> adding this new architecture with a new sub-architecture
> parameter is not as trivial as adding a few lines of YAML config.
> So unless someone on this list is interested, or someone wants to
> run an internship topic around that, I think you'll have to go
> and find someone to do the work.
>
> KernelCI is starting to run KUnit which does involve UM-Linux
> builds but that's all done "under the hood" by the KUnit
> framework.  Still, I guess it would catch some build errors as a
> side-effect.  So an alternative is to wait for that to be fully
> in production (first half 2023) and we can consider enabling it
> on some Android kernel trees.
>

Thanks, that would be fine. This is not super urgent.


>
> Best wishes,
> Guillaume
>
> > On Mon, Sep 5, 2022 at 4:59 AM Mark Brown <broonie@kernel.org> wrote:
> >
> >> On Thu, Sep 01, 2022 at 08:44:25AM -0700, Todd Kjos wrote:
> >>> Could we start by building but not testing? That at least prevents
> build
> >>> breakage (which is the case that motivated this).
> >>
> >> Yes, that's definitely an easier first step.
> >>
> >
> >
> > 
> >
> >
>
>

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

On Thu, Sep 15, 2022 at 9:25 AM Todd Kjos <tkjos@google.com> wrote:

>
>
> On Thu, Sep 15, 2022 at 9:23 AM Guillaume Tucker <
> guillaume.tucker@collabora.com> wrote:
>
>> Hi Todd,
>>
>> On 14/09/2022 22:36, Todd Kjos via groups.io wrote:
>> > Is there an ETA for at least doing the builds?
>>
>> I don't think anyone else is asking for user-mode builds, and
>> adding this new architecture with a new sub-architecture
>> parameter is not as trivial as adding a few lines of YAML config.
>> So unless someone on this list is interested, or someone wants to
>> run an internship topic around that, I think you'll have to go
>> and find someone to do the work.
>>
>> KernelCI is starting to run KUnit which does involve UM-Linux
>> builds but that's all done "under the hood" by the KUnit
>> framework.  Still, I guess it would catch some build errors as a
>> side-effect.  So an alternative is to wait for that to be fully
>> in production (first half 2023) and we can consider enabling it
>> on some Android kernel trees.
>>
>
> Thanks, that would be fine. This is not super urgent.
>

Monthly ping...any progress on this?


>
>
>>
>> Best wishes,
>> Guillaume
>>
>> > On Mon, Sep 5, 2022 at 4:59 AM Mark Brown <broonie@kernel.org> wrote:
>> >
>> >> On Thu, Sep 01, 2022 at 08:44:25AM -0700, Todd Kjos wrote:
>> >>> Could we start by building but not testing? That at least prevents
>> build
>> >>> breakage (which is the case that motivated this).
>> >>
>> >> Yes, that's definitely an easier first step.
>> >>
>> >
>> >
>> > 
>> >
>> >
>>
>>

Re: UM-Linux compilation on Android Common Kernels

[Guillaume Tucker]

On 06/07/2023 19:00, Todd Kjos wrote:
> Any progress on this? (at least doing the um builds?)
> 
> On Thu, Mar 16, 2023 at 3:46 PM Todd Kjos <tkjos@google.com <mailto:tkjos@google.com>> wrote:
> 
>     On Thu, Sep 15, 2022 at 9:23 AM Guillaume Tucker
>     <guillaume.tucker@collabora.com <mailto:guillaume.tucker@collabora.com>> wrote:
>     >
>     > Hi Todd,
>     >
>     > On 14/09/2022 22:36, Todd Kjos via groups.io <http://groups.io> wrote:
>     > > Is there an ETA for at least doing the builds?
>     >
>     > I don't think anyone else is asking for user-mode builds, and
>     > adding this new architecture with a new sub-architecture
>     > parameter is not as trivial as adding a few lines of YAML config.
>     > So unless someone on this list is interested, or someone wants to
>     > run an internship topic around that, I think you'll have to go
>     > and find someone to do the work.
>     >
>     > KernelCI is starting to run KUnit which does involve UM-Linux
>     > builds but that's all done "under the hood" by the KUnit
>     > framework.  Still, I guess it would catch some build errors as a
>     > side-effect.  So an alternative is to wait for that to be fully
>     > in production (first half 2023) and we can consider enabling it
>     > on some Android kernel trees.
> 
>     Is this in production now?

No, the timeline for making the new API & Pipeline as the new
production system is basically bumped to 2024.  However, KUnit
jobs are now being run every day on our staging instance and
we're planning to have an "early access" stable instance online
in the next couple of months.  I think we'll get back to you at
that point.

Thank you for your understanding.

Best wishes,
Guillaume

>     > > On Mon, Sep 5, 2022 at 4:59 AM Mark Brown <broonie@kernel.org <mailto:broonie@kernel.org>> wrote:
>     > >
>     > >> On Thu, Sep 01, 2022 at 08:44:25AM -0700, Todd Kjos wrote:
>     > >>> Could we start by building but not testing? That at least prevents build
>     > >>> breakage (which is the case that motivated this).
>     > >>
>     > >> Yes, that's definitely an easier first step.
>     > >>
>     > >
>     > >
>     > > -=-=-=-=-=-=-=-=-=-=-=-
>     > > Groups.io Links: You receive all messages sent to this group.
>     > > View/Reply Online (#1593): https://groups.io/g/kernelci/message/1593 <https://groups.io/g/kernelci/message/1593>
>     > > Mute This Topic: https://groups.io/mt/93087607/924702 <https://groups.io/mt/93087607/924702>
>     > > Group Owner: kernelci+owner@groups.io <mailto:kernelci%2Bowner@groups.io>
>     > > Unsubscribe: https://groups.io/g/kernelci/unsub <https://groups.io/g/kernelci/unsub> [guillaume.tucker@collabora.com <mailto:guillaume.tucker@collabora.com>]
>     > > -=-=-=-=-=-=-=-=-=-=-=-
>     > >
>     > >
>     >
> 

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

On Thu, Jul 13, 2023 at 12:08 AM Guillaume Tucker
<guillaume.tucker@collabora.com> wrote:
>
> On 06/07/2023 19:00, Todd Kjos wrote:
> > Any progress on this? (at least doing the um builds?)
> >
> > On Thu, Mar 16, 2023 at 3:46 PM Todd Kjos <tkjos@google.com <mailto:tkjos@google.com>> wrote:
> >
> >     On Thu, Sep 15, 2022 at 9:23 AM Guillaume Tucker
> >     <guillaume.tucker@collabora.com <mailto:guillaume.tucker@collabora.com>> wrote:
> >     >
> >     > Hi Todd,
> >     >
> >     > On 14/09/2022 22:36, Todd Kjos via groups.io <http://groups.io> wrote:
> >     > > Is there an ETA for at least doing the builds?
> >     >
> >     > I don't think anyone else is asking for user-mode builds, and
> >     > adding this new architecture with a new sub-architecture
> >     > parameter is not as trivial as adding a few lines of YAML config.
> >     > So unless someone on this list is interested, or someone wants to
> >     > run an internship topic around that, I think you'll have to go
> >     > and find someone to do the work.
> >     >
> >     > KernelCI is starting to run KUnit which does involve UM-Linux
> >     > builds but that's all done "under the hood" by the KUnit
> >     > framework.  Still, I guess it would catch some build errors as a
> >     > side-effect.  So an alternative is to wait for that to be fully
> >     > in production (first half 2023) and we can consider enabling it
> >     > on some Android kernel trees.
> >
> >     Is this in production now?
>
> No, the timeline for making the new API & Pipeline as the new
> production system is basically bumped to 2024.  However, KUnit
> jobs are now being run every day on our staging instance and
> we're planning to have an "early access" stable instance online
> in the next couple of months.  I think we'll get back to you at
> that point.

Any update on the schedule for the new API/Pipeline or the "early access"?

>
> Thank you for your understanding.
>
> Best wishes,
> Guillaume
>
> >     > > On Mon, Sep 5, 2022 at 4:59 AM Mark Brown <broonie@kernel.org <mailto:broonie@kernel.org>> wrote:
> >     > >
> >     > >> On Thu, Sep 01, 2022 at 08:44:25AM -0700, Todd Kjos wrote:
> >     > >>> Could we start by building but not testing? That at least prevents build
> >     > >>> breakage (which is the case that motivated this).
> >     > >>
> >     > >> Yes, that's definitely an easier first step.
> >     > >>
> >     > >
> >     > >
> >     > > -=-=-=-=-=-=-=-=-=-=-=-
> >     > > Groups.io Links: You receive all messages sent to this group.
> >     > > View/Reply Online (#1593): https://groups.io/g/kernelci/message/1593 <https://groups.io/g/kernelci/message/1593>
> >     > > Mute This Topic: https://groups.io/mt/93087607/924702 <https://groups.io/mt/93087607/924702>
> >     > > Group Owner: kernelci+owner@groups.io <mailto:kernelci%2Bowner@groups.io>
> >     > > Unsubscribe: https://groups.io/g/kernelci/unsub <https://groups.io/g/kernelci/unsub> [guillaume.tucker@collabora.com <mailto:guillaume.tucker@collabora.com>]
> >     > > -=-=-=-=-=-=-=-=-=-=-=-
> >     > >
> >     > >
> >     >
> >
>

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

On Fri, Mar 1, 2024 at 10:22 AM Gustavo Padovan
<gustavo.padovan@collabora.com> wrote:
>
> Hi Todd,
>
> On 3/1/24 15:15, Todd Kjos wrote:
>
> On Thu, Jul 13, 2023 at 12:08 AM Guillaume Tucker
> <guillaume.tucker@collabora.com> wrote:
>
> On 06/07/2023 19:00, Todd Kjos wrote:
>
> Any progress on this? (at least doing the um builds?)
>
> On Thu, Mar 16, 2023 at 3:46 PM Todd Kjos <tkjos@google.com <mailto:tkjos@google.com>> wrote:
>
>     On Thu, Sep 15, 2022 at 9:23 AM Guillaume Tucker
>     <guillaume.tucker@collabora.com <mailto:guillaume.tucker@collabora.com>> wrote:
>     >
>     > Hi Todd,
>     >
>     > On 14/09/2022 22:36, Todd Kjos via groups.io <http://groups.io> wrote:
>     > > Is there an ETA for at least doing the builds?
>     >
>     > I don't think anyone else is asking for user-mode builds, and
>     > adding this new architecture with a new sub-architecture
>     > parameter is not as trivial as adding a few lines of YAML config.
>     > So unless someone on this list is interested, or someone wants to
>     > run an internship topic around that, I think you'll have to go
>     > and find someone to do the work.
>     >
>     > KernelCI is starting to run KUnit which does involve UM-Linux
>     > builds but that's all done "under the hood" by the KUnit
>     > framework.  Still, I guess it would catch some build errors as a
>     > side-effect.  So an alternative is to wait for that to be fully
>     > in production (first half 2023) and we can consider enabling it
>     > on some Android kernel trees.
>
>     Is this in production now?
>
> No, the timeline for making the new API & Pipeline as the new
> production system is basically bumped to 2024.  However, KUnit
> jobs are now being run every day on our staging instance and
> we're planning to have an "early access" stable instance online
> in the next couple of months.  I think we'll get back to you at
> that point.
>
> Any update on the schedule for the new API/Pipeline or the "early access"?
>
>
> We are enabling the new system as we speak, but slowly with a handful of trees we are building and a handful of tests as a first step. We are also sorting out ways for to share the results, since the new system won't have a web dashboard for the time being.
>
> I am getting to this thread just now, but it seems that for your need, in a first step, would be adding user-mode builds. Is that correct? What would be in your scope after that?

Currently no expectations beyond UM builds. Right now the point is to
catch cases where we might inadvertently break UM since it isn't part
of our workflow, but might be part of the workflow for downstream
users of ACK kernels. We'll make a separate request if we need more
than builds.

>
> Best regards,
>
> Gustavo
>
> --
> Gustavo Padovan
> Kernel Lead
>
> Collabora Ltd.
> Platinum Building, St John's Innovation Park
> Cambridge CB4 0DS, UK
> Registered in England & Wales, no. 5513718

Re: UM-Linux compilation on Android Common Kernels

[Todd Kjos]

On Fri, Mar 1, 2024 at 10:34 AM Gustavo Padovan
<gustavo.padovan@collabora.com> wrote:
>
>
>
> On 3/1/24 15:30, Todd Kjos wrote:
>
> On Fri, Mar 1, 2024 at 10:22 AM Gustavo Padovan
> <gustavo.padovan@collabora.com> wrote:
>
> Hi Todd,
>
> On 3/1/24 15:15, Todd Kjos wrote:
>
> On Thu, Jul 13, 2023 at 12:08 AM Guillaume Tucker
> <guillaume.tucker@collabora.com> wrote:
>
> On 06/07/2023 19:00, Todd Kjos wrote:
>
> Any progress on this? (at least doing the um builds?)
>
> On Thu, Mar 16, 2023 at 3:46 PM Todd Kjos <tkjos@google.com <mailto:tkjos@google.com>> wrote:
>
>     On Thu, Sep 15, 2022 at 9:23 AM Guillaume Tucker
>     <guillaume.tucker@collabora.com <mailto:guillaume.tucker@collabora.com>> wrote:
>     >
>     > Hi Todd,
>     >
>     > On 14/09/2022 22:36, Todd Kjos via groups.io <http://groups.io> wrote:
>     > > Is there an ETA for at least doing the builds?
>     >
>     > I don't think anyone else is asking for user-mode builds, and
>     > adding this new architecture with a new sub-architecture
>     > parameter is not as trivial as adding a few lines of YAML config.
>     > So unless someone on this list is interested, or someone wants to
>     > run an internship topic around that, I think you'll have to go
>     > and find someone to do the work.
>     >
>     > KernelCI is starting to run KUnit which does involve UM-Linux
>     > builds but that's all done "under the hood" by the KUnit
>     > framework.  Still, I guess it would catch some build errors as a
>     > side-effect.  So an alternative is to wait for that to be fully
>     > in production (first half 2023) and we can consider enabling it
>     > on some Android kernel trees.
>
>     Is this in production now?
>
> No, the timeline for making the new API & Pipeline as the new
> production system is basically bumped to 2024.  However, KUnit
> jobs are now being run every day on our staging instance and
> we're planning to have an "early access" stable instance online
> in the next couple of months.  I think we'll get back to you at
> that point.
>
> Any update on the schedule for the new API/Pipeline or the "early access"?
>
>
> We are enabling the new system as we speak, but slowly with a handful of trees we are building and a handful of tests as a first step. We are also sorting out ways for to share the results, since the new system won't have a web dashboard for the time being.
>
> I am getting to this thread just now, but it seems that for your need, in a first step, would be adding user-mode builds. Is that correct? What would be in your scope after that?
>
> Currently no expectations beyond UM builds. Right now the point is to
> catch cases where we might inadvertently break UM since it isn't part
> of our workflow, but might be part of the workflow for downstream
> users of ACK kernels. We'll make a separate request if we need more
> than builds.
>
>
> Okay. Let me see if we add yours soon in the new system. (it is really painful to add new things to the legacy system).
>
> Would you be a recipient of the build breakages? I also want to figure out the regression reporting structure.

Yes, several of us on the Android kernel team are closely monitoring
kernelci breakages. These can be reported to us in the same way as
other breakages (visible as build breaks at
https://linux.kernelci.org/job/android/)

>
> Best regards,
>
> Gustavo
>
> --
> Gustavo Padovan
> Kernel Lead
>
> Collabora Ltd.
> Platinum Building, St John's Innovation Park
> Cambridge CB4 0DS, UK
> Registered in England & Wales, no. 5513718
>
>
> --
> Gustavo Padovan
> Kernel Lead
>
> Collabora Ltd.
> Platinum Building, St John's Innovation Park
> Cambridge CB4 0DS, UK
> Registered in England & Wales, no. 5513718