All of lore.kernel.org
 help / color / mirror / Atom feed
From: "machael thailer" <dony.he@huawei.com>
To: <linux-mips@oss.sgi.com>
Subject: question about syscall and interrupts......
Date: Wed, 22 Aug 2001 10:33:08 +0800	[thread overview]
Message-ID: <001201c12ab2$c7c4e700$8021690a@huawei.com> (raw)

Hello,
    I find that in handle_sys() of scall_o32.S, it calls:
        SAVE_SOME
    But in the various board interrupt handlers entry(int-handler.S), it
calls:
        SAVE_ALL

    So before entering syscall and interrupt handler entry, why do they need
save different registers? and interrupt need save more things than syscalls?

Thank you very much.

machael thailer

WARNING: multiple messages have this Message-ID (diff)
From: "machael thailer" <dony.he@huawei.com>
To: linux-mips@oss.sgi.com
Subject: question about syscall and interrupts......
Date: Wed, 22 Aug 2001 10:33:08 +0800	[thread overview]
Message-ID: <001201c12ab2$c7c4e700$8021690a@huawei.com> (raw)
Message-ID: <20010822023308.MOHxWacn1vbaXzsSo7Nh33jUniZ4-cP2kpckPTKSJeE@z> (raw)

Hello,
    I find that in handle_sys() of scall_o32.S, it calls:
        SAVE_SOME
    But in the various board interrupt handlers entry(int-handler.S), it
calls:
        SAVE_ALL

    So before entering syscall and interrupt handler entry, why do they need
save different registers? and interrupt need save more things than syscalls?

Thank you very much.

machael thailer

             reply	other threads:[~2001-08-22  2:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22  2:33 machael thailer [this message]
2001-08-22  2:33 ` question about syscall and interrupts machael thailer

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='001201c12ab2$c7c4e700$8021690a@huawei.com' \
    --to=dony.he@huawei.com \
    --cc=linux-mips@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.