linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] i386: Per node IDT
Date: Sat, 6 Aug 2005 19:13:00 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0508061906050.470@montezuma.fsmlabs.com> (raw)
In-Reply-To: <42D28DE4.B5B17853@tv-sign.ru>

On Mon, 11 Jul 2005, Oleg Nesterov wrote:

> Oleg Nesterov wrote:
> > 
> > Probably it makes sense to change it to
> >         pushl $vector - 0xFFFF - 1
> > 
> 
> Please note that entry.S:BUILD_INTERRUPT() also does this trick:
> 	pushl $nr-256;
> 
> so it should be changed as well.

I was making these changes and noticed that those were for the various SMP 
interrupts so they are real vectors. These will always remain within the 
256 range.

	Zwane


  reply	other threads:[~2005-08-07  1:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 12:28 [RFC][PATCH] i386: Per node IDT Oleg Nesterov
2005-07-11 14:03 ` Zwane Mwaikambo
2005-07-11 14:44   ` Oleg Nesterov
2005-07-11 15:05     ` Zwane Mwaikambo
2005-07-11 15:19     ` Oleg Nesterov
2005-08-07  1:13       ` Zwane Mwaikambo [this message]
2005-08-07 10:47         ` Oleg Nesterov
     [not found] <Pine.LNX.4.61.0507101617240.16055@montezuma.fsmlabs.com.suse.lists.linux.kernel>
2005-07-11  1:59 ` Andi Kleen
2005-07-11  4:02   ` Arjan van de Ven
2005-07-11  4:08     ` Andi Kleen
2005-07-11 14:09     ` Zwane Mwaikambo
2005-07-11 14:05       ` Arjan van de Ven
2005-07-11 15:17       ` Kenji Kaneshige
2005-07-11 13:34   ` Zwane Mwaikambo
2005-07-11 15:03     ` Brian Gerst
2005-07-11 15:21       ` Zwane Mwaikambo
2005-07-11 16:39         ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-07-10 22:41 Zwane Mwaikambo

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=Pine.LNX.4.61.0508061906050.470@montezuma.fsmlabs.com \
    --to=zwane@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    /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).