From: Michael Ellerman <michael@ellerman.id.au>
To: linuxppc64-dev@ozlabs.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why no bigphysarea in mainline?
Date: Fri, 18 Mar 2005 14:42:48 +1100 [thread overview]
Message-ID: <200503181442.51830.michael@ellerman.id.au> (raw)
In-Reply-To: <1111070132.19021.31.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
On Fri, 18 Mar 2005 01:35, Dave Hansen wrote:
> Doing mem= for drivers isn't just a hack, it's *WRONG*. It's a ticking
> time bomb that magically happens to work on some systems. It will not
> work consistently on a discontiguous memory system, or a memory hotplug
> system.
I couldn't agree more. Problem is I've been asked to change the way mem=X
works on PPC64 so that this hack will work, which is a horrible thought.
> Could you give some examples of drivers which are in the kernel that
> could benefit from this patch? We don't tend to put things like this
> in, unless they have actual users. We don't tend to change code for
> out-of-tree users, either.
No I can't. I've been approached by several "vendors" asking about using mem=X
hacks on PPC64, however I doubt any of them have code in-tree. I'll check
though.
cheers
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-03-18 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 9:57 Why no bigphysarea in mainline? Michael Ellerman
2005-03-17 14:35 ` Dave Hansen
2005-03-18 3:42 ` Michael Ellerman [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=200503181442.51830.michael@ellerman.id.au \
--to=michael@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.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