linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: tom_gall@vnet.ibm.com
To: Tom Gall <tgall@rochcivictheatre.org>
Cc: Troy Benjegerdes <hozer@drgw.net>, Dan Malek <dan@mvista.com>,
	linuxppc_commit@hq.fsmlabs.com,
	linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: context overflow
Date: Mon, 22 Jan 2001 18:55:43 +0000	[thread overview]
Message-ID: <3A6C822F.7DB50A58@vnet.ibm.com> (raw)
In-Reply-To: 3A6BB971.7F128273@rochcivictheatre.org


Tom Gall wrote:
>
> Troy Benjegerdes wrote:
>
> > On Fri, Jan 19, 2001 at 09:27:44PM -0500, Dan Malek wrote:
> > >
> > > I just heard about the bug Tom Gall fixed in "context_overflow"
> > > by testing for current->mm == NULL.
> > >
> > > I believe the proper solution is to use 'current->active_mm'
> > > instead of 'current->mm' (and you never get a null pointer).
> > > This way, the proper 'active' context is updated with a new
> > > context even though a kernel thread has stolen it from somewhere
> > > else to use.  I think skipping the selection of a new context
> > > in this case could be logically incorrect for some PowerPC cores.
> >
> > Since this got no response, I'm cross-posting to linuxppc-commit.
>
> I will look into this tomorrow.  It's an important fix, I don't want to rush.

Hi All,

  Ok here's the explaination and I beg forgivness if this isn't clear or needs
more filled in.

  current->mm I believe is correct. active_mm for tasks in user space just point
back to mm. kernel space tasks will have an mm of NULL yet their active_mm will
point back to the last user space task they ran.

  The reason for this patch is in the case where the idle task comes in on one
processor and on another processor it has encountered a context overflow. The
idle task on processor 0 detects the overflow as well and that's when things get
interesting, and why the change.

  So anyway that's the situation from my neck of the woods. These other
processor cores make me worried. What cores are you refering too? Are they SMP?
How and in what ways are they different?

  Many thanks to Pat McCarthy who is my local guru on this topic and also the
author of the fix in question.

  Regards,

  Tom
--
Tom Gall - PowerPC Linux Team    "Where's the ka-boom? There was
Linux Technology Center           supposed to be an earth
(w) tom_gall@vnet.ibm.com         shattering ka-boom!"
(w) 507-253-4558                 -- Marvin Martian
(h) tgall@rochcivictheatre.org
http://oss.software.ibm.com/developerworks/opensource/linux

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-01-22 18:55 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-20  2:27 context overflow Dan Malek
2001-01-22  4:28 ` Troy Benjegerdes
2001-01-22  4:39   ` Tom Gall
2001-01-22 18:10     ` Dan Malek
2001-01-22 18:55     ` tom_gall [this message]
2001-01-22 19:59       ` Dan Malek
2001-01-22 22:08         ` tom_gall
2001-01-23  0:10           ` Dan Malek
2001-01-23 10:00             ` Gabriel Paubert
2001-01-23 18:21               ` Dan Malek
2001-02-06 10:55                 ` Paul Mackerras
2001-02-06 21:11                   ` Dan Malek
2001-02-06 21:50                     ` Paul Mackerras
2001-02-06 22:29                       ` Dan Malek
2001-02-06 22:45                         ` Paul Mackerras
2001-02-06 10:50               ` Paul Mackerras
2001-02-06 21:32                 ` Dan Malek
2001-02-06 22:08                   ` Paul Mackerras
2001-02-06 23:14                     ` Dan Malek
2001-02-07  0:23                       ` Paul Mackerras
2001-02-07 18:02                         ` Dan Malek
2001-02-08  0:48                           ` Paul Mackerras
2001-02-08  1:39                             ` Frank Rowand
2001-02-08 19:00                             ` David Edelsohn
2001-02-08 20:53                               ` Roman Zippel
2001-02-08 21:14                                 ` David Edelsohn
2001-02-08 23:23                                   ` Roman Zippel
2001-02-08 23:48                                     ` Cort Dougan
2001-02-08 21:28                               ` Cort Dougan
2001-02-08 22:08                                 ` David Edelsohn
2001-02-08 22:26                                   ` Cort Dougan
2001-02-08 23:17                                     ` David Edelsohn
2001-02-08 23:27                                       ` Cort Dougan
2001-02-08 23:28                                   ` Gabriel Paubert
2001-02-09  9:58                                     ` Paul Mackerras
2001-02-09 10:57                                       ` Gabriel Paubert
2001-02-09 11:26                                         ` Paul Mackerras
2001-02-09 10:49                               ` Paul Mackerras
2001-02-07  9:18                   ` Roman Zippel
2001-02-07 17:46                     ` Dan Malek
2001-02-07 18:39                       ` Roman Zippel
2001-02-07 21:16                         ` Gabriel Paubert
2001-02-08  0:34                           ` Paul Mackerras
2001-01-22  4:55   ` Larry McVoy
2001-01-22  6:15     ` Troy Benjegerdes
2001-01-23  1:12 ` Frank Rowand
2001-01-23  1:20   ` Dan Malek
2001-01-23  2:12     ` Frank Rowand

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=3A6C822F.7DB50A58@vnet.ibm.com \
    --to=tom_gall@vnet.ibm.com \
    --cc=dan@mvista.com \
    --cc=hozer@drgw.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc_commit@hq.fsmlabs.com \
    --cc=tgall@rochcivictheatre.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;
as well as URLs for NNTP newsgroup(s).