linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Gavin Hemphill <hemphill@drea.dnd.ca>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: mprotect and SMP
Date: Wed, 6 Dec 2000 22:52:16 +0100	[thread overview]
Message-ID: <19341031152400.31248@192.168.1.10> (raw)
In-Reply-To: <3A2E643E.6EBA2012@drea.dnd.ca>


>(2.2.18-pre11) which uses the mprotect call to lock pages between the
>threads.  If I run the test program on this machine in SMP mode, it
>fails (threads tromp on their shared memory locations).  If I run in
>uni-processor mode however it works fine.  It also works fine on a dual
>processor pentium using a similar version of the kernel.  The question
>is... Has anyone seen this sort of behavior and are there any suggested
>places to start looking to fix it?  I took a look at the gemini specific
>files to see if there were any obvious missing eieio or sync
>instructions and so far haven't seen any, but I don't have the
>experience to know where else I should be looking.

Can you get the latest bitkeeper _2_2 tree or paulus latest rsync
tree and see if it still happens ?

Ben.

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

  reply	other threads:[~2000-12-06 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 16:08 mprotect and SMP Gavin Hemphill
2000-12-06 21:52 ` Benjamin Herrenschmidt [this message]
2000-12-07 12:29   ` Gavin Hemphill
2000-12-07 13:15     ` Benjamin Herrenschmidt
2001-01-03  1:35       ` Gavin Hemphill
2000-12-07 17:16   ` Gavin Hemphill

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=19341031152400.31248@192.168.1.10 \
    --to=bh40@calva.net \
    --cc=hemphill@drea.dnd.ca \
    --cc=linuxppc-dev@lists.linuxppc.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).