mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <jbeulich@novell.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Andi Kleen <andi@firstfloor.org>,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386: improve double fault handling
Date: Mon, 21 Jul 2008 13:05:10 +0200	[thread overview]
Message-ID: <20080721110510.GC10782@elte.hu> (raw)
In-Reply-To: <48846B02.76E4.0078.0@novell.com>


* Jan Beulich <jbeulich@novell.com> wrote:

> > This patch doesn't apply for me to the extent that I'm hesitant to 
> > fix it up manually.  Could you please refresh it against current 
> > -linus?
> 
> Make the double fault handler use CPU-specific stacks. Add some 
> abstraction to simplify future change of other exception handlers to 
> go through task gates. Add a new notification of the event through the 
> die notifier chain, also providing some environmental adjustments so 
> that various infrastructural things work independent of the fact that 
> the fault and the callbacks are running on other then the normal 
> kernel stack.

this still doesnt apply to latest -git. (or tip/master)

	Ingo

  reply	other threads:[~2008-07-21 11:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 12:30 Jan Beulich
2008-07-18 23:24 ` H. Peter Anvin
2008-07-21  8:54   ` Jan Beulich
2008-07-21 11:05     ` Ingo Molnar [this message]
2008-07-22 10:13       ` Jan Beulich
2008-07-28 13:42         ` Ingo Molnar
2008-07-28 13:45           ` H. Peter Anvin
2008-07-28 13:59           ` Jan Beulich
2008-07-28 14:02             ` H. Peter Anvin
2008-07-28 16:28               ` Ingo Molnar
2008-07-28 22:00           ` Chuck Ebbert
2008-07-31 10:46             ` Ingo Molnar
2008-07-23 21:43 ` Joerg Roedel
2008-07-24  7:08   ` Jan Beulich
2008-07-24 13:24     ` H. Peter Anvin

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=20080721110510.GC10782@elte.hu \
    --to=mingo@elte.hu \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®