The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: eliad lubovsky <eliadl@013.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Handle kernel page faults using task gate
Date: Fri, 1 Jul 2005 00:40:27 -0400	[thread overview]
Message-ID: <200507010043_MC3-1-A32F-B78C@compuserve.com> (raw)

On Fri, 01 Jul 2005 at 04:23:08 +0300, eliad lubovsky wrote:

> attached a patch, it may be more clear to understand what I have done.

Ouch.

Are you doublefaulting before you reach the handler?


--
Chuck

             reply	other threads:[~2005-07-01  4:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  4:40 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-30 16:53 Handle kernel page faults using task gate Chuck Ebbert
2005-06-30 16:53 Chuck Ebbert
2005-06-28 22:18 eliad lubovsky
2005-06-29 13:09 ` Ingo Molnar
2005-06-29 15:43   ` eliad lubovsky
2005-06-29 19:27   ` Ingo Molnar
2005-06-30  6:57     ` eliad lubovsky
2005-06-30  7:11       ` Ingo Molnar
2005-07-01  1:23         ` eliad lubovsky

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=200507010043_MC3-1-A32F-B78C@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=eliadl@013.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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