From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] kernel: consolidated pull request
Date: Mon, 21 Oct 2019 16:16:12 -0400 [thread overview]
Message-ID: <cover.1571688520.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here's a set of changes that I've been testing while the release finalizes.
Now that master is open, I figured I'd send them before starting to stack
on more changes.
Note: I have more -stable changes for 5.2 and 4.19, I just haven't fully
tested them yet, so they'll follow in a day or so.
For linux-yocto-dev, I'm bumping it to v5.4-rcX .. and of note, mips64 boot
was totally broken on the switch to userspace, I had to do the following
mainline reverts to get it working (after a couple of days of bisecting):
932bb934ed4d mips: compat: vdso: Use legacy syscalls as fallback
cdab7e2c73d5 mips: vdso: Fix flip/flop vdso building bug
b4c0f7fa5308 mips: vdso: Fix source path
1f66c45db330 mips: Add clock_gettime64 entry point
abed3d826f2f mips: Add clock_getres entry point
6393e6064486 mips: fix vdso32 build, again
24640f233b46 mips: Add support for generic vDSO
8919975b6171 MIPS: VDSO: Fix build for binutils < 2.25
90800281e761 MIPS: VDSO: Remove unused gettimeofday.c
I'll report this upstream to linux-mips, since we'll want this properly
fixed before I start into the next release kernel. While annoying, I'm glad
that I ran into this right after it happened in mainline, and not in three
months from now.
During my v5.4 testing, I ran into some perf build failures and came up
with a series of patches to fix it, and get rid of some warnings while
building.
The update and fix are these two changes:
perf: fix v5.4+ builds
perf: create directories before copying single files
I also noticed a libcap non-derministic detection, so I created a patch
to control it via PACKAGECONFIG:
perf: add 'cap' PACKAGECONFIG
And then my final patch for perf, which is a RFC/RFT sort of thing. When
fixing (yet another) set of "out of sync" file detection changes between
perf and the headers, I realized that it was between the tools captured
headers and a copy of the main include that we are doing from the kernel
source directory. I was able to drop that include completely, and build
for all architectures. I was also then able to drop some of the file copies
that we've added over time.
This worked for me, but I'd be interested to see if it breaks anyone elses
perf builds.
Cheers,
Bruce
The following changes since commit f484aa6090c5fa3f69c3aed0cab154ed1f46b7ac:
python-native: Remove debug.patch (2019-10-19 23:18:34 +0100)
are available in the Git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (6):
linux-yocto/4.19: update to v4.19.78
linux-yocto/5.2: update to v5.2.20
perf: fix v5.4+ builds
perf: create directories before copying single files
perf: add 'cap' PACKAGECONFIG
perf: drop 'include' copy
.../linux/linux-yocto-rt_4.19.bb | 6 ++---
.../linux/linux-yocto-rt_5.2.bb | 6 ++---
.../linux/linux-yocto-tiny_4.19.bb | 8 +++----
.../linux/linux-yocto-tiny_5.2.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_4.19.bb | 20 ++++++++---------
meta/recipes-kernel/linux/linux-yocto_5.2.bb | 22 +++++++++----------
meta/recipes-kernel/perf/perf.bb | 9 ++++----
7 files changed, 40 insertions(+), 39 deletions(-)
--
2.19.1
next reply other threads:[~2019-10-21 20:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 20:16 bruce.ashfield [this message]
2019-10-21 20:16 ` [PATCH 1/6] linux-yocto/4.19: update to v4.19.78 bruce.ashfield
2019-10-21 20:16 ` [PATCH 2/6] linux-yocto/5.2: update to v5.2.20 bruce.ashfield
2019-10-21 20:16 ` [PATCH 3/6] perf: fix v5.4+ builds bruce.ashfield
2019-10-21 20:23 ` Martin Jansa
2019-10-21 20:59 ` Bruce Ashfield
2019-10-21 21:11 ` Bruce Ashfield
2019-10-21 20:16 ` [PATCH 4/6] perf: create directories before copying single files bruce.ashfield
2019-10-21 20:16 ` [PATCH 5/6] perf: add 'cap' PACKAGECONFIG bruce.ashfield
2019-10-21 20:16 ` [PATCH 6/6] perf: drop 'include' copy bruce.ashfield
2019-10-21 20:24 ` Martin Jansa
2019-10-21 20:57 ` Bruce Ashfield
2020-05-26 5:44 ` [OE-core] " Andrey Zhizhikin
2020-05-26 12:31 ` Bruce Ashfield
2020-05-26 20:22 ` Andrey Zhizhikin
2020-05-26 20:44 ` Martin Jansa
2020-05-26 20:55 ` Andrey Zhizhikin
-- strict thread matches above, loose matches on Subject: below --
2021-03-09 19:23 [PATCH 0/6] kernel: consolidated pull request Bruce Ashfield
2021-11-04 19:48 bruce.ashfield
2022-01-14 18:23 bruce.ashfield
2022-01-27 3:55 bruce.ashfield
2022-02-04 4:16 bruce.ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1571688520.git.bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.