From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>, Jike Song <albcamus@gmail.com>,
Rijndael Cosque <rijcos@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: What's the status of x2APIC support in Linux kernel?
Date: Thu, 14 Feb 2008 12:06:37 -0700 [thread overview]
Message-ID: <200802141206.37542.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20080201180822.GA376@linux-os.sc.intel.com>
On Friday 01 February 2008 11:08:23 am Siddha, Suresh B wrote:
> On Fri, Feb 01, 2008 at 01:17:14PM +0100, Andi Kleen wrote:
> > "Jike Song" <albcamus@gmail.com> writes:
> >
> > > On 2/1/08, Rijndael Cosque <rijcos@gmail.com> wrote:
> > >> Hi all,
> > >>
> > >> I found the x2APIC spec via http://www.intel.com/products/processor/manuals/.
> > >>
> > >> Looks at present there is no x2APIC support in Linux kernel 2.6.24?
> > >>
> > >> Is there any experimental patch available for Linux kernel? -- I
> > >> googled "x2APIC Linux"; looks no patch for now?
> >
> > There are right no CPUs shipping which implement x2apic.
>
> That's correct. None of the released CPU's support it.
>
> I am working on a patch enabling these future x2apic extensions and the plan
> is to post this kernel patch shortly.
Are you adding x2apic support for both x86 and ia64, or only for x86?
Bjorn
next prev parent reply other threads:[~2008-02-14 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 8:43 Rijndael Cosque
2008-02-01 8:53 ` Jike Song
2008-02-01 12:17 ` Andi Kleen
2008-02-01 18:08 ` Siddha, Suresh B
2008-02-14 19:06 ` Bjorn Helgaas [this message]
2008-02-14 21:48 ` Siddha, Suresh B
2008-02-02 2:55 ` Jike Song
2008-02-02 4:43 ` Andi Kleen
2008-02-02 17:43 ` Yinghai Lu
2008-02-01 9:46 ` Peter Zijlstra
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=200802141206.37542.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=albcamus@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rijcos@gmail.com \
--cc=suresh.b.siddha@intel.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
all inboxes | Powered by JetHome®