From: Ingo Molnar <mingo@elte.hu>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [patch 1/2] x2apic: fix reserved APIC register accesses in print_local_APIC()
Date: Fri, 5 Sep 2008 18:04:14 +0200 [thread overview]
Message-ID: <20080905160414.GL10292@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.55.0809032145020.23174@cliff.in.clinika.pl>
* Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Wed, 3 Sep 2008, Suresh Siddha wrote:
>
> > from SDV Vol 3a Section 17.27.1
> >
> > The remote read delivery mode provided in the 82489DX and local APIC for
> > Pentium processors is not supported in the local APIC in the Pentium 4, Intel
> > Xeon, and P6 family processors.
> >
> > It looks like it is not supported (officially atleast) even in APIC bus
> > architectures. Only the Pentium integrated APIC seems to be the exception.
>
> Yeah, trust documentation and see where you'll get... ;)
hm, is the remote read debug output, now that it's not present in CPUs
made in the past 5 years or so, really that important?
Ingo
next prev parent reply other threads:[~2008-09-05 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 23:46 [patch 1/2] x2apic: fix reserved APIC register accesses in print_local_APIC() Suresh Siddha
2008-09-02 23:46 ` [patch 2/2] x2apic: fix using early fixmap mapping for DMAR table parsing Suresh Siddha
2008-09-03 5:28 ` [patch 1/2] x2apic: fix reserved APIC register accesses in print_local_APIC() Maciej W. Rozycki
2008-09-03 18:45 ` Suresh Siddha
2008-09-03 21:28 ` Maciej W. Rozycki
2008-09-05 16:04 ` Ingo Molnar [this message]
2008-09-05 21:02 ` Maciej W. Rozycki
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=20080905160414.GL10292@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.