public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: "M. Mohan Kumar" <mohan@in.ibm.com>
Cc: Michael Ellerman <michael@ellerman.id.au>,
	kexec@lists.infradead.org, Simon Horman <horms@verge.net.au>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Do not inline putprops function
Date: Mon, 10 Aug 2009 02:37:49 -0500	[thread overview]
Message-ID: <1249889869_10618@mercury.realtime.net> (raw)
In-Reply-To: <20090805164938.GA2970@in.ibm.com>

On Thu Aug 6 at about 02:49:38 EST in 2009, M. Mohan Kumar  wrote:
>
> When I align the dtstruct variable to 8 bytes, I am able to invoke kdump.
> 
> When the line
> 	static unsigned dtstruct[TREEWORDS], *dt;
> changed to 
> 	static unsigned dtstruct[TREEWORDS] __attribute__ ((aligned (8))), *dt;
> 
> kexec-tool works.


Doh.  that is the correct fix.

kexec is creating a version 3 device tree, to be backwards compatible
as far as possible.  (Well, that and it was written before version 3
existed).  This version of the struct has 8-byte alignment for properties
whose value is 8 or more bytes.  As the code directly checks the pointer
when deciding to add the alignment word, the struct memory must start on
an 8 byte boundary.

Mohan, please prepare a patch with the above text in the changelog 
and send it to Simon.

thanks.
milton

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      parent reply	other threads:[~2009-08-10  7:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 11:34 [PATCH] Do not inline putprops function M. Mohan Kumar
2009-06-17 11:45 ` Simon Horman
2009-06-17 11:59   ` M. Mohan Kumar
2009-06-17 12:26     ` Michael Ellerman
2009-06-17 13:04       ` Neil Horman
2009-06-17 13:34         ` M. Mohan Kumar
2009-06-17 14:05           ` Neil Horman
2009-06-17 14:26             ` M. Mohan Kumar
2009-06-17 14:40               ` Neil Horman
2009-06-23 12:55                 ` M. Mohan Kumar
2009-06-23 13:56                   ` Neil Horman
2009-06-24  0:27                     ` Michael Ellerman
2009-08-03  5:49                       ` M. Mohan Kumar
2009-08-05 16:49                         ` M. Mohan Kumar
2009-08-06 14:24                           ` Michael Ellerman
2009-08-07 14:35                             ` M. Mohan Kumar
2009-08-07 14:54                               ` M. Mohan Kumar
2009-08-10  1:51                                 ` Michael Ellerman
2009-08-10  7:37                           ` Milton Miller [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=1249889869_10618@mercury.realtime.net \
    --to=miltonm@bga.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=mohan@in.ibm.com \
    /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