From: Mike Rapoport <rppt@kernel.org>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] m68k: mcfmmu: remove stale part of comment about steal_context
Date: Thu, 18 Jun 2020 15:09:56 +0300 [thread overview]
Message-ID: <20200618120956.GE6571@kernel.org> (raw)
In-Reply-To: <bb70270a-5634-f258-f144-9410e8baf068@linux-m68k.org>
Hi Greg,
On Thu, Jun 18, 2020 at 09:48:42PM +1000, Greg Ungerer wrote:
> Hi Mike,
>
> On 18/6/20 6:17 pm, Mike Rapoport wrote:
> > From: Mike Rapoport <rppt@linux.ibm.com>
> >
> > The comment about steal_context() came from powerpc and a part of it
> > addresses differences between powerpc variants that are not really
> > relevant to m68k.
> >
> > Remove that part of the comment.
> >
> > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
>
> Acked-by: Greg Ungerer <gerg@linux-m68k.org>
>
> Do you want me to carry that in my m68k (m68knommu) tree for v5.9?
Yes, please :)
> Regards
> Greg
>
>
> > ---
> > Hi,
> >
> > I've found this by pure chance while grepping for pgalloc.h
> > It's been there since 2011, but I don't think it's a stable material, so I
> > didn't cc them.
> >
> > arch/m68k/mm/mcfmmu.c | 5 -----
> > 1 file changed, 5 deletions(-)
> >
> > diff --git a/arch/m68k/mm/mcfmmu.c b/arch/m68k/mm/mcfmmu.c
> > index 29f47923aa46..cb9f8675d81b 100644
> > --- a/arch/m68k/mm/mcfmmu.c
> > +++ b/arch/m68k/mm/mcfmmu.c
> > @@ -214,11 +214,6 @@ void __init cf_mmu_context_init(void)
> > /*
> > * Steal a context from a task that has one at the moment.
> > - * This is only used on 8xx and 4xx and we presently assume that
> > - * they don't do SMP. If they do then thicfpgalloc.hs will have to check
> > - * whether the MM we steal is in use.
> > - * We also assume that this is only used on systems that don't
> > - * use an MMU hash table - this is true for 8xx and 4xx.
> > * This isn't an LRU system, it just frees up each context in
> > * turn (sort-of pseudo-random replacement :). This would be the
> > * place to implement an LRU scheme if anyone was motivated to do it.
> >
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2020-06-18 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 8:17 [PATCH] m68k: mcfmmu: remove stale part of comment about steal_context Mike Rapoport
2020-06-18 11:48 ` Greg Ungerer
2020-06-18 12:09 ` Mike Rapoport [this message]
2020-06-18 12:25 ` Greg Ungerer
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=20200618120956.GE6571@kernel.org \
--to=rppt@kernel.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rppt@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox