linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <ak@suse.de>,
	mingo@elte.hu, tglx@linutronix.de, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/8] x86_64: Support for new UV apic
Date: Sun, 30 Mar 2008 21:23:23 -0500	[thread overview]
Message-ID: <20080331022323.GD20619@sgi.com> (raw)
In-Reply-To: <86802c440803301913n1cd4fe88v2374a8ba835153e@mail.gmail.com>

On Sun, Mar 30, 2008 at 07:13:42PM -0700, Yinghai Lu wrote:
> On Sun, Mar 30, 2008 at 7:06 PM, Jack Steiner <steiner@sgi.com> wrote:
> > > so this is "the new one of Friday"?
> >
> >  Yes, and it has the same bug although it is located
> >  in a slightly different place.
> >
> >  A few minutes ago, I posted a patch to delete the extra lines.
> >
> >
> >
> >  > Did you test it on non UV_X2APIC box?
> >
> >  The code is clearly wrong.  I booted on an 8p AMD box and
> >  had no problems. Apparently the kernel (at least basic booting) is
> >  not too sensitive to incorrect apicids being returned. Most
> >  critical-to-boot code must use apicids from the ACPI tables.
> >  However, the bug does affect numa node assignment. And probably
> >  other places, too.
> 
> please consider one global get_apic_id() and bad_apicid to replace
> GET_APIC_ID and BAD_APICID at this point.

I think that makes sense.

The x2apic patch that should be posted in the near future also makes
significant changes in this area.  Once that patch is posted, I'll
make the simplifications.

Ok???

--- jack

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-03-31  2:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 19:12 Jack Steiner
2008-03-28 20:15 ` Ingo Molnar
2008-03-28 20:24   ` Jack Steiner
2008-03-28 20:45     ` Ingo Molnar
2008-03-28 21:08       ` Jack Steiner
2008-03-30 23:22 ` Yinghai Lu
2008-03-31  1:33   ` Yinghai Lu
2008-03-31  2:12     ` Jack Steiner
2008-03-31  2:23       ` Yinghai Lu
2008-03-31  2:26         ` Jack Steiner
2008-03-31  2:29           ` Yinghai Lu
2008-03-31  2:40             ` Jack Steiner
2008-03-31  2:06   ` Jack Steiner
2008-03-31  2:13     ` Yinghai Lu
2008-03-31  2:23       ` Jack Steiner [this message]
2008-03-31  2:27         ` Yinghai Lu
2008-03-31  2:31           ` Jack Steiner
2008-03-31  2:02 ` [PATCH 8/8] x86_64: V2 " Jack Steiner
2008-03-31 13:07   ` Ingo Molnar

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=20080331022323.GD20619@sgi.com \
    --to=steiner@sgi.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox