Date: Thu, 24 Jul 2008 07:03:00 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, suresh.b.siddha@intel.com,
       hpa@zytor.com, tglx@linutronix.de, arjan@linux.intel.com,
       andi@firstfloor.org, ebiederm@xmission.com, jbarnes@virtuousgeek.org,
       steiner@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 00/26] x64, x2apic/intr-remap: Interrupt-remapping and
	x2apic support
Message-ID: <20080724050300.GB25161@elte.hu>
References: <20080710181634.764954000@linux-os.sc.intel.com> <20080710195320.GA23322@elte.hu> <20080722134909.2cbf719b.akpm@linux-foundation.org> <48864A7F.3050908@sgi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48864A7F.3050908@sgi.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1657
Lines: 40


* Mike Travis <travis@sgi.com> wrote:

> Andrew Morton wrote:
> > On Thu, 10 Jul 2008 21:53:20 +0200
> > Ingo Molnar <mingo@elte.hu> wrote:
> > 
> >> For review and testing purposes i've created a new topic branch for 
> >> this: tip/x86/x2apic and have picked up your patches into it.
> > 
> > This has today turned up in linux-next and I'm having to rework 2.6.27
> > patches to compensate for it.
> > 
> > Which means that I now need to wait until this work goes into mainline
> > before I can merge those patches or I need to undo those fixes, route
> > around Suresh's changes and then force you to fix the resulting damage.
> > 
> > What's the score here?  Is this stuff going into 2.6.27?
> 
> Hi Andrew,
> 
> Jack is out at OLS this week, but yes I believe we're trying to push 
> this into 6.2.27 as that is what the distro's will be basing their 
> distributions on when the new system sees the light of day.

Note that this is the generic x2apic work from Intel, not the SGI/UV 
specific x2apic stuff. The SGI-specific code is upstream already. (and 
as i understand it was based on an earlier version of the Intel code)

The Intel x2apic code was submitted before the merge window but was 
indeed pushed to linux-next during the window because that's when its 
integration became fully ready. We'd rather not hold the whole merge 
window and linux-next hostage with not fully ready stuff :-)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/