From: Denys Dmytriyenko <denis@denix.org>
To: "Balagopalakrishnan, Anand" <anandb@ti.com>
Cc: "Bajjuri, Praneeth" <praneeth@ti.com>,
"meta-ti@lists.yoctoproject.org" <meta-ti@lists.yoctoproject.org>,
"Eatmon, Ryan" <reatmon@ti.com>,
"Adivi, Sai Sree Kartheek" <s-adivi@ti.com>,
"Gupta, Gyan" <g-gupta@ti.com>,
"Khasim, Syed Mohammed" <khasim@ti.com>,
"Pothukuchi, Vijay" <vijayp@ti.com>
Subject: Re: [EXTERNAL] Re: [meta-ti] [RFC|kirkstone] linux-ti-staging: add config preempt for am335x and am437x
Date: Tue, 19 Sep 2023 14:13:41 -0400 [thread overview]
Message-ID: <20230919181341.GC7013@denix.org> (raw)
In-Reply-To: <cfe86ebae4374412817e3c4c2c4fc423@ti.com>
Anand,
Please check corresponding -next branches (master/kirkstone) - CICD automerges
and SRCREV bumps are queued up there and I'm guessing they are going through
the build and boot-test cycles now. If everything's green, they should be
merged back to main kirkstone and master branches automatically. Ryan can
definitely explain the entire CICD process in more detail.
--
Denys
On Tue, Sep 19, 2023 at 04:35:30AM +0000, Balagopalakrishnan, Anand wrote:
> Praneeth,
>
> srcrev in kernel recipe for kirkstone branch needs to be bumped. The last CICD build was 6-Sep - also a good idea to trigger another full build.
>
> Regards,
> Anand
>
> -----Original Message-----
> From: Bajjuri, Praneeth <praneeth@ti.com>
> Sent: Friday, September 15, 2023 9:47 PM
> To: Balagopalakrishnan, Anand <anandb@ti.com>; Denys Dmytriyenko <denis@denix.org>
> Cc: meta-ti@lists.yoctoproject.org; Eatmon, Ryan <reatmon@ti.com>; Adivi, Sai Sree Kartheek <s-adivi@ti.com>; Gupta, Gyan <g-gupta@ti.com>; Khasim, Syed Mohammed <khasim@ti.com>; Pothukuchi, Vijay <vijayp@ti.com>
> Subject: Re: [EXTERNAL] Re: [meta-ti] [RFC|kirkstone] linux-ti-staging: add config preempt for am335x and am437x
>
>
>
> On 9/14/2023 8:47 PM, Balagopalakrishnan, Anand wrote:
> > Hi Denys,
> >
> > This is only needed for v7 platforms like AM3 / AM4 and possibly AM57x also. CONFIG_PREEMPT is enabled by default on arm64 platforms like AM65x.
> >
> > Praneeth will send a kernel patch for TI kernel. This meta-ti patch is meant to unblock anyone who wants to enable SGX drive in the meanwhile.
>
>
> This patch can be abandoned .
> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.1.y-cicd&id=e025e31126fff01ded59d901af916abe87646ca6
> enables CONFIG_PREEMPT
>
>
> >
> > Regards,
> > Anand
> >
> > -----Original Message-----
> > From: Denys Dmytriyenko <denis@denix.org>
> > Sent: Friday, September 15, 2023 1:25 AM
> > To: Balagopalakrishnan, Anand <anandb@ti.com>
> > Cc: meta-ti@lists.yoctoproject.org; Eatmon, Ryan <reatmon@ti.com>; Adivi, Sai Sree Kartheek <s-adivi@ti.com>; Gupta, Gyan <g-gupta@ti.com>; Khasim, Syed Mohammed <khasim@ti.com>; Pothukuchi, Vijay <vijayp@ti.com>; Bajjuri, Praneeth <praneeth@ti.com>
> > Subject: [EXTERNAL] Re: [meta-ti] [RFC|kirkstone] linux-ti-staging: add config preempt for am335x and am437x
> >
> > On Thu, Sep 14, 2023 at 03:36:18PM -0400, Denys Dmytriyenko wrote:
> >> On Thu, Sep 14, 2023 at 10:40:26PM +0530, Anand Balagopalakrishnan via lists.yoctoproject.org wrote:
> >>> SGX needs a preemptible kernel. CONFIG_PREEMPT has always been
> >>> enabled on TI Linux kernels upto K5.1.
> >>>
> >>> This is enabled on AM65x by default but missed out AM335x and AM437x.
> >>> Add a kernel config fragment to enable config preempt.
> >>
> >> Hi, Anand,
> >>
> >> Is this only needed for am335x and am437x, as the subject suggests? If
> >> so, why the code adds the config fragment to all platforms?
> >>
> >> Second question - historically this has been enabled in the TI kernel itself.
> >> Why not do it like that again, why add the fragment to the OE metadata
> >> instead of keeping it in-tree? How the distro-agnostic approach would be handled?
> >>
> >>
> >>> Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
> >>> ---
> >>> .../linux/files/configs/config-preempt.cfg | 12 ++++++++++++
> >>> .../recipes-kernel/linux/linux-ti-staging_6.1.bb | 1 +
> >>> 2 files changed, 13 insertions(+)
> >>> create mode 100644
> >>> meta-ti-bsp/recipes-kernel/linux/files/configs/config-preempt.cfg
> >>>
> >>> diff --git
> >>> a/meta-ti-bsp/recipes-kernel/linux/files/configs/config-preempt.cfg
> >>> b/meta-ti-bsp/recipes-kernel/linux/files/configs/config-preempt.cfg
> >>> new file mode 100644
> >>> index 00000000..c1e5ad7d
> >>> --- /dev/null
> >>> +++ b/meta-ti-bsp/recipes-kernel/linux/files/configs/config-preempt.
> >>> +++ cfg
> >>
> >> This is not the right location for the file. You want to add to the
> >> linux-ti-staging-rt-6.1/ directory, since you are only using it from
> >> the corresponding linux-ti-staging_6.1.bb recipe.
> >
> > Sorry, typo here - linux-ti-staging-6.1/ directory, if it's not RT-specific.
> >
> >>
> >>> @@ -0,0 +1,12 @@
> >>> +CONFIG_PREEMPT_BUILD=y
> >>> +# CONFIG_PREEMPT_NONE is not set
> >>> +CONFIG_PREEMPT=y
> >>> +CONFIG_PREEMPT_COUNT=y
> >>> +CONFIG_PREEMPTION=y
> >>> +CONFIG_PREEMPT_RCU=y
> >>> +CONFIG_TASKS_RCU_GENERIC=y
> >>> +CONFIG_TASKS_RCU=y
> >>> +CONFIG_UNINLINE_SPIN_UNLOCK=y
> >>> +# CONFIG_CEC_GPIO is not set
> >>> +CONFIG_DEBUG_PREEMPT=y
> >>> +# CONFIG_PREEMPT_TRACER is not set
> >>> diff --git
> >>> a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> >>> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> >>> index 8a883878..0ee63358 100644
> >>> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> >>> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> >>> @@ -33,6 +33,7 @@ PR = "${MACHINE_KERNEL_PR}"
> >>>
> >>> KERNEL_GIT_URI ?= "git://git.ti.com/git/ti-linux-kernel/ti-linux-kernel.git"
> >>> KERNEL_GIT_PROTOCOL = "https"
> >>> +KERNEL_CONFIG_FRAGMENTS += "${WORKDIR}/config-preempt.cfg"
> >>
> >> Since this file is out-of-tree and in the OE metadata, it would also
> >> require listing it in SRC_URI.
> >>
> >>
> >>> SRC_URI += "${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${BRANCH} \
> >>> file://defconfig"
> >>>
> >>> --
> >>> 2.34.1
next prev parent reply other threads:[~2023-09-19 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 17:10 [RFC|kirkstone] linux-ti-staging: add config preempt for am335x and am437x Anand Balagopalakrishnan
2023-09-14 19:09 ` [meta-ti] " Andrew Davis
2023-09-14 19:30 ` Ryan Eatmon
2023-09-14 19:36 ` [meta-ti] " Denys Dmytriyenko
2023-09-14 19:57 ` Bajjuri, Praneeth
[not found] ` <1784DB091C7C28F5.22721@lists.yoctoproject.org>
2023-09-14 19:55 ` Denys Dmytriyenko
2023-09-15 1:47 ` [EXTERNAL] " Balagopalakrishnan, Anand
2023-09-15 16:17 ` Bajjuri, Praneeth
2023-09-15 16:42 ` Denys Dmytriyenko
2023-09-21 0:31 ` Bajjuri, Praneeth
2023-09-19 4:35 ` Balagopalakrishnan, Anand
2023-09-19 18:13 ` Denys Dmytriyenko [this message]
2023-09-20 10:04 ` [EXTERNAL] " Anand Balagopalakrishnan
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=20230919181341.GC7013@denix.org \
--to=denis@denix.org \
--cc=anandb@ti.com \
--cc=g-gupta@ti.com \
--cc=khasim@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=s-adivi@ti.com \
--cc=vijayp@ti.com \
/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.