public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Universal Regs address
Date: Mon, 25 Feb 2002 13:05:43 -0800	[thread overview]
Message-ID: <3C7AA727.316EC197@mvista.com> (raw)

&regs is needed by the deliver signal code and currently is supplied by
the system call interface to the system calls that need it.  This
requires that any new system call to have (at least in some archs)
special code in the system call trap area to pass the &regs, or does it?

In an arch in which the call stack address decreases as calls are made,
isn't:

&regs = stack_base+size of(stack) - size of(struct regs);

an for stacks that increase:

&regs = stack_base;

The only time this would not be true, unless I am missing something, is
if the system call is made from kernel space.  Is this an issue?  Do we
ever need &regs if called from the kernel?  If not, can we tell the call
was from the kernel?

comments?
-- 
George           george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/

                 reply	other threads:[~2002-02-25 21:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C7AA727.316EC197@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.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