public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Joerg Roedel <joerg.roedel@amd.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	stable@kernel.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] x86: used used_vectors in init_IRQ
Date: Wed, 15 Apr 2009 21:47:05 +0200	[thread overview]
Message-ID: <20090415194705.GA8290@elte.hu> (raw)
In-Reply-To: <49E6397D.1020201@kernel.org>


* Yinghai Lu <yinghai@kernel.org> wrote:

> Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@kernel.org> wrote:
> > 
> >> Ingo Molnar wrote:
> >>
> >>> Note, i removed the -stable tag because i dont think .29 nor 
> >>> .30-rc2 is affected. Your patch to irqinit*.c (and the later 
> >>> unification by Pekka) is something still pending in the 
> >>> perfcounters and x86 trees, queued for .31.
> >> not sure .29, but it seems we need this for 2.6.30
> >>
> 
> you are right...
> 
> in trap_init with linus tree
> 
> still have
> #ifdef CONFIG_X86_64
>         set_bit(IA32_SYSCALL_VECTOR, used_vectors);
> #else
>         set_bit(SYSCALL_VECTOR, used_vectors);
> #endif
> 
> 
> so one patch (merge irqinit_32/64) in tip for .31 expose that bug.
> 
> aka we don't back port ...

ok, good!

	Ingo

  reply	other threads:[~2009-04-15 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 18:57 [PATCH] x86: used used_vectors in init_IRQ Yinghai Lu
2009-04-15 19:25 ` Ingo Molnar
2009-04-15 19:35   ` Yinghai Lu
2009-04-15 19:38     ` Ingo Molnar
2009-04-15 19:46       ` Yinghai Lu
2009-04-15 19:47         ` Ingo Molnar [this message]
2009-04-15 19:52           ` Yinghai Lu
2009-04-15 20:02           ` Yinghai Lu
2009-04-15 20:08             ` Ingo Molnar
2009-04-15 19:48 ` [tip:x86/apic] x86: use used_vectors in init_IRQ() tip-bot for Yinghai Lu

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=20090415194705.GA8290@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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