From: Simon Horman <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] kexec/kdump: Use generic elf code on ia64
Date: Tue, 24 Apr 2007 01:49:58 +0000 [thread overview]
Message-ID: <20070424014955.GA14353@verge.net.au> (raw)
In-Reply-To: <20070416074103.GA27981@verge.net.au>
On Fri, Apr 20, 2007 at 01:15:34AM +0800, Zou, Nanhai wrote:
>
> > -----Original Message-----
> > From: Simon Horman [mailto:horms@verge.net.au]
> > Sent: 2007年4月16日 16:21
> > To: fastboot@lists.osdl.org; linux-ia64@vger.kernel.org
> > Cc: Vivek Goyal; Luck, Tony; Zou, Nanhai
> > Subject: Re: [PATCH] kexec/kdump: Use generic elf code on ia64
[snip]
> > -crash_save_this_cpu(void)
> > +ia64_kexec_elf_core_copy_regs(elf_gregset_t *elfregs, struct pt_regs *regs)
> > {
> > - void *buf;
> > unsigned long cfm, sof, sol;
> > -
> > - int cpu = smp_processor_id();
> > - struct elf_prstatus *prstatus = &per_cpu(elf_prstatus, cpu);
> > -
> > - elf_greg_t *dst = (elf_greg_t *)&(prstatus->pr_reg);
> > - memset(prstatus, 0, sizeof(*prstatus));
> > - prstatus->pr_pid = current->pid;
> > + elf_greg_t *dst = (elf_greg_t *)elfregs;
>
> There was a concern about struct elf_prstatus is so big on IA64 that it better not to put it on stack, consider crash happen with a deep stack..., So I put the structure into percpu data.
>
> With this patch, it fallbacks to stack.
Thanks, I was wondering why was per_cpu rather than on the stack.
I'll rework things a bit so per_cpu data is used once again.
[snip]
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
prev parent reply other threads:[~2007-04-24 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 7:41 [PATCH] kexec/kdump: Use generic elf code on ia64 Simon Horman
2007-04-16 8:21 ` Simon Horman
2007-04-19 17:15 ` Zou, Nanhai
2007-04-24 1:49 ` Simon Horman [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=20070424014955.GA14353@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-ia64@vger.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