linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K.R. Foley" <kr@cybsft.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	Mike Galbraith <efault@gmx.de>,
	Clark Williams <williams@redhat.com>,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	Giandomenico De Tullio <ghisha@email.it>
Subject: Re: v2.6.19-rt6, yum/rpm
Date: Thu, 07 Dec 2006 13:40:34 -0600	[thread overview]
Message-ID: <45786E32.3010201@cybsft.com> (raw)
In-Reply-To: <20061207165751.GA2720@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 549 bytes --]

Ingo Molnar wrote:
> * K.R. Foley <kr@cybsft.com> wrote:
> 
>> Ingo Molnar wrote:
>>
>> The attached patch is necessary to build 2.6.19-rt8 without KEXEC 
>> enabled. Without KEXEC enabled crash.c doesn't get included. I believe 
>> this is correct.
> 
> ah, indeed. I went for a slightly different approach - see the patch 
> below. Sending an NMI to all CPUs is not something that is tied to 
> KEXEC, it belongs into nmi.c.
> 
> 	Ingo

Much better I think. It still requires the patch below, which includes
mach_ipi.h, to build here.


-- 
   kr

[-- Attachment #2: nmifix2.patch --]
[-- Type: text/x-patch, Size: 315 bytes --]

--- linux-2.6.19/arch/i386/kernel/nmi.c.orig	2006-12-07 13:03:12.000000000 -0600
+++ linux-2.6.19/arch/i386/kernel/nmi.c	2006-12-07 13:03:21.000000000 -0600
@@ -30,6 +30,7 @@
 #include <asm/intel_arch_perfmon.h>
 
 #include "mach_traps.h"
+#include <mach_ipi.h>
 
 int unknown_nmi_panic;
 int nmi_watchdog_enabled;

  reply	other threads:[~2006-12-07 19:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 17:11 v2.6.19-rt6, yum/rpm Ingo Molnar
2006-12-07 11:33 ` K.R. Foley
2006-12-07 12:13   ` Ingo Molnar
2006-12-07 15:54     ` K.R. Foley
2006-12-07 16:57       ` Ingo Molnar
2006-12-07 19:40         ` K.R. Foley [this message]
2006-12-07 20:04           ` Ingo Molnar
2006-12-07 20:45 ` Fernando Lopez-Lezcano
2006-12-07 20:58   ` Ingo Molnar
2006-12-07 21:07     ` Fernando Lopez-Lezcano
2006-12-07 21:42       ` Fernando Lopez-Lezcano
2006-12-07 21:20     ` Arjan van de Ven
2006-12-07 21:44       ` Ingo Molnar
2006-12-08 19:40 ` Ethernet transmit timeouts, was: " Dirk Behme
2006-12-08 20:15   ` Thomas Gleixner
2006-12-09  7:53     ` Ethernet transmit timeouts Dirk Behme
2006-12-10  8:27       ` Ingo Molnar
2006-12-09  4:26   ` Ethernet transmit timeouts, was: v2.6.19-rt6, yum/rpm Bruce Ashfield
2006-12-15 16:18 ` Sergei Shtylyov
2006-12-15 16:19   ` Ingo Molnar
2007-02-01 15:52     ` Sergei Shtylyov
2007-02-01 17:38       ` Ingo Molnar
2007-02-01 17:49         ` Ingo Molnar
2007-02-01 18:01           ` Sergei Shtylyov
2007-03-07 14:55             ` Sergei Shtylyov

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=45786E32.3010201@cybsft.com \
    --to=kr@cybsft.com \
    --cc=efault@gmx.de \
    --cc=ghisha@email.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=sshtylyov@ru.mvista.com \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).