From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@suse.cz>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] x86: Make NUMA on 32-bit depend on BROKEN
Date: Tue, 11 Nov 2008 15:08:58 +0100 [thread overview]
Message-ID: <200811111508.58886.rjw@sisk.pl> (raw)
In-Reply-To: <20081111094617.GB16496@elte.hu>
On Tuesday, 11 of November 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
>
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> > Subject: x86: Make NUMA on 32-bit depend on BROKEN
> >
> > While investigating the failure of hibernation on 32-bit x86 with
> > CONFIG_NUMA set, as described in this message
> > http://marc.info/?l=linux-kernel&m=122634118116226&w=4 I asked some
> > people for help and I was told that it wasn't really worth the
> > effort, because CONFIG_NUMA was generally broken on 32-bit x86
> > systems and it shouldn't be used in such configs. For this reason,
> > make CONFIG_NUMA depend on BROKEN instead of EXPERIMENTAL on x86-32.
>
> Actually, it works just fine on a wide range of 32-bit systems that i
> have, so NAK.
>
> Hibernation might not work but that's i believe a NUMA<->HIBERNATION
> interaction issue, we need to fix that. Regular system bootup and
> stress-tests work just fine.
OK, so it seems I'll have to find out what exactly happens. :-(
Thanks,
Rafael
prev parent reply other threads:[~2008-11-11 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 20:52 Rafael J. Wysocki
2008-11-11 8:41 ` Pavel Machek
2008-11-11 9:46 ` Ingo Molnar
2008-11-11 14:08 ` Rafael J. Wysocki [this message]
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=200811111508.58886.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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®