From: "Jike Song" <albcamus@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Rijndael Cosque" <rijcos@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: What's the status of x2APIC support in Linux kernel?
Date: Sat, 2 Feb 2008 10:55:06 +0800 [thread overview]
Message-ID: <df9815e70802011855p29c10787lcee23bc9fab181d4@mail.gmail.com> (raw)
In-Reply-To: <p73fxwc50s5.fsf@bingen.suse.de>
On 2/1/08, Andi Kleen <andi@firstfloor.org> wrote:
> There are right no CPUs shipping which implement x2apic.
Thanks for your information.
> "Jike Song" <albcamus@gmail.com> writes:
> > Maybe. I have a question as well, what about the status of I/O
> > xAPIC support in linux? If it is not supported yet, is there any
> > effort to add it? I'm interested in that, hopefully can take part in
> > the development.
>
> xAPIC has been supported forever.
Thank you for your attention, Andi.
Oh, what do I mean is "I/O xAPIC", but not the "local xAPIC" or xAPIC
interrupt architecture introduced by Intel Pentium4 CPU. It seems
that the "I/O xAPIC" hasn't been well documented yet, but some other
document do have some description about it. Some Intel guys gave me
an URL for the document:
http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_Direct_IO.pdf
Section 5 and section 9.5 describe 'I/OxAPIC'. I'm not sure if it is
already supported by Linux, I guess it is not.
--
Best Regards,
Jike
next prev parent reply other threads:[~2008-02-02 2:55 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
2008-02-14 21:48 ` Siddha, Suresh B
2008-02-02 2:55 ` Jike Song [this message]
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=df9815e70802011855p29c10787lcee23bc9fab181d4@mail.gmail.com \
--to=albcamus@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rijcos@gmail.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®