Message-ID: <2a7ff382-1d35-0eeb-6fb6-bad37aa4c1d7@redhat.com>
Date:   Fri, 19 Feb 2021 16:45:42 +0200
From:   Nikolai Kondrashov <Nikolai.Kondrashov@...hat.com>
To:     Hanjun Guo <guohanjun@...wei.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Scott Branden <scott.branden@...adcom.com>
Cc:     Huxinwei <huxinwei@...wei.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Yanjin <yanjin.yan@...wei.com>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
        Zhaohongjiang <zhaohongjiang@...wei.com>,
        "Zhangdianfang (Dianfang, OS Lab)" <zhangdianfang@...wei.com>,
        PEIXIN HOU <PEIXIN.HOU@...wei.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        kernelci@...ups.io
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?

Hi Hanjun,

On 2/19/21 10:54 AM, Hanjun Guo wrote:
 > In specific, we will start from the testing work, using HULK robot
 > (reports lots of bugs to mainline kernel) testing framework to test
 > compile, reboot, functional testing, and will extend to basic
 > performance regression testing in the future.

I heard about Huawei ramping up kernel testing from someone at FOSDEM
2019. I wonder if it was you :) Nice to see your progress and the company
stepping up to help with testing!

Would you be interested in working with the Linux Foundation KernelCI project
on submitting your build and test results to the common database - KCIDB?

We are working on aggregating results from various testing systems so we can
provide a dashboard, and a single, aggregated e-mail report to subscribed
maintainers and developers.

We have a prototype dashboard at https://staging.kernelci.org:3000/ and are
working hard on making the e-mail reports good enough to start reaching out to
maintainers.

We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of
course, KernelCI native tests sending data to the database. Linaro Tuxsuite is
starting sending today. We could use your data, and of course any development
help you could spare :)

I wish I could show you my today's KCIDB presentation at DevConf.cz, but the
recording is not out yet. Meanwhile you can take a look at our presentation at
last year's Linux Plumbers: https://youtu.be/y9Glc90WUN0?t=10739

Or see our intro in an older blog post:
https://foundation.kernelci.org/blog/2020/08/21/introducing-common-reporting/

Anyone wishing to contribute to KCIDB gets credentials and permissions to
submit to our "playground" setup where they can send their data, see it in a
dashboard, experiment without worrying about breaking anything, and decide if
they like it or not.

If you're interested, take a look at our Submission HOWTO:
https://github.com/kernelci/kcidb/blob/v8/SUBMISSION_HOWTO.md
and send an email to kernelci@...ups.io (CC'd), or come over to the #kernelci
channel on freenode.net!

Nick

On 2/19/21 10:54 AM, Hanjun Guo wrote:
 > Hi Greg,
 >
 > On 2021/1/26 15:29, Greg Kroah-Hartman wrote:
 > [...]
 >>
 >> I want to see companies _using_ the kernel, and most importantly,
 >> _updating_ their devices with it, to know if it is worth to keep around
 >> for longer than 2 years.  I also, hopefully, want to see how those
 >> companies will help me out in the testing and maintenance of that kernel
 >> version in order to make supporting it for 6 years actually possible.
 >>
 >> So, are you planning on using 5.10?  Will you will be willing to help
 >> out in testing the -rc releases I make to let me know if there are any
 >> problems, and to help in pointing out and backporting any specific
 >> patches that your platforms need for that kernel release?
 >
 > We(Huawei) are willing to commit resources to help out in testing the
 > stable -rc releases, and to help to backport patches for stable kernels.
 >
 > 5.10 stable kernel will be used for openEuler [1] kernel and also inside
 > Huawei. From customer's feedback, it's very important to see the stable
 > kernel we used to be maintained for 6 years in the community, and we
 > will use 5.10 kernel for at least 6 years, so we are willing to help
 > you and help ourselves :)
 >
 > In specific, we will start from the testing work, using HULK robot
 > (reports lots of bugs to mainline kernel) testing framework to test
 > compile, reboot, functional testing, and will extend to basic
 > performance regression testing in the future.
 >
 > And we will start from ARM64 and X86 architecture first, and then extend
 > to other platforms.
 >
 > For patch backporting, will send the bugfix patches (from mainline)
 > we spotted, but I think this work may not doing in regular but will
 > be triggered as needed.
 >
 > Does this sound good to you?
 >
 > Thanks
 > Hanjun
 >
 > [1]: https://openeuler.org/en/
 >
 > _______________________________________________
 > linux-arm-kernel mailing list
 > linux-arm-kernel@...ts.infradead.org
 > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
 >

Powered by blists - more mailing lists