All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Simon Horman <horms@verge.net.au>, kexec@lists.infradead.org
Subject: Re: [Patch] kexec: fix the missing i386 part in commit 1100580b05e
Date: Wed, 20 Apr 2011 18:52:02 +0800	[thread overview]
Message-ID: <4DAEBAD2.5080004@redhat.com> (raw)
In-Reply-To: <20110419165359.GI31712@redhat.com>

于 2011年04月20日 00:53, Vivek Goyal 写道:
> On Wed, Apr 20, 2011 at 12:20:13AM +0800, Cong Wang wrote:
>> 于 2011年04月19日 20:47, Cong Wang 写道:
>>> 于 2011年04月18日 20:58, Vivek Goyal 写道:
>>>> Have you verified the contents of backup area? I want to make sure that
>>>> everything is working and in second kernel when we read up vmcore, we
>>>> do read contents properly.
>>>>
>>>
>>> Not yet, I am still trying to figure out what the problem is.
>>> I will send another patch once I know how to fix it, so, although this
>>> patch doesn't fix that problem, it is clearly needed.
>>
>> Ok, the issue I discussed with Vivek does _not_ apply to upstream,
>> that is a mistake when I backported the patch to RHEL5.
>>
>> So, for upstream the patch in this thread is enough.
>>
>> Hope this is clear now.
>
> So again, have you done testing on upstream kernels to make sure backup
> area contents are fine?

I did a crash reboot test and didn't see any problems,
but I didn't check the backup area contents. :-/

I will look at this shortly.

Thanks.

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

      reply	other threads:[~2011-04-20 10:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-17  8:29 [Patch] kexec: fix the missing i386 part in commit 1100580b05e Amerigo Wang
2011-04-18  7:59 ` Simon Horman
2011-04-18 12:58 ` Vivek Goyal
2011-04-19 12:47   ` Cong Wang
2011-04-19 16:20     ` Cong Wang
2011-04-19 16:53       ` Vivek Goyal
2011-04-20 10:52         ` Cong Wang [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=4DAEBAD2.5080004@redhat.com \
    --to=amwang@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.