From: "H. Peter Anvin" <hpa@zytor.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: David Rientjes <rientjes@google.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Casey Dahlin <cdahlin@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] x86: allow ZONE_DMA to be configurable
Date: Thu, 14 Oct 2010 10:44:44 -0700 [thread overview]
Message-ID: <4CB7418C.7010505@zytor.com> (raw)
In-Reply-To: <AANLkTin-VOKXe6wcwt_r3bLcS6=WYJ4EAPPUZWLbEGQF@mail.gmail.com>
On 10/14/2010 09:00 AM, Pekka Enberg wrote:
> On 10/13/2010 09:46 PM, David Rientjes wrote:
>>> I'm not running a CONFIG_EMBEDDED kernel and I'm pretty sure Casey isn't
>>> either, so we'd still need to carry our own patches to change the Kconfig
>>> bool line anyway.
>>>
>>> I'm suprised that we can't allow users who definitively know that they
>>> have no hardware limitations the ability to disable ZONE_DMA. Would a
>>> strong caution in the Kconfig "help" text suffice or will you not be
>>> convinced?
>
> On Thu, Oct 14, 2010 at 6:38 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> CONFIG_EMBEDDED *is* "I am a user who (think I) know what I'm doing".
>> That is *what it is* and *all it is*.
>
> Yup. The naming is quite unfortunate, though. Can we change it to
> something else?
>
Funny, this seems to come up repeatedly ;)
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-10-14 17:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 0:15 [patch] x86: allow ZONE_DMA to be configurable David Rientjes
2010-10-14 0:23 ` H. Peter Anvin
2010-10-14 0:42 ` David Rientjes
2010-10-14 0:44 ` H. Peter Anvin
2010-10-14 0:49 ` David Rientjes
2010-10-14 1:21 ` H. Peter Anvin
2010-10-14 1:48 ` David Rientjes
2010-10-14 2:38 ` H. Peter Anvin
2010-10-14 3:55 ` David Rientjes
2010-10-14 4:37 ` H. Peter Anvin
2010-10-14 4:46 ` David Rientjes
2010-10-14 15:38 ` H. Peter Anvin
2010-10-14 16:00 ` Pekka Enberg
2010-10-14 17:44 ` H. Peter Anvin [this message]
2010-10-14 18:34 ` Ingo Molnar
2010-10-14 19:35 ` Andrew Morton
2010-10-14 20:40 ` H. Peter Anvin
2010-10-15 3:03 ` Ingo Molnar
2010-10-15 4:45 ` H. Peter Anvin
2010-10-15 9:05 ` David Rientjes
2010-10-15 15:06 ` H. Peter Anvin
2010-10-14 22:08 ` David Rientjes
2010-10-14 8:10 ` Andrew Morton
2010-10-14 8:32 ` KOSAKI Motohiro
2010-10-14 22:15 ` David Rientjes
2010-10-14 22:32 ` Andrew Morton
2010-10-15 3:10 ` Ingo Molnar
2010-10-15 9:11 ` David Rientjes
2010-10-15 9:09 ` David Rientjes
2010-10-21 14:56 ` Christoph Lameter
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=4CB7418C.7010505@zytor.com \
--to=hpa@zytor.com \
--cc=cdahlin@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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.