From: David Miller <davem@davemloft.net>
To: apenwarr@gmail.com
Cc: akpm@linux-foundation.org, josh@joshtriplett.org,
paulmck@linux.vnet.ibm.com, mingo@elte.hu,
a.p.zijlstra@chello.nl, fdinitto@redhat.com, hannes@cmpxchg.org,
olaf@aepfle.de, paul.gortmaker@windriver.com, tj@kernel.org,
hpa@linux.intel.com, yinghai@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/5] Persist printk buffer across reboots.
Date: Tue, 13 Mar 2012 00:18:42 -0700 (PDT) [thread overview]
Message-ID: <20120313.001842.1454669292182923878.davem@davemloft.net> (raw)
In-Reply-To: <CAHqTa-3sMRJ0p7driNF+d=f_NZNCF-+TWnCSNO2efEdfv0ayVQ@mail.gmail.com>
From: Avery Pennarun <apenwarr@gmail.com>
Date: Tue, 13 Mar 2012 03:14:21 -0400
> On Tue, Mar 13, 2012 at 2:50 AM, David Miller <davem@davemloft.net> wrote:
>> The idea is that you call prom_retain() before you take a look at what
>> physical memory is available in the kernel, and the firmware takes
>> this physical chunk out of those available memory lists upon
>> prom_retain() success.
>
> This sounds like exactly the API I would have wanted, however:
>
> 1) It's only available in arch/sparc so I can't test my patch if I try
> to use it;
> 2) There's nobody that calls it so it might not work;
> 3) I don't understand the API so I'm not really confident that
> reserving memory this way will actually prevent it from being seen by
> the kernel.
>
> In short, I think I would screw it up.
I'm only saying that you should design your stuff such that an
architecture with such features could easily hook into it using this
kind facility.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-03-13 7:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 5:36 Avery Pennarun
2012-03-13 5:36 ` [PATCH 1/5] mm: bootmem: BUG() if you try to allocate bootmem too late Avery Pennarun
2012-03-13 5:36 ` [PATCH 2/5] mm: bootmem: it's okay to reserve_bootmem an invalid address Avery Pennarun
2012-03-13 5:36 ` [PATCH 3/5] mm: nobootmem: implement reserve_bootmem() in terms of memblock Avery Pennarun
2012-03-13 5:36 ` [PATCH 4/5] printk: use alloc_bootmem() instead of memblock_alloc() Avery Pennarun
2012-03-13 6:13 ` Yinghai Lu
2012-03-13 6:40 ` Avery Pennarun
2012-03-13 8:26 ` Ingo Molnar
2012-03-13 21:50 ` Yinghai Lu
2012-03-14 2:23 ` Avery Pennarun
2012-03-13 5:36 ` [PATCH 5/5] printk: CONFIG_PRINTK_PERSIST: persist printk buffer across reboots Avery Pennarun
2012-03-13 5:53 ` [PATCH 0/5] Persist " David Miller
2012-03-13 6:00 ` Avery Pennarun
2012-03-13 6:50 ` David Miller
2012-03-13 7:14 ` Avery Pennarun
2012-03-13 7:18 ` David Miller [this message]
2012-03-13 8:10 ` Avery Pennarun
2012-03-13 8:16 ` David Miller
2012-03-13 13:50 ` Peter Zijlstra
2012-03-14 1:57 ` Daniel Walker
2012-03-13 8:32 ` Stephen Boyd
2012-03-13 17:08 ` Daniel Walker
2012-03-13 22:10 ` Andrew Morton
2012-03-14 2:19 ` Daniel Walker
2012-03-15 22:10 ` Seiji Aguchi
2012-03-14 2:21 ` Avery Pennarun
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=20120313.001842.1454669292182923878.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=apenwarr@gmail.com \
--cc=fdinitto@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@linux.intel.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=olaf@aepfle.de \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tj@kernel.org \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox