Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liu hua <sdu.liu@huawei.com>
To: Dave Anderson <anderson@redhat.com>
Cc: horms@verge.net.au, kexec@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	"Discussion list for crash utility usage,
	maintenance and development" <crash-utility@redhat.com>
Subject: Re: [PATCH 0/3] add LPAE support for kexec and kernel (Liu Hua)
Date: Tue, 1 Apr 2014 11:29:05 +0800	[thread overview]
Message-ID: <533A3281.6080907@huawei.com> (raw)
In-Reply-To: <1897155363.7224032.1396021473883.JavaMail.zimbra@redhat.com>

于 2014/3/28 23:44, Dave Anderson 写道:
> 
> 
> ----- Original Message -----
>> On 2014/3/27 22:04, Dave Anderson wrote:
>>>
>>>
>>> ----- Original Message -----
>>>
>>>> The patch series introduce LPAE support for user space
>>>> utility kexec(the last) and ARM linux kernel(the others).
>>>>
>>>> I have tested the patch series in armA15 platform which have
>>>> more than 4G memory.
>>>
>>> Hello Liu,
>>>
>>> I'm curious how you tested this?  The crash utility does not have
>>> any specific support for LPAE on ARM, and a couple years ago I
>>> asked on the crash-utility mailing list whether any of the ARM
>>> developers were working on it.  But at that time none of them were
>>> working with LPAE.  I see that you are on the crash-utility mailing
>>> list -- are you planning to post follow-up patches to the crash-utility?
>>>
>>> Thanks,
>>>   Dave
>>
>> Yes, you are very "sensitive"! our team has worked on it for a while. And
>> we went through the whole kdump process for LPAE enabled ARM. Our changes
>> include kexec-tools, makedumpfile, crash utility and the kernel.
>>
>> But we did that in a rather limited time. So some patches are silly and
>> need to be reconstructed before submission. In addition, my job is quit
>> full now. So I decide to post the patch series that are clear and
>> independent of the others at first.
>>
>> But I got no response from the linux-arm and kexec mailinglist. What about
>> your opinion about the feature of LPAE support for kdump related tools
>> including crash utility and the kernel?
> 
> I can't speak for the linux-arm and kexec mailing lists, but certainly 
> when you post your crash-related patches on the crash-utility mailing 
> list, I'll review, respond, and get them in place as soon as possible.
> 
> Thanks,
>   Dave

Hi Dave,

That's great. I will post crash-related patches after finishing my
work on hand, perhaps two weeks or longer. Thanks to your advice.

Thanks,
Liu Hua



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

      reply	other threads:[~2014-04-01  3:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.28599.1395907790.1059.kexec@lists.infradead.org>
2014-03-27 14:04 ` [PATCH 0/3] add LPAE support for kexec and kernel (Liu Hua) Dave Anderson
2014-03-28 12:05   ` Liu hua
2014-03-28 15:44     ` Dave Anderson
2014-04-01  3:29       ` Liu hua [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=533A3281.6080907@huawei.com \
    --to=sdu.liu@huawei.com \
    --cc=anderson@redhat.com \
    --cc=crash-utility@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.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