From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Petr Holasek <pholasek@redhat.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Anton Arapov <anton@redhat.com>
Subject: Re: [PATCH v2] NUMA x86: add constraints check for nid parameters
Date: Fri, 9 Dec 2011 08:11:09 +0100 [thread overview]
Message-ID: <20111209071109.GE24537@elte.hu> (raw)
In-Reply-To: <m2mxb2nb58.fsf@firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> Petr Holasek <pholasek@redhat.com> writes:
>
> > This patch adds constraints checks for numa_set_distance()
> > function. It emits warning when pxms are used uninitialized
> > when parsing the SRAT.
>
> Can you expand on the motivation for this please?
> Is this to catch buggy code or to catch buggy SRATs?
Both.
> If the later are they actually out there?
Not that i know of - they would likely not boot Linux very well
today.
Thanks,
Ingo
prev parent reply other threads:[~2011-12-09 7:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 11:45 [PATCH RESEND] NUMA x86: add constraints check for nid parameters Petr Holasek
2011-12-01 21:34 ` Andrew Morton
2011-12-01 23:14 ` Petr Holasek
2011-12-01 23:28 ` Andrew Morton
2011-12-02 10:55 ` Petr Holasek
2011-12-06 20:45 ` David Rientjes
2011-12-07 19:40 ` Petr Holasek
2011-12-07 19:43 ` [PATCH v2] " Petr Holasek
2011-12-07 21:46 ` David Rientjes
2011-12-08 12:16 ` [PATCH v3] " Petr Holasek
2011-12-08 21:09 ` David Rientjes
2011-12-09 7:10 ` Ingo Molnar
2011-12-09 10:44 ` David Rientjes
2011-12-09 20:08 ` [tip:x86/mm] x86/numa: Add " tip-bot for Petr Holasek
2011-12-08 18:58 ` [PATCH v2] NUMA x86: add " Andi Kleen
2011-12-08 21:12 ` David Rientjes
2011-12-09 7:11 ` Ingo Molnar [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=20111209071109.GE24537@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=anton@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pholasek@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
/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.