From: James Hogan <james.hogan@imgtec.com>
To: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: yhb@ruijie.com.cn, ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: We need to clear MMU contexts of all other processes when asid_cache(cpu) wraps to 0.
Date: Mon, 11 Jul 2016 21:18:40 +0100 [thread overview]
Message-ID: <20160711201839.GD26799@jhogan-linux.le.imgtec.org> (raw)
Message-ID: <20160711201840.ztPdeWWlzIAWDSW3m8qA3ktkXW0K4esfpzD64EEPdHw@z> (raw)
In-Reply-To: <5783F5D7.2090804@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Hi Leonid,
On Mon, Jul 11, 2016 at 12:39:03PM -0700, Leonid Yegoshin wrote:
> On 07/11/2016 12:21 PM, James Hogan wrote:
> > Note also that I have a patch I'm about to submit which changes some of
> > those assignments of 0 to assign 1 instead (so as not to confuse the
> > cache management code into thinking the CPU has never run the code when
> > it has, while still triggering ASID regeneration). That applies here
> > too, so it should perhaps be doing something like this instead:
> >
> > if (t->mm != mm && cpu_context(cpu, t->mm))
> > cpu_context(cpu, t->mm) = 1;
> Not sure, but did you have chance to look into having another variable
> for cache flush control? It can be that some more states may be needed
> in future, so - just disjoin both, TLB and cache coontrol.
No, I haven't yet. I'll Cc you so we can discuss there instead, and in
the mean time perhaps its best to ignore what I said above for this
patch.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-11 20:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 13:04 MIPS: We need to clear MMU contexts of all other processes when asid_cache(cpu) wraps to 0 yhb
2016-07-10 13:04 ` yhb
2016-07-11 9:30 ` James Hogan
2016-07-11 9:30 ` James Hogan
2016-07-11 18:02 ` Leonid Yegoshin
2016-07-11 18:02 ` Leonid Yegoshin
2016-07-11 18:05 ` [PATCH] " Leonid Yegoshin
2016-07-11 18:05 ` Leonid Yegoshin
2016-07-11 18:07 ` James Hogan
2016-07-11 18:07 ` James Hogan
2016-07-11 18:19 ` [PATCH] " Leonid Yegoshin
2016-07-11 18:19 ` Leonid Yegoshin
2016-07-11 19:21 ` James Hogan
2016-07-11 19:21 ` James Hogan
2016-07-11 19:39 ` Leonid Yegoshin
2016-07-11 19:39 ` Leonid Yegoshin
2016-07-11 20:18 ` James Hogan [this message]
2016-07-11 20:18 ` James Hogan
2016-07-12 3:48 yhb
2016-07-12 3:48 ` yhb
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=20160711201839.GD26799@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=yhb@ruijie.com.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;
as well as URLs for NNTP newsgroup(s).