From: Haibo Li <haibo.li@mediatek.com>
To: <samitolvanen@google.com>
Cc: <andrealmeid@igalia.com>, <atomlin@redhat.com>,
<christophe.leroy@csgroup.eu>, <dmitry.torokhov@gmail.com>,
<haibo.li@mediatek.com>, <jgross@suse.com>,
<keescook@chromium.org>, <lecopzer.chen@mediatek.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <llvm@lists.linux.dev>,
<matthias.bgg@gmail.com>, <mcgrof@kernel.org>,
<mhiramat@kernel.org>, <nathan@kernel.org>,
<ndesaulniers@google.com>, <peterz@infradead.org>,
<xiaoming.yu@mediatek.com>, <yangtiezhu@loongson.cn>
Subject: Re: [PATCH 2/2] ANDROID: cfi: free old cfi shadow asynchronously
Date: Fri, 1 Jul 2022 10:42:33 +0800 [thread overview]
Message-ID: <20220701024233.52022-1-haibo.li@mediatek.com> (raw)
In-Reply-To: <CABCJKudz5O5_-1q1H0o2DFRcnpMQDBPv4STUVa2bOE9ePaeyDA@mail.gmail.com>
> Hi,
>
> On Thu, Jun 30, 2022 at 2:47 AM Haibo Li <haibo.li@mediatek.com> wrote:
> >
> > Currenly, it uses synchronize_rcu() to wait old rcu reader to go away
> > in update_shadow.In embedded platform like ARM CA7X, load_module
> > blocks 40~50ms in update_shadow.
> > When there are more than one hundred kernel modules, it blocks several
> > seconds.
> >
> > To accelerate load_module,change synchronize_rcu to call_rcu.
> >
> > Signed-off-by: Haibo Li <haibo.li@mediatek.com>
> > Signed-off-by: Lecopzer Chen <lecopzer.chen@mediatek.com>
>
> Thanks for the patch! Please drop ANDROID: from the subject line, that's only
> used in the Android kernel trees.
>
Thanks for the comment.I will change it in next patch.
> > kernel/cfi.c | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/cfi.c b/kernel/cfi.c index
> > 456771c8e454..a4836d59ca27 100644
> > --- a/kernel/cfi.c
> > +++ b/kernel/cfi.c
> > @@ -43,6 +43,8 @@ typedef u16 shadow_t; struct cfi_shadow {
> > /* Page index for the beginning of the shadow */
> > unsigned long base;
> > + /* rcu to free old cfi_shadow asynchronously */
> > + struct rcu_head rcu;
> > /* An array of __cfi_check locations (as indices to the shadow) */
> > shadow_t shadow[1];
> > } __packed;
> > @@ -182,6 +184,13 @@ static void remove_module_from_shadow(struct
> cfi_shadow *s, struct module *mod,
> > }
> > }
> >
> > +static void _cfi_shadow_free_rcu(struct rcu_head *rcu)
>
> I think this can be simply renamed to free_shadow.
Thanks for the comment.I will change it in next patch.
>
> > +{
> > + struct cfi_shadow *old = container_of(rcu, struct cfi_shadow,
> > +rcu);
> > +
> > + vfree(old);
> > +}
> > +
> > typedef void (*update_shadow_fn)(struct cfi_shadow *, struct module *,
> > unsigned long min_addr, unsigned long
> > max_addr);
> >
> > @@ -211,11 +220,10 @@ static void update_shadow(struct module *mod,
> > unsigned long base_addr,
> >
> > rcu_assign_pointer(cfi_shadow, next);
> > mutex_unlock(&shadow_update_lock);
> > - synchronize_rcu();
> >
> > if (prev) {
> > set_memory_rw((unsigned long)prev, SHADOW_PAGES);
> > - vfree(prev);
> > + call_rcu(&prev->rcu, _cfi_shadow_free_rcu);
> > }
> > }
>
> It's probably better to keep the pages read-only until they're actually released.
> Can you move the set_memory_rw call to the new function?
>
Since call_rcu and rcu callbacks change members in &prev->rcu,the old pages need to be rw at first.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-01 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 9:46 [PATCH 0/2] ANDROID: cfi:free old cfi shadow asynchronously Haibo Li
2022-06-30 9:46 ` [PATCH 1/2] ANDROID: cfi: enable sanitize for cfi.c Haibo Li
2022-06-30 16:19 ` Sami Tolvanen
2022-07-01 2:10 ` Haibo Li
2022-06-30 9:46 ` [PATCH 2/2] ANDROID: cfi: free old cfi shadow asynchronously Haibo Li
2022-06-30 16:16 ` Sami Tolvanen
2022-07-01 2:27 ` Haibo Li
2022-07-01 2:42 ` Haibo Li [this message]
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=20220701024233.52022-1-haibo.li@mediatek.com \
--to=haibo.li@mediatek.com \
--cc=andrealmeid@igalia.com \
--cc=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dmitry.torokhov@gmail.com \
--cc=jgross@suse.com \
--cc=keescook@chromium.org \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=xiaoming.yu@mediatek.com \
--cc=yangtiezhu@loongson.cn \
/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