All of lore.kernel.org
 help / color / mirror / Atom feed
From: "machael thailer" <dony.he@huawei.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: questions about some bits of STATUS register and exception priority...
Date: Tue, 21 Aug 2001 18:53:34 +0800	[thread overview]
Message-ID: <001901c12a2f$8626be00$8021690a@huawei.com> (raw)
In-Reply-To: 20010821085353.B13302@dea.linux-mips.net

> On Tue, Aug 21, 2001 at 09:34:00AM +0800, machael thailer wrote:
>
> >     I am confused about CU0 and UM(ERL EXL) bit of STATUS register.
> >
> >     The user manual says that " CP0 is always usable when in Kernel
mode,
> > regardless of the setting of CU0 bit". Does it mean that when in Kernel
mode
> > , the CU0 bit is always 1 and in User mode, the CU0 bit is 0? If the CU0
is
> > 0, can we be sure that it is in User mode?
>
> In the Linux kernel CU0 is used to indicate that we're running on the
> kernel stack.

Yes, when CU0 is 1, we can see we are running on the kernel stack.
But when CU0 is 0, can we say it is in User mode?

>
> > Another question about exception priority:
> > In entry.S, some exception handlers enables global interrupt bit(IE) but
> > others disables it.
>
> We have to avoid infinite recursion of exceptions; in same cases it's
> just paranoia or minor performance issue.
>
> > Also syscall exception handler enables global interrupt bit(IE). Since
the
> > interrupt priority  is lowest,If an interrupt happens in a syscall
exception
> > handler, will it pause the syscall exception handler and run the
interrupt
> > handler? If not, why it enable the IE bit(STI) in the syscall exception
> > handler??


The answer of this question? Thanks.

machael thailer

WARNING: multiple messages have this Message-ID (diff)
From: "machael thailer" <dony.he@huawei.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: questions about some bits of STATUS register and exception priority...
Date: Tue, 21 Aug 2001 18:53:34 +0800	[thread overview]
Message-ID: <001901c12a2f$8626be00$8021690a@huawei.com> (raw)
Message-ID: <20010821105334._sq4LHaDHtfjx8Uaps1_Q1LccFCwKkl6vRDpAM5sd4U@z> (raw)
In-Reply-To: 20010821085353.B13302@dea.linux-mips.net

> On Tue, Aug 21, 2001 at 09:34:00AM +0800, machael thailer wrote:
>
> >     I am confused about CU0 and UM(ERL EXL) bit of STATUS register.
> >
> >     The user manual says that " CP0 is always usable when in Kernel
mode,
> > regardless of the setting of CU0 bit". Does it mean that when in Kernel
mode
> > , the CU0 bit is always 1 and in User mode, the CU0 bit is 0? If the CU0
is
> > 0, can we be sure that it is in User mode?
>
> In the Linux kernel CU0 is used to indicate that we're running on the
> kernel stack.

Yes, when CU0 is 1, we can see we are running on the kernel stack.
But when CU0 is 0, can we say it is in User mode?

>
> > Another question about exception priority:
> > In entry.S, some exception handlers enables global interrupt bit(IE) but
> > others disables it.
>
> We have to avoid infinite recursion of exceptions; in same cases it's
> just paranoia or minor performance issue.
>
> > Also syscall exception handler enables global interrupt bit(IE). Since
the
> > interrupt priority  is lowest,If an interrupt happens in a syscall
exception
> > handler, will it pause the syscall exception handler and run the
interrupt
> > handler? If not, why it enable the IE bit(STI) in the syscall exception
> > handler??


The answer of this question? Thanks.

machael thailer

  reply	other threads:[~2001-08-21 10:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15  1:30 Virtual address to physical address mapping machael thailer
2001-08-15  1:30 ` machael thailer
2001-08-15  8:33 ` Ralf Baechle
2001-08-20  9:54   ` questions about eret machael thailer
2001-08-20  9:54     ` machael thailer
2001-08-20 21:07     ` Ralf Baechle
2001-08-21  1:06       ` machael thailer
2001-08-21  1:06         ` machael thailer
2001-08-21  6:35         ` Ralf Baechle
2001-08-21 10:09           ` machael thailer
2001-08-21 10:09             ` machael thailer
2001-08-21 11:17             ` Ralf Baechle
2001-08-21 15:17               ` Question on porting Linux Shuanglin Wang
2001-08-21 14:33                 ` jeff_lee
2001-08-21 14:33                   ` jeff_lee
2001-08-21 15:33                   ` Shuanglin Wang
2001-08-21 17:26                 ` Jun Sun
2001-08-21 20:26                 ` Carsten Langgaard
2001-08-21 21:36                   ` Shuanglin Wang
2001-08-22  9:58                     ` Carsten Langgaard
2001-08-21  1:34       ` questions about some bits of STATUS register and exception priority machael thailer
2001-08-21  1:34         ` machael thailer
2001-08-21  6:53         ` Ralf Baechle
2001-08-21 10:53           ` machael thailer [this message]
2001-08-21 10:53             ` machael thailer
2001-08-21 11:14             ` Ralf Baechle

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='001901c12a2f$8626be00$8021690a@huawei.com' \
    --to=dony.he@huawei.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.