From: Hui Zhu <teawater@gmail.com>
To: Amerigo Wang <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix the multithread program core thread message error
Date: Wed, 1 Jul 2009 11:29:14 +0800 [thread overview]
Message-ID: <daef60380906302029r1f2ad54dk30dd3d75ad53624@mail.gmail.com> (raw)
In-Reply-To: <daef60380906302027i39097bd6wc336f44763cf32bc@mail.gmail.com>
On Wed, Jul 1, 2009 at 11:27, Hui Zhu<teawater@gmail.com> wrote:
> Hi Amerigo,
>
> Thanks for your reply.
>
> On Wed, Jul 1, 2009 at 08:54, Amerigo Wang<xiyou.wangcong@gmail.com> wrote:
>>
>> Hi, Hui.
>>
>> On Tue, Jun 30, 2009 at 05:12:31PM +0800, Hui Zhu wrote:
>>>Fix the multithread program core thread message error.
>>>The thread message of core file is generated in
>>>elf_dump_thread_status. The register values is set by
>>>elf_core_copy_task_regs in this function.
>>>static inline int elf_core_copy_task_regs(struct task_struct *t,
>>> elf_gregset_t* elfregs)
>>>{
>>>
>>> return ELF_CORE_COPY_TASK_REGS(t, elfregs);
>>> return 0;
>>>}
>>>If a arch doesn't define ELF_CORE_COPY_TASK_REGS, This function will do
>>>nothing. Then the core file will not have the register message of
>>>thread.
>>>So add elf_core_copy_regs to set regiser values if
>>>ELF_CORE_COPY_TASK_REGS doesn't define.
>>
>>
>> You forgot your Signed-off-by line. :)
>
> Signed-off-by: Hui Zhu <hui.zhu@windriver.com>
I need change it to Signed-off-by: Hui Zhu <teawater@gmail.com>
Sorry about it.
Thanks,
Hui
next prev parent reply other threads:[~2009-07-01 3:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 9:12 Hui Zhu
2009-07-01 0:54 ` Amerigo Wang
2009-07-01 3:27 ` Hui Zhu
2009-07-01 3:29 ` Hui Zhu [this message]
2009-07-01 4:51 ` Amerigo Wang
2009-07-01 6:21 ` Hui Zhu
2009-07-01 7:20 ` Amerigo Wang
2009-07-01 8:16 ` Hui Zhu
2009-07-01 19:05 ` Andrew Morton
2009-07-01 19:19 ` Bill Gatliff
2009-07-03 9:48 ` Amerigo Wang
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=daef60380906302029r1f2ad54dk30dd3d75ad53624@mail.gmail.com \
--to=teawater@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®