linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Yinghai Lu <yhlu@tyan.com>
Cc: "'Siddha, Suresh B'" <suresh.b.siddha@intel.com>,
	"'Mikael Pettersson'" <mikpe@csd.uu.se>,
	jamesclv@us.ibm.com, Matt_Domsch@dell.com, discuss@x86-64.org,
	linux-kernel@vger.kernel.org
Subject: Re: 256 apic id for amd64
Date: 11 Jan 2005 18:50:28 +0100
Date: Tue, 11 Jan 2005 18:50:28 +0100	[thread overview]
Message-ID: <20050111175028.GB17077@muc.de> (raw)
In-Reply-To: 20050110200425.B30630@unix-os.sc.intel.com

On Tue, Jan 11, 2005 at 09:44:07AM -0800, Yinghai Lu wrote:
> Actually It seems the Opteron System with Nvidia chip set can lift the bsp
> (core0/node0) to 0x10, and the jiffies is still changing in for CPU0. I try
> to enable the 8259 PIC in SB, it will cause the jiffies not changing.
> At the same time in the AMD 8111 SB MB, the 8259 PIC is default enabled, So
> after I lift the APIC id, it will stop jiffies. The problem is after I
> disable the 8259 in amd8111, it will cause other booting problem. maybe the
> io-apic is not enabled properly.

There is code that assumes all legacy interrupts (that includes the timer)
are routed to IO-APIC #0.  I still didn't get quite why you want to 
change that anyways. 

-Andi

  parent reply	other threads:[~2005-01-11 18:03 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 18:44 256 apic id for amd64 Andi Kleen
2005-01-11  4:04 ` Siddha, Suresh B
2005-01-11  4:39   ` Andi Kleen
2005-01-11 17:50   ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-11 19:11 YhLu
2005-01-11 19:04 YhLu
2005-01-10 20:48 YhLu
2005-01-10 20:46 YhLu
2005-01-11  5:36 ` Andi Kleen
2005-01-10 20:37 YhLu
2005-01-10 20:09 YhLu
2005-01-10 20:18 ` Andi Kleen
2005-01-10 19:41 YhLu
2005-01-10 19:43 ` Andi Kleen
2005-01-11  0:42 ` James Cleverdon
2005-01-11  3:28   ` Siddha, Suresh B
2005-01-11  4:42     ` Andi Kleen
2005-01-10 18:48 YhLu
2005-01-10 18:45 ` Andi Kleen
2005-01-08  2:53 YhLu
2005-01-09 23:56 ` James Cleverdon
2005-01-08  2:37 Mikael Pettersson
2005-01-08 15:46 ` Andi Kleen
2005-01-08  1:50 YhLu
2005-01-08  0:50 YhLu
2005-01-08  0:42 ` Andi Kleen
2005-01-08  0:28 YhLu
2005-01-08  0:26 ` James Cleverdon
2005-01-08  0:34   ` Andi Kleen
2005-01-08  0:04 YhLu
2005-01-08  0:12 ` James Cleverdon
2005-01-07 21:44 YhLu
2005-01-07 22:18 ` Andi Kleen
2005-01-07 21:14 YhLu
2005-01-07 21:12 ` Andi Kleen
2005-01-07 19:43 YhLu
2005-01-07 19:40 ` Andi Kleen
2005-01-07 18:27 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 18:19 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07  2:53 YhLu
2005-01-07 12:24 ` Andi Kleen
2005-01-08  1:30   ` James Cleverdon
2005-01-07  1:06 YhLu
2005-01-07 12:44 ` Andi Kleen
2004-12-30 23:19 YhLu
2004-12-30 23:16 YhLu
2004-12-29  4:43 YhLu
2004-12-30 18:45 ` Andi Kleen
2004-12-30 22:56   ` Matt Domsch
2004-12-30 23:26     ` Andi Kleen

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=20050111175028.GB17077@muc.de \
    --to=ak@muc.de \
    --cc=Matt_Domsch@dell.com \
    --cc=discuss@x86-64.org \
    --cc=jamesclv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=suresh.b.siddha@intel.com \
    --cc=yhlu@tyan.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;
as well as URLs for NNTP newsgroup(s).