public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: khaled MOHAMMED atteya <khaled.m.atteya@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what is x86 entry point?
Date: Fri, 01 Oct 2010 12:58:24 -0600	[thread overview]
Message-ID: <4CA62F50.1070208@genband.com> (raw)
In-Reply-To: <AANLkTik9NCgucKyi367HZKzEUJXE3ysRdyryQLnEAAMC@mail.gmail.com>

On 10/01/2010 09:27 AM, khaled MOHAMMED atteya wrote:
> I want to know where is entry point for x86 arch?
> Also i read on some papers there are many entry points in kernel ,
> which are these?

Take a look at arch/x86/kernel/entry_32.S (or entry_64.S) for starters.

Conceptually you can get into the kernel via old-school system calls,
the sysenter mechanism, page faults, interrupts, etc.

Chris


-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com

      reply	other threads:[~2010-10-01 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 15:27 what is x86 entry point? khaled MOHAMMED atteya
2010-10-01 18:58 ` Chris Friesen [this message]

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=4CA62F50.1070208@genband.com \
    --to=chris.friesen@genband.com \
    --cc=khaled.m.atteya@gmail.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