From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>
Cc: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"raj.khem@gmail.com" <raj.khem@gmail.com>
Subject: Re: [OE-core] [PATCH 3/3] linux-yocto/5.8: update to v5.8.2
Date: Mon, 24 Aug 2020 03:21:30 +0000 [thread overview]
Message-ID: <227946a676d142f2a1d15ba3b8eaab85800212fc.camel@intel.com> (raw)
In-Reply-To: <CADkTA4NApf+0cxP21pQ=JykJbazGk1M-si6etrqPFvQ0oE6STw@mail.gmail.com>
On Sun, 2020-08-23 at 23:03 -0400, Bruce Ashfield wrote:
>
>
> On Sun, Aug 23, 2020 at 7:59 PM Mittal, Anuj <anuj.mittal@intel.com>
> wrote:
> > On Sat, 2020-08-22 at 01:20 -0700, Khem Raj wrote:
> > > Hi Bruce
> > >
> > > On rv64 I am seeing an error while building lttng
> > >
> > > #error "LTTng-modules requires CONFIG_KPROBES on kernels >=
> > 5.7.0"
> > > > 20 | # error "LTTng-modules requires CONFIG_KPROBES on
> > kernels
> > > > >= 5.7.0"
> > > > | ^~~~~
> > >
> > > I wonder if we need to update defconfig
> >
> > I see the same failure with linux-yocto-rt kernel as well.
> >
>
> -rt doesn't enable kprobes, so yes, with the latest lttng, it would
> trigger that issue.
>
> Traditionally -rt had issues with kprobes, but that is resolved now.
> Rather than adding the overhead, the enablement is still on demand
> for -rt.
>
> That being said, it looks like lttng has forced my hand, I just
> enabled the config by default in -rt and don't see any issues.
>
> I'll send a patch on Monday to fix it up.
Thanks Bruce. Should PREFERRRED_VERSION of linux-yocto-rt should also
be explicitly set like that of linux-yocto? I was wondering if there is
a specific reason why we don't set version for that kernel for qemu and
BSPs?
Thanks,
Anuj
next prev parent reply other threads:[~2020-08-24 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 19:02 [PATCH 0/3] kernel-yocto: consolidated pull request Bruce Ashfield
2020-08-21 19:02 ` [PATCH 1/3] qemu: bump default reference kernel to v5.8 Bruce Ashfield
2020-08-21 19:02 ` [PATCH 2/3] linux-yocto/5.4: update to v5.4.59 Bruce Ashfield
2020-08-21 19:02 ` [PATCH 3/3] linux-yocto/5.8: update to v5.8.2 Bruce Ashfield
2020-08-22 8:20 ` [OE-core] " Khem Raj
2020-08-22 16:16 ` Bruce Ashfield
[not found] ` <162DA34FDEE6646E.7353@lists.openembedded.org>
2020-08-22 17:11 ` Bruce Ashfield
2020-08-23 3:36 ` Khem Raj
2020-08-23 23:59 ` Anuj Mittal
2020-08-24 3:03 ` Bruce Ashfield
2020-08-24 3:21 ` Anuj Mittal [this message]
2020-08-24 7:39 ` Khem Raj
2020-08-24 12:51 ` Bruce Ashfield
2020-08-24 12:30 ` 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=227946a676d142f2a1d15ba3b8eaab85800212fc.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox