linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Gall <gall@rochcivictheatre.org>
To: Kaoru Fukui <k_fukui@highway.ne.jp>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent kernel
Date: Thu, 29 Mar 2001 20:18:13 -0600	[thread overview]
Message-ID: <3AC3ECE5.1B65198F@rochcivictheatre.org> (raw)
In-Reply-To: 20010330062000.Postino-000633@smtp01.highway.ne.jp


Hi Kaoru,

  I tried your patch on my 2 way Power3 Model 270 RS/6000 just before I
left but didn't have enough time to write this note until now.

  Your patch amazingly booted my box quite a bit further... it still
dies for me but in a new and interesting way, that doesn't appear to be
related to the page_table_lock. (Token Ring and shared memory
...sigh...)

  The part that REALLY REALLY bothers me tho is why does this patch
work? I *HAVE* CONFIG_SMP on... least I think I do... there's two
penguins on my screen ... two processors grinding away ... that's
CONFIG_SMP right??? I'm not losing my mind am I?

  So assuming that CONFIG_SMP is on, this patch shouldn't yeild anything
different what so ever from a codegen perspective with or without the
patch for an SMP kernel build. It doesn't make sense.

Kaoru Fukui wrote:
>
> Many thanks Tom,
>
> I have had a success for kernel-2.4.3.pre8-SMP on Dual G4.
> This kernel needs the patch.
>
> Kernel Guys, Please look the patch
>
> I will be able to upload this binary kernel into my directory tomorrow.
>
> Kaoru
> -------- this patch is needed for SMP kernel-2.4.3.pre8  ---------
>
> diff -urN base/arch/ppc/mm/init.c fixed/arch/ppc/mm/init.c
> --- base/arch/ppc/mm/init.c     Thu Mar 29 06:02:35 2001
> +++ fixed/arch/ppc/mm/init.c    Fri Mar 30 05:51:16 2001
> @@ -437,12 +437,15 @@
>         /*
>          * Should check if it is a candidate for a BAT mapping
>          */
> -
> +#ifndef CONFIG_SMP
>         spin_lock(&init_mm.page_table_lock);
> +#endif
>         err = 0;
>         for (i = 0; i < size && err == 0; i += PAGE_SIZE)
>                 err = map_page(v+i, p+i, flags);
> +#ifndef CONFIG_SMP
>         spin_unlock(&init_mm.page_table_lock);
> +#endif
>         if (err) {
>                 if (mem_init_done)
>                         vfree((void *)v);
> diff -urN base/mm/memory.c fixed/mm/memory.c
> --- base/mm/memory.c    Thu Mar 29 09:22:35 2001
> +++ fixed/mm/memory.c   Fri Mar 30 05:52:17 2001
> @@ -1320,9 +1320,13 @@
>                 /* "fast" allocation can happen without dropping the lock.. */
>                 new = pte_alloc_one_fast(address);
>                 if (!new) {
> +#ifndef CONFIG_SMP
>                         spin_unlock(&mm->page_table_lock);
> +#endif
>                         new = pte_alloc_one(address);
> +#ifndef CONFIG_SMP
>                         spin_lock(&mm->page_table_lock);
> +#endif
>                         if (!new)
>                                 return NULL;
>
> ---------- END -------------
>
> > > This is booing message when kernel-2.4.3pre8-SMP.
> > >
> > > <snip>
> > > TCP: Hash tables configured (established 8192 bind 8192)
> > > ip_conntrack(2048 buckets,16384 max)
> > > _spin_lock(c02cc470) CPU# 1 NIP c0033404 holder: cpu 1 pc C002B384
> > > _spin_lock(c02ce740) CPU# 0 NIP c0015890 holder: cpu 1 pc C0015890
>
> >   Can you look at your system.map for that kernel and tell me what is at
> > addresses:
>
> > This is getton  data from system.map
>
> > c00153b0 T schedule_tail
> > <C001589>
> > c0015a4c T __wake_up
> > <snip>
> > c002b28c T pte_alloc
> > <C002b384>
> > c002b3d8 T make_pages_present
> > <snip>
> > c02cc42c D init_mm
> > <c02cc470>
> > c02cc4d0 D init_task_union
> > <snip>
> > c02ce738 d null_pci_ops
> > <c02ce740>
> > c02ce750 D kernel_flag
> >
>

--
Regards,

Tom

--------------------------------------------------------------
Linux Guy             "My heart is human, my blood is boiling,
gall@rochcivictheatre.org    my brain IBM" -- Mr Roboto, Styxx

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

  reply	other threads:[~2001-03-30  2:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-28 17:18 spin_lock problem in recent kernel Kaoru Fukui
2001-03-28 19:02 ` Tom Gall
2001-03-29 13:29   ` Kaoru Fukui
     [not found]     ` <3AC33CA7.E5DF4C03@vnet.ibm.com>
2001-03-29 21:20       ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent k ernel Kaoru Fukui
2001-03-30  2:18         ` Tom Gall [this message]
2001-03-30  2:16           ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent kernel Takashi Oe
2001-03-30  2:48             ` Tom Gall
2001-03-30  2:36           ` Tony Mantler
2001-03-30  3:07             ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem inrecent kernel Tom Gall
2001-03-30 12:40               ` Olaf Hering
2001-03-30  9:16         ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent k ernel Geert Uytterhoeven

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=3AC3ECE5.1B65198F@rochcivictheatre.org \
    --to=gall@rochcivictheatre.org \
    --cc=k_fukui@highway.ne.jp \
    --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).