[PATCH 0/4] kernel/yocto: conslidated pull request

[PATCH 0/4] kernel/yocto: conslidated pull request

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here's my latest set of patches.

For 5.4: a -stable update, and -rt bug fix

For the build: a tweak to the config generation (as reported
and discussed on the mailing list)

For 5.8 (aka the next reference kernel): a fix for devsrc and
on target kernel building. With this tweak, I have all of the
refrences booting and passing most tests on 5.8, so we are in
good shape on that front. I'll be doing libc-headers testing
next.

I ran these through the AB and local testing, no issues popped
up, except a warning on qemuarm-alt in my last run. It was
about a console login and didn't look related to the change,
but I'm keeping my eye on it.

Cheers,

Bruce

The following changes since commit 968fcf4989f86a0a41fd1ccf08be3e73af428136:

  bitbake: server/process: Increase timeout for commands (2020-07-08 12:12:45 +0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (4):
  linux-yocto/5.4: update to v5.4.51
  linux-yocto-rt/5.4: fix mmdrop stress test issues
  kernel-yocto: account for extracted defconfig in elements check
  kernel-devsrc: fix on-target module build for v5.8+

 meta/classes/kernel-yocto.bbclass             |  2 +-
 meta/recipes-kernel/linux/kernel-devsrc.bb    | 16 ++++++++++++++
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +++++++++----------
 5 files changed, 35 insertions(+), 19 deletions(-)

-- 
2.19.1

[PATCH 1/4] linux-yocto/5.4: update to v5.4.51

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:

    1c54d3c15afa Linux 5.4.51
    8ba1913cd6ba efi: Make it possible to disable efivar_ssdt entirely
    43986c32ee00 dm zoned: assign max_io_len correctly
    215e562251bb x86/resctrl: Fix memory bandwidth counter width for AMD
    d827fe702e07 mm, compaction: make capture control handling safe wrt interrupts
    64a94c550c44 mm, compaction: fully assume capture is not NULL in compact_zone_order()
    2a9278ac9c55 irqchip/gic: Atomically update affinity
    7ba23593cbc5 dma-buf: Move dma_buf_release() from fops to dentry_ops
    4ae695a05516 drm/amdgpu/atomfirmware: fix vram_info fetching for renoir
    2b8c0876bf71 drm/amdgpu: use %u rather than %d for sclk/mclk
    94de85d16b0c drm/amd/display: Only revalidate bandwidth on medium and fast updates
    032343ed6927 MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
    2e859b14da39 MIPS: lantiq: xway: sysctrl: fix the GPHY clock alias names
    71a20b798da3 cifs: Fix the target file was deleted when rename failed.
    49dae9bed7dd SMB3: Honor 'handletimeout' flag for multiuser mounts
    7ab27439fec7 SMB3: Honor lease disabling for multiuser mounts
    0d5824aea7a0 SMB3: Honor persistent/resilient handle flags for multiuser mounts
    d56787683c61 SMB3: Honor 'seal' flag for multiuser mounts
    e0ed5a36fb3a Revert "ALSA: usb-audio: Improve frames size computation"
    fe05e114d0fd nfsd: apply umask on fs without ACL support
    4ee7f1d2f1c9 spi: spi-fsl-dspi: Fix external abort on interrupt in resume or exit paths
    9d60af5c3bb3 i2c: mlxcpld: check correct size of maximum RECV_LEN packet
    b460fc9d0525 i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
    a632f91f7a9c samples/vfs: avoid warning in statx override
    cd62eeb31512 nvme: fix a crash in nvme_mpath_add_disk
    c64141c68f72 nvme: fix identify error status silent ignore
    7d3f489e61b6 SMB3: Honor 'posix' flag for multiuser mounts
    8964c93436ad virtio-blk: free vblk-vqs in error path of virtblk_probe()
    f795a88eade5 drm: sun4i: hdmi: Remove extra HPD polling
    c84138b3c162 nfsd: fix nfsdfs inode reference count leak
    2571e1735602 nfsd4: fix nfsdfs reference count loop
    31ec38ec9cd5 thermal/drivers/rcar_gen3: Fix undefined temperature if negative
    a65bde001008 thermal/drivers/mediatek: Fix bank number settings on mt8183
    c9426817eac7 hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add()
    3e7bd7e10639 hwmon: (max6697) Make sure the OVERT mask is set correctly
    0465f54c5cc4 cxgb4: fix SGE queue dump destination buffer context
    6bcb00d08361 cxgb4: use correct type for all-mask IP address comparison
    f68bda772639 cxgb4: fix endian conversions for L4 ports in filters
    180fbf10a26d cxgb4: parse TC-U32 key values and masks natively
    0dc4dd433b94 cxgb4: use unaligned conversion for fetching timestamp
    8a1b8e64204e RDMA/counter: Query a counter before release
    53e9b62672f7 rxrpc: Fix afs large storage transmission performance drop
    60d7de28e0ca drm/msm/dpu: fix error return code in dpu_encoder_init
    cc0f67835302 crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
    5d6b46a94dbb tpm: Fix TIS locality timeout problems
    563e9491f0a3 selftests: tpm: Use /bin/sh instead of /bin/bash
    1f98a9ed5799 kgdb: Avoid suspicious RCU usage warning
    e6b2e3b5e16e nvme-multipath: fix bogus request queue reference put
    5e9523d7e8cd nvme-multipath: fix deadlock due to head->lock
    ad69fbe1d262 nvme-multipath: fix deadlock between ana_work and scan_work
    c4f007d3dbdd nvme-multipath: set bdi capabilities once
    8f4aa3a6de24 s390/debug: avoid kernel warning on too large number of pages
    517326aaf41e tools lib traceevent: Handle __attribute__((user)) in field names
    6f3b8c269d88 tools lib traceevent: Add append() function helper for appending strings
    3dca0a299ff4 usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
    0ff5b1b50d5c rxrpc: Fix race between incoming ACK parser and retransmitter
    fe688b144c14 mm/slub: fix stack overruns with SLUB_STATS
    f459e8fc7c69 mm/slub.c: fix corrupted freechain in deactivate_slab()
    542d541c1edd sched/debug: Make sd->flags sysctl read-only
    ab9ee18f4646 usbnet: smsc95xx: Fix use-after-free after removal
    58ab86e58b55 EDAC/amd64: Read back the scrub rate PCI register on F15h
    d0e533584a05 mm: fix swap cache node allocation mask
    1c4404efcf2c io_uring: make sure async workqueue is canceled on exit

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +++++++++----------
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index a4b593b96d..22a0dc997e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "6415a4e7c405526f97049ede833f52127a5ce7a1"
-SRCREV_meta ?= "416566e1f01c3c02ca5b3a03d0943df387d521f0"
+SRCREV_machine ?= "a1e1e3cbe42d8a08de5a3e3daaa2b389e352fe77"
+SRCREV_meta ?= "caafbdfe382bf22a4786d871af097acd49d0867a"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "5.4.50"
+LINUX_VERSION ?= "5.4.51"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index 0622d33835..86e133f9f2 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "5.4.50"
+LINUX_VERSION ?= "5.4.51"
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "1a8a14e45f01cfee926c5b35d2d67e6f1a7eebfc"
-SRCREV_machine ?= "94667198aabf869571bdff5291a24956796faddf"
-SRCREV_meta ?= "416566e1f01c3c02ca5b3a03d0943df387d521f0"
+SRCREV_machine_qemuarm ?= "d4c9ad88abadd22f7b2785e8a101523fe9a74dc0"
+SRCREV_machine ?= "fed60f1c8e56095647fa8497270ecacea4c45dbc"
+SRCREV_meta ?= "caafbdfe382bf22a4786d871af097acd49d0867a"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 2476b3502c..e79793b5f0 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86  ?= "v5.4/standard/base"
 KBRANCH_qemux86-64 ?= "v5.4/standard/base"
 KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "99743105f331e90852ccb9e72ce26134dbcafec6"
-SRCREV_machine_qemuarm64 ?= "94667198aabf869571bdff5291a24956796faddf"
-SRCREV_machine_qemumips ?= "886870e5abaeaaf753fb50a1e5be56336c44c642"
-SRCREV_machine_qemuppc ?= "94667198aabf869571bdff5291a24956796faddf"
-SRCREV_machine_qemuriscv64 ?= "94667198aabf869571bdff5291a24956796faddf"
-SRCREV_machine_qemux86 ?= "94667198aabf869571bdff5291a24956796faddf"
-SRCREV_machine_qemux86-64 ?= "94667198aabf869571bdff5291a24956796faddf"
-SRCREV_machine_qemumips64 ?= "7548abbb409eeef6f0575eed25231090f902559e"
-SRCREV_machine ?= "94667198aabf869571bdff5291a24956796faddf"
-SRCREV_meta ?= "416566e1f01c3c02ca5b3a03d0943df387d521f0"
+SRCREV_machine_qemuarm ?= "601e67d37274e4a0890bcdbe6660c2dbd08d3b97"
+SRCREV_machine_qemuarm64 ?= "fed60f1c8e56095647fa8497270ecacea4c45dbc"
+SRCREV_machine_qemumips ?= "c8543a84037b88da45d0d825216187b42d0c509a"
+SRCREV_machine_qemuppc ?= "fed60f1c8e56095647fa8497270ecacea4c45dbc"
+SRCREV_machine_qemuriscv64 ?= "fed60f1c8e56095647fa8497270ecacea4c45dbc"
+SRCREV_machine_qemux86 ?= "fed60f1c8e56095647fa8497270ecacea4c45dbc"
+SRCREV_machine_qemux86-64 ?= "fed60f1c8e56095647fa8497270ecacea4c45dbc"
+SRCREV_machine_qemumips64 ?= "c741fec6daabb449d08c9f96052be1477fe3c968"
+SRCREV_machine ?= "fed60f1c8e56095647fa8497270ecacea4c45dbc"
+SRCREV_meta ?= "caafbdfe382bf22a4786d871af097acd49d0867a"
 
 # remap qemuarm to qemuarma15 for the 5.4 kernel
 # KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.50"
+LINUX_VERSION ?= "5.4.51"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
 DEPENDS += "openssl-native util-linux-native"
-- 
2.19.1

[PATCH 2/4] linux-yocto-rt/5.4: fix mmdrop stress test issues

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Integrating the following commit(s) to linux-yocto/5.4:

    508b4e6ada7f sched: Remove unexpected mmdrop on RT

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 22a0dc997e..caa5b4ef53 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,7 +11,7 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "a1e1e3cbe42d8a08de5a3e3daaa2b389e352fe77"
+SRCREV_machine ?= "508b4e6ada7f78b3ef5a9dbdd182d13dffe00123"
 SRCREV_meta ?= "caafbdfe382bf22a4786d871af097acd49d0867a"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
-- 
2.19.1

[PATCH 3/4] kernel-yocto: account for extracted defconfig in elements check

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

The test for whether or not scc should to invoked to generate a
config.queue was missing the newly created sccs_defconfig variable.
We need to test for that variable as well, or we may miss generating
the config.queue in some cases.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/classes/kernel-yocto.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 54a1a1627a..3311f6e84e 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -213,7 +213,7 @@ do_kernel_metadata() {
 	meta_dir=$(kgit --meta)
 
 	# run1: pull all the configuration fragments, no matter where they come from
-	elements="`echo -n ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}`"
+	elements="`echo -n ${bsp_definition} $sccs_defconfig ${sccs} ${patches} ${KERNEL_FEATURES}`"
 	if [ -n "${elements}" ]; then
 		echo "${bsp_definition}" > ${S}/${meta_dir}/bsp_definition
 		scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} $sccs_defconfig $bsp_definition $sccs $patches ${KERNEL_FEATURES}
-- 
2.19.1

[PATCH 4/4] kernel-devsrc: fix on-target module build for v5.8+

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

The kernel build is now more sensitive to changing build inputs,
like the compiler, linker, source tree location, versions, file
timestamps, etc.

When a difference is detected, the kernel build invokes a syncconfig
to update/regenerate files as required. That process may prompt, and
hence breaks automated tested and other workflows.

By default, we don't want this to happen so we make sure that auto*
timestamps are newer or equal to the .config timestap, we ensure that
autoconf.h is in the filesystem and that we've substituted the
cross tools used to build the kernel with the names that will be
on the target.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/kernel-devsrc.bb | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
index 5940cc90ea..0c98535f75 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -108,6 +108,11 @@ do_install() {
 	fi
 
 	cp -a include $kerneldir/build/include
+
+	# we don't usually copy generated files, since they can be rebuilt on the target,
+	# but without this file, we get a forced syncconfig run in v5.8+, which prompts and
+	# breaks workflows.
+	cp -a --parents include/generated/autoconf.h $kerneldir/build 2>/dev/null || :
     )
 
     # now grab the chunks from the source tree that we need
@@ -249,6 +254,17 @@ do_install() {
     # Copy .config to include/config/auto.conf so "make prepare" is unnecessary.
     cp $kerneldir/build/.config $kerneldir/build/include/config/auto.conf
 
+    # make sure these are at least as old as the .config, or rebuilds will trigger
+    touch -r $kerneldir/build/.config $kerneldir/build/include/generated/autoconf.h 2>/dev/null || :
+    touch -r $kerneldir/build/.config $kerneldir/build/include/config/auto.conf* 2>/dev/null || :
+
+    if [ -e "$kerneldir/build/include/config/auto.conf.cmd" ]; then
+        sed -i 's/ifneq "$(CC)" ".*-linux-gcc.*$/ifneq "$(CC)" "gcc"/' "$kerneldir/build/include/config/auto.conf.cmd"
+        sed -i 's/ifneq "$(LD)" ".*-linux-ld.bfd.*$/ifneq "$(LD)" "ld"/' "$kerneldir/build/include/config/auto.conf.cmd"
+        sed -i 's/ifneq "$(CC_VERSION_TEXT)".*\(gcc.*\)"/ifneq "$(CC_VERSION_TEXT)" "\1"/' "$kerneldir/build/include/config/auto.conf.cmd"
+        sed -i 's/ifneq "$(srctree)" ".*"/ifneq "$(srctree)" "."/' "$kerneldir/build/include/config/auto.conf.cmd"
+    fi
+
     # make the scripts python3 safe. We won't be running these, and if they are
     # left as /usr/bin/python rootfs assembly will fail, since we only have python3
     # in the RDEPENDS (and the python3 package does not include /usr/bin/python)
-- 
2.19.1

Re: [PATCH 0/4] kernel/yocto: conslidated pull request

[Richard Purdie]

On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
> Here's my latest set of patches.
> 
> For 5.4: a -stable update, and -rt bug fix
> 
> For the build: a tweak to the config generation (as reported
> and discussed on the mailing list)
> 
> For 5.8 (aka the next reference kernel): a fix for devsrc and
> on target kernel building. With this tweak, I have all of the
> refrences booting and passing most tests on 5.8, so we are in
> good shape on that front. I'll be doing libc-headers testing
> next.
> 
> I ran these through the AB and local testing, no issues popped
> up, except a warning on qemuarm-alt in my last run. It was
> about a console login and didn't look related to the change,
> but I'm keeping my eye on it.

Thanks, I ran this combined with Khem's binutils change through the
autobuilder and your changes are likely fine but we need more work to
get binutils in. Basically:

* meta-arm needs to add the kernel patch for perf
* meta-intel needs to add the kernel patch for perf
* the hardware BSPs need to add the kernel patch for perf

I've added a few maintainers/people to the address list to try and sort
that out. Who is going to handle the hardware platforms?

Cheers,

Richard

Re: [OE-core] [PATCH 0/4] kernel/yocto: conslidated pull request

[Richard Purdie]

On Wed, 2020-08-05 at 12:06 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
> > Here's my latest set of patches.
> > 
> > For 5.4: a -stable update, and -rt bug fix
> > 
> > For the build: a tweak to the config generation (as reported
> > and discussed on the mailing list)
> > 
> > For 5.8 (aka the next reference kernel): a fix for devsrc and
> > on target kernel building. With this tweak, I have all of the
> > refrences booting and passing most tests on 5.8, so we are in
> > good shape on that front. I'll be doing libc-headers testing
> > next.
> > 
> > I ran these through the AB and local testing, no issues popped
> > up, except a warning on qemuarm-alt in my last run. It was
> > about a console login and didn't look related to the change,
> > but I'm keeping my eye on it.
> 
> Thanks, I ran this combined with Khem's binutils change through the
> autobuilder and your changes are likely fine but we need more work to
> get binutils in. Basically:
> 
> * meta-arm needs to add the kernel patch for perf
> * meta-intel needs to add the kernel patch for perf
> * the hardware BSPs need to add the kernel patch for perf
> 
> I've added a few maintainers/people to the address list to try and
> sort
> that out. Who is going to handle the hardware platforms?

Sorry, the url for the failing builds:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1231

The kernel tweak needed for binutils 2.35:

http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.4/standard/base&id=1fe4ee7f680c3f69f620d68a5d2f7341e8db693b

Cheers,

Richard

Re: [OE-core] [PATCH 0/4] kernel/yocto: conslidated pull request

[Andrey Zhizhikin]

On Wed, Aug 5, 2020 at 1:06 PM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
> > Here's my latest set of patches.
> >
> > For 5.4: a -stable update, and -rt bug fix
> >
> > For the build: a tweak to the config generation (as reported
> > and discussed on the mailing list)
> >
> > For 5.8 (aka the next reference kernel): a fix for devsrc and
> > on target kernel building. With this tweak, I have all of the
> > refrences booting and passing most tests on 5.8, so we are in
> > good shape on that front. I'll be doing libc-headers testing
> > next.
> >
> > I ran these through the AB and local testing, no issues popped
> > up, except a warning on qemuarm-alt in my last run. It was
> > about a console login and didn't look related to the change,
> > but I'm keeping my eye on it.
>
> Thanks, I ran this combined with Khem's binutils change through the
> autobuilder and your changes are likely fine but we need more work to
> get binutils in. Basically:
>
> * meta-arm needs to add the kernel patch for perf
> * meta-intel needs to add the kernel patch for perf
> * the hardware BSPs need to add the kernel patch for perf

meta-freescale has this patch already included for 5.4.y kernel:
https://github.com/Freescale/linux-fslc/commit/415afad5ca95f303000b58b7c77871e99c8244b5

>
> I've added a few maintainers/people to the address list to try and sort
> that out. Who is going to handle the hardware platforms?
>
> Cheers,
>
> Richard
>
>
>
>
> 



-- 
Regards,
Andrey.

Re: [PATCH 0/4] kernel/yocto: conslidated pull request

[Bruce Ashfield]

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

On Wed, Aug 5, 2020 at 7:06 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
> > Here's my latest set of patches.
> >
> > For 5.4: a -stable update, and -rt bug fix
> >
> > For the build: a tweak to the config generation (as reported
> > and discussed on the mailing list)
> >
> > For 5.8 (aka the next reference kernel): a fix for devsrc and
> > on target kernel building. With this tweak, I have all of the
> > refrences booting and passing most tests on 5.8, so we are in
> > good shape on that front. I'll be doing libc-headers testing
> > next.
> >
> > I ran these through the AB and local testing, no issues popped
> > up, except a warning on qemuarm-alt in my last run. It was
> > about a console login and didn't look related to the change,
> > but I'm keeping my eye on it.
>
> Thanks, I ran this combined with Khem's binutils change through the
> autobuilder and your changes are likely fine but we need more work to
> get binutils in. Basically:
>
> * meta-arm needs to add the kernel patch for perf
> * meta-intel needs to add the kernel patch for perf
> * the hardware BSPs need to add the kernel patch for perf
>
> I've added a few maintainers/people to the address list to try and sort
> that out. Who is going to handle the hardware platforms?
>

I have a meta-yocto-bsp bump that I did for the latest 5.4, it'll have that
fix as well. I can send it out now for the reference platforms.

Bruce



>
> Cheers,
>
> Richard
>
>
>
>
>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

[-- Attachment #2: Type: text/html, Size: 2751 bytes --]

Re: [OE-core] [PATCH 0/4] kernel/yocto: conslidated pull request

[Anuj Mittal]

On Wed, 2020-08-05 at 12:10 +0100, Richard Purdie wrote:
> On Wed, 2020-08-05 at 12:06 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
> > > Here's my latest set of patches.
> > > 
> > > For 5.4: a -stable update, and -rt bug fix
> > > 
> > > For the build: a tweak to the config generation (as reported
> > > and discussed on the mailing list)
> > > 
> > > For 5.8 (aka the next reference kernel): a fix for devsrc and
> > > on target kernel building. With this tweak, I have all of the
> > > refrences booting and passing most tests on 5.8, so we are in
> > > good shape on that front. I'll be doing libc-headers testing
> > > next.
> > > 
> > > I ran these through the AB and local testing, no issues popped
> > > up, except a warning on qemuarm-alt in my last run. It was
> > > about a console login and didn't look related to the change,
> > > but I'm keeping my eye on it.
> > 
> > Thanks, I ran this combined with Khem's binutils change through the
> > autobuilder and your changes are likely fine but we need more work
> > to
> > get binutils in. Basically:
> > 
> > * meta-arm needs to add the kernel patch for perf
> > * meta-intel needs to add the kernel patch for perf
> > * the hardware BSPs need to add the kernel patch for perf
> > 
> > I've added a few maintainers/people to the address list to try and
> > sort
> > that out. Who is going to handle the hardware platforms?
> 
> Sorry, the url for the failing builds:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1231
> 
> The kernel tweak needed for binutils 2.35:
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.4/standard/base&id=1fe4ee7f680c3f69f620d68a5d2f7341e8db693b
> 

Thanks Richard. I have included the patch in meta-intel.

Thanks,

Anuj

Re: [OE-core] [PATCH 0/4] kernel/yocto: conslidated pull request

[Richard Purdie]

On Thu, 2020-08-06 at 05:04 +0000, Mittal, Anuj wrote:
> On Wed, 2020-08-05 at 12:10 +0100, Richard Purdie wrote:
> > On Wed, 2020-08-05 at 12:06 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
> > > > Here's my latest set of patches.
> > > > 
> > > > For 5.4: a -stable update, and -rt bug fix
> > > > 
> > > > For the build: a tweak to the config generation (as reported
> > > > and discussed on the mailing list)
> > > > 
> > > > For 5.8 (aka the next reference kernel): a fix for devsrc and
> > > > on target kernel building. With this tweak, I have all of the
> > > > refrences booting and passing most tests on 5.8, so we are in
> > > > good shape on that front. I'll be doing libc-headers testing
> > > > next.
> > > > 
> > > > I ran these through the AB and local testing, no issues popped
> > > > up, except a warning on qemuarm-alt in my last run. It was
> > > > about a console login and didn't look related to the change,
> > > > but I'm keeping my eye on it.
> > > 
> > > Thanks, I ran this combined with Khem's binutils change through the
> > > autobuilder and your changes are likely fine but we need more work
> > > to
> > > get binutils in. Basically:
> > > 
> > > * meta-arm needs to add the kernel patch for perf
> > > * meta-intel needs to add the kernel patch for perf
> > > * the hardware BSPs need to add the kernel patch for perf
> > > 
> > > I've added a few maintainers/people to the address list to try and
> > > sort
> > > that out. Who is going to handle the hardware platforms?
> > 
> > Sorry, the url for the failing builds:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1231
> > 
> > The kernel tweak needed for binutils 2.35:
> > 
> > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.4/standard/base&id=1fe4ee7f680c3f69f620d68a5d2f7341e8db693b
> > 
> 
> Thanks Richard. I have included the patch in meta-intel.

Thanks Anuj. That fixed the errors but there are still warnings with
master-next:

https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/594

I've sent a patch for the first one which is a simple typo. The other
one looks to be a meta-intel configuration issue.

Cheers,

Richard

Re: [OE-core] [PATCH 0/4] kernel/yocto: conslidated pull request

[Bruce Ashfield]

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

On Thu, Aug 6, 2020 at 5:15 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Thu, 2020-08-06 at 05:04 +0000, Mittal, Anuj wrote:
> > On Wed, 2020-08-05 at 12:10 +0100, Richard Purdie wrote:
> > > On Wed, 2020-08-05 at 12:06 +0100, Richard Purdie via
> > > lists.openembedded.org wrote:
> > > > On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
> > > > > Here's my latest set of patches.
> > > > >
> > > > > For 5.4: a -stable update, and -rt bug fix
> > > > >
> > > > > For the build: a tweak to the config generation (as reported
> > > > > and discussed on the mailing list)
> > > > >
> > > > > For 5.8 (aka the next reference kernel): a fix for devsrc and
> > > > > on target kernel building. With this tweak, I have all of the
> > > > > refrences booting and passing most tests on 5.8, so we are in
> > > > > good shape on that front. I'll be doing libc-headers testing
> > > > > next.
> > > > >
> > > > > I ran these through the AB and local testing, no issues popped
> > > > > up, except a warning on qemuarm-alt in my last run. It was
> > > > > about a console login and didn't look related to the change,
> > > > > but I'm keeping my eye on it.
> > > >
> > > > Thanks, I ran this combined with Khem's binutils change through the
> > > > autobuilder and your changes are likely fine but we need more work
> > > > to
> > > > get binutils in. Basically:
> > > >
> > > > * meta-arm needs to add the kernel patch for perf
> > > > * meta-intel needs to add the kernel patch for perf
> > > > * the hardware BSPs need to add the kernel patch for perf
> > > >
> > > > I've added a few maintainers/people to the address list to try and
> > > > sort
> > > > that out. Who is going to handle the hardware platforms?
> > >
> > > Sorry, the url for the failing builds:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1231
> > >
> > > The kernel tweak needed for binutils 2.35:
> > >
> > >
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.4/standard/base&id=1fe4ee7f680c3f69f620d68a5d2f7341e8db693b
> > >
> >
> > Thanks Richard. I have included the patch in meta-intel.
>
> Thanks Anuj. That fixed the errors but there are still warnings with
> master-next:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/594
>
> I've sent a patch for the first one which is a simple typo. The other
> one looks to be a meta-intel configuration issue.
>

Looks a bug in my new analysis tools, if you drop that patch from
master-next, I can look into it a bit more and try to reproduce the issue
locally.

Bruce



>
> Cheers,
>
> Richard
>
>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

[-- Attachment #2: Type: text/html, Size: 4767 bytes --]

Re: [OE-core] [PATCH 0/4] kernel/yocto: conslidated pull request

[Bruce Ashfield]

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

On Thu, Aug 6, 2020 at 8:46 AM Bruce Ashfield via lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:

>
>
> On Thu, Aug 6, 2020 at 5:15 AM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
>> On Thu, 2020-08-06 at 05:04 +0000, Mittal, Anuj wrote:
>> > On Wed, 2020-08-05 at 12:10 +0100, Richard Purdie wrote:
>> > > On Wed, 2020-08-05 at 12:06 +0100, Richard Purdie via
>> > > lists.openembedded.org wrote:
>> > > > On Fri, 2020-07-17 at 08:56 -0400, bruce.ashfield@gmail.com wrote:
>> > > > > Here's my latest set of patches.
>> > > > >
>> > > > > For 5.4: a -stable update, and -rt bug fix
>> > > > >
>> > > > > For the build: a tweak to the config generation (as reported
>> > > > > and discussed on the mailing list)
>> > > > >
>> > > > > For 5.8 (aka the next reference kernel): a fix for devsrc and
>> > > > > on target kernel building. With this tweak, I have all of the
>> > > > > refrences booting and passing most tests on 5.8, so we are in
>> > > > > good shape on that front. I'll be doing libc-headers testing
>> > > > > next.
>> > > > >
>> > > > > I ran these through the AB and local testing, no issues popped
>> > > > > up, except a warning on qemuarm-alt in my last run. It was
>> > > > > about a console login and didn't look related to the change,
>> > > > > but I'm keeping my eye on it.
>> > > >
>> > > > Thanks, I ran this combined with Khem's binutils change through the
>> > > > autobuilder and your changes are likely fine but we need more work
>> > > > to
>> > > > get binutils in. Basically:
>> > > >
>> > > > * meta-arm needs to add the kernel patch for perf
>> > > > * meta-intel needs to add the kernel patch for perf
>> > > > * the hardware BSPs need to add the kernel patch for perf
>> > > >
>> > > > I've added a few maintainers/people to the address list to try and
>> > > > sort
>> > > > that out. Who is going to handle the hardware platforms?
>> > >
>> > > Sorry, the url for the failing builds:
>> > >
>> > >
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1231
>> > >
>> > > The kernel tweak needed for binutils 2.35:
>> > >
>> > >
>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.4/standard/base&id=1fe4ee7f680c3f69f620d68a5d2f7341e8db693b
>> > >
>> >
>> > Thanks Richard. I have included the patch in meta-intel.
>>
>> Thanks Anuj. That fixed the errors but there are still warnings with
>> master-next:
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/594
>>
>> I've sent a patch for the first one which is a simple typo. The other
>> one looks to be a meta-intel configuration issue.
>>
>
> Looks a bug in my new analysis tools, if you drop that patch from
> master-next, I can look into it a bit more and try to reproduce the issue
> locally.
>
>
and now I see that you fixed it .. thanks!

Bruce



> Bruce
>
>
>
>>
>> Cheers,
>>
>> Richard
>>
>>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

[-- Attachment #2: Type: text/html, Size: 5962 bytes --]