All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: Dave Carroll <dcarroll@astekcorp.com>
Cc: Paul Mackerras <paulus@samba.org>,
	LPPC <linuxppc-dev@lists.ozlabs.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RE: [ v4] powerpc: Force page alignment for initrd reserved memory
Date: Mon, 23 May 2011 12:39:06 -0500	[thread overview]
Message-ID: <initrd-align-withdrawn@mdm.bga.com> (raw)
In-Reply-To: <522F24EF533FC546962ECFA2054FF777373072AB78@MAILSERVER2.cos.astekcorp.com>


On Mon, 23 May 2011 about 10:50:07 -0600, Dave Carroll wrote:
> I'm withdrawing this patch for the moment, due to two areas that need
> further research;
> 
> 1) An adjacent FDT blob, as mentioned by Milton Miller, and
> 

Ok ... by the way, see move_device_tree() in arch/powerpc/kernel/prom.c

> 2) Potential interaction with the crash kernel, as used in
>         init/initramfs.c

which already goes around the start and end of crashk_res, which
is adjusted to PAGE_ALIGN in reserve_crashkernel() in machine_kexec.c

 
> If anyone sees other interactions, please feel free to let me know ...
> 
> Thanks,
> -Dave Carroll

One interaction that I have ignored is preserve_initrd overlapping
crash kernel.  Loading the crash kernel destroys the preserved initrd.
But that is beyond the scope of your current patch (and probably a
seperate patch, with cross-architecture scope).

milton

WARNING: multiple messages have this Message-ID (diff)
From: Milton Miller <miltonm@bga.com>
To: Dave Carroll <dcarroll@astekcorp.com>
Cc: LPPC <linuxppc-dev@lists.ozlabs.org>,
	Paul Mackerras <paulus@samba.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Subject: RE: [ v4] powerpc: Force page alignment for initrd reserved memory
Date: Mon, 23 May 2011 12:39:06 -0500	[thread overview]
Message-ID: <initrd-align-withdrawn@mdm.bga.com> (raw)
In-Reply-To: <522F24EF533FC546962ECFA2054FF777373072AB78@MAILSERVER2.cos.astekcorp.com>


On Mon, 23 May 2011 about 10:50:07 -0600, Dave Carroll wrote:
> I'm withdrawing this patch for the moment, due to two areas that need
> further research;
> 
> 1) An adjacent FDT blob, as mentioned by Milton Miller, and
> 

Ok ... by the way, see move_device_tree() in arch/powerpc/kernel/prom.c

> 2) Potential interaction with the crash kernel, as used in
>         init/initramfs.c

which already goes around the start and end of crashk_res, which
is adjusted to PAGE_ALIGN in reserve_crashkernel() in machine_kexec.c

 
> If anyone sees other interactions, please feel free to let me know ...
> 
> Thanks,
> -Dave Carroll

One interaction that I have ignored is preserve_initrd overlapping
crash kernel.  Loading the crash kernel destroys the preserved initrd.
But that is beyond the scope of your current patch (and probably a
seperate patch, with cross-architecture scope).

milton

  reply	other threads:[~2011-05-23 17:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 21:26 [PATCH]powerpc: Force page alignment for early reserved memory Dave Carroll
2011-05-20 21:26 ` Dave Carroll
2011-05-20 22:27 ` Benjamin Herrenschmidt
2011-05-20 22:27   ` Benjamin Herrenschmidt
2011-05-20 23:23   ` [PATCH v2]powerpc: Force page alignment for initrd Dave Carroll
2011-05-20 23:23     ` Dave Carroll
2011-05-21 10:36     ` [v2] powerpc: " Milton Miller
2011-05-21 10:36       ` Milton Miller
2011-05-21 17:05       ` [PATCH v3] powerpc: Force page alignment for initrd reserved memory Dave Carroll
2011-05-21 17:05         ` Dave Carroll
2011-05-22 21:17         ` [PATCH v3] powerpc: Force page alignment for initrd reserved memory, " 'Milton Miller'
2011-05-22 21:17           ` 'Milton Miller'
2011-05-23  1:29           ` Dave Carroll
2011-05-23  1:29             ` Dave Carroll
2011-05-23  2:31           ` [PATCH v4] " Dave Carroll
2011-05-23  2:31             ` Dave Carroll
2011-05-23 16:50             ` [ " Dave Carroll
2011-05-23 16:50               ` Dave Carroll
2011-05-23 17:39               ` Milton Miller [this message]
2011-05-23 17:39                 ` Milton Miller
2011-05-23 22:54                 ` [PATCH v5] " Dave Carroll
2011-05-23 22:54                   ` Dave Carroll
2011-05-25  9:28                   ` [v5] " Milton Miller
2011-05-25  9:28                     ` Milton Miller
2011-05-26  2:00                     ` [PATCH v6] " Dave Carroll
2011-05-26  2:00                       ` Dave Carroll
2011-05-26  2:32                     ` [PATCH v7] " Dave Carroll
2011-05-26  2:32                       ` Dave Carroll
2011-05-26 11:18                       ` Milton Miller
2011-05-26 11:18                         ` Milton Miller
2011-05-26 16:53                         ` [PATCH v8] " Dave Carroll
2011-05-26 16:53                           ` Dave Carroll
2011-06-11  1:38                     ` [PATCH 1/2] powerpc: Move free_initmem to common code Dave Carroll
2011-06-11  1:38                       ` Dave Carroll
2011-06-11  1:38                       ` [PATCH 2/2] powerpc: Add printk companion for ppc_md.progress Dave Carroll
2011-06-11  1:38                         ` Dave Carroll

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=initrd-align-withdrawn@mdm.bga.com \
    --to=miltonm@bga.com \
    --cc=dcarroll@astekcorp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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.