linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
	Fastboot mailing list <fastboot@lists.osdl.org>
Subject: Re: [Fastboot] [PATCH] kexec: remove memory reserve patching for powerpc	device tree
Date: Thu, 21 Sep 2006 11:51:23 +0900	[thread overview]
Message-ID: <20060921025122.GA8573@verge.net.au> (raw)
In-Reply-To: <1158803944.7062.9.camel@localhost.localdomain>

On Thu, Sep 21, 2006 at 11:59:04AM +1000, Michael Ellerman wrote:
> On Thu, 2006-09-21 at 11:10 +1000, Michael Neuling wrote:
> > This code no longer needed with Jimi's auto reserve of device tree blob
> > kernel patch now in 2.6.18.    
> > 
> > This patch will break Linux if you're kexecing to a kernel which doesn't
> > have this patch (ie. earlier than 2.6.17).  Required kernel patch is
> > this one:   
> > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4d1f3f25d9c303d1ce63b42cc94c54ac0ab2e950
> > 
> 
> Although it'd be nice to get rid of that code, I'm not sure we want to
> go breaking this. This will mean RHEL5 and SLES10 users can't use
> upstream kexec-tools :/

Surely if they are using a RHEL5 or SLES10 kernel then its
reasonably to expect they are also using a RHEL5 or SLES10 supplied
kexec-tool.

I guess it all comes down to backwards compatibility.
And IMHO thats a hard thing to maintain with something
as green as kexec.

I'm in favour of the patch, though I'm prepared to be convinced otherwise.

If the code needs to stay, perhaps this patch could be modified
so that the code in question is only executed if the kernel
is pre 2.6.18. Or is that just overly complex?

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/

  reply	other threads:[~2006-09-21  3:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  1:10 [PATCH] kexec: remove memory reserve patching for powerpc device tree Michael Neuling
2006-09-21  1:59 ` Michael Ellerman
2006-09-21  2:51   ` Horms [this message]
2006-09-21  3:40     ` [Fastboot] " Michael Ellerman
2006-09-21  4:04       ` Michael Neuling
2006-09-21 13:55       ` Vivek Goyal
2006-09-21 14:18         ` Jon Loeliger
2006-09-21 14:32           ` Vivek Goyal
2006-09-22  1:11             ` Michael Neuling
2006-09-22  1:21               ` Horms
2006-09-22 14:23               ` Vivek Goyal

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=20060921025122.GA8573@verge.net.au \
    --to=horms@verge.net.au \
    --cc=fastboot@lists.osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=mikey@neuling.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;
as well as URLs for NNTP newsgroup(s).