linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Takeharu KATO <takeharu1219@ybb.ne.jp>
To: Joerg Dorchain <joerg@dorchain.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: boot time scheduling hile atomic
Date: Fri, 11 Mar 2005 01:19:53 +0900	[thread overview]
Message-ID: <423073A9.70404@ybb.ne.jp> (raw)
In-Reply-To: <20050310072803.GR4017@Redstar.dorchain.net>

Hi Joerg:

> I came to the same idea. This explains as well why the i386 party does
> not notice the effect, as their first interrupt happen later (different
> HZ value)
> 
As far as I know, current HZ value for PPC is 1000
as same as i386 family.

Please see following:

-- include/asm-i386/param.h
   1 #ifndef _ASMi386_PARAM_H
   2 #define _ASMi386_PARAM_H
   3
   4 #ifdef __KERNEL__
   5 # define HZ             1000            /* Internal kernel timer 
frequency */
-- include/asm-i386/param.h

-- include/asm-ppc/param.h

   1 #ifndef _ASM_PPC_PARAM_H
   2 #define _ASM_PPC_PARAM_H
   3
   4 #ifdef __KERNEL__
   5 #define HZ              1000            /* internal timer frequency */
   6 #define USER_HZ         100             /* for user interfaces in 
"ticks" */
-- include/asm-ppc/param.h

FYI, Kernel preemption ought not to be taken place at this point,
because preemption count is a positive number.

According to my observation, the problem occur on second call of
proc_root_init.But I could not who call it.
IIRC,the value of LR(link register) pointed at the start of BSS.

Regards,



-- 
Takeharu KATO

  reply	other threads:[~2005-03-10 16:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 12:44 GCC4 fun Joerg Dorchain
2005-03-03 13:13 ` Marc Leeman
2005-03-03 13:46 ` evilninja
2005-03-03 14:18   ` boot time scheduling hile atomic (was: GCC4 fun.) Joerg Dorchain
2005-03-04  7:57     ` Joerg Dorchain
2005-03-04 15:06       ` boot time scheduling hile atomic _evil
2005-03-10  4:51       ` Takeharu KATO
2005-03-10  7:28         ` Joerg Dorchain
2005-03-10 16:19           ` Takeharu KATO [this message]
2005-03-11  6:19             ` Takeharu KATO
2005-03-16  0:18               ` Benjamin Herrenschmidt
2005-03-16  5:24                 ` Takeharu KATO
2005-03-16  5:49                   ` Takeharu KATO
2005-03-16  6:28                     ` Benjamin Herrenschmidt
2005-03-16 14:07                       ` Takeharu KATO
2005-03-16 22:28                         ` Benjamin Herrenschmidt
2005-03-17  0:46                           ` Takeharu KATO
2005-03-11 22:21           ` boot time scheduling while atomic Takeharu KATO
  -- strict thread matches above, loose matches on Subject: below --
2005-06-10 14:23 boot time scheduling hile atomic Rune Torgersen
2005-06-14 12:41 ` Takeharu KATO

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=423073A9.70404@ybb.ne.jp \
    --to=takeharu1219@ybb.ne.jp \
    --cc=joerg@dorchain.net \
    --cc=linuxppc-dev@ozlabs.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).