public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: suresh.b.siddha@intel.com
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Possible x2apic breakage
Date: Thu, 29 Jan 2009 09:41:46 -0600	[thread overview]
Message-ID: <20090129154146.GA2694@sgi.com> (raw)

Suresh -

This popped up in Ingo's x86 tree yesterday. This appears to be breaking
on our simulator running in x2apic mode. If I understand the code,
this is a real breakage and not a problem in our simulator:


arch/x86/include/asm/genapic.h

	static inline unsigned int read_apic_id(void)
	{
        	unsigned int reg;

        	reg = *(u32 *)(APIC_BASE + APIC_ID);
        	return apic->get_apic_id(reg);
	}


As expected, the failure occurs right after:

	Enabling x2apic
	Enabled x2apic and interrupt-remapping

The next reference to apicid tries to read from mem instead of MSRs.


--- jack


             reply	other threads:[~2009-01-29 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 15:41 Jack Steiner [this message]
2009-01-29 16:15 ` Possible x2apic breakage Ingo Molnar
2009-01-29 20:03   ` Jack Steiner

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=20090129154146.GA2694@sgi.com \
    --to=steiner@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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