All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minfei Huang <mhuang@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dmitry Safonov <dsafonov@virtuozzo.com>,
	linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, ebiederm@xmission.com,
	linux-s390@vger.kernel.org, 0x7f454c46@gmail.com,
	kexec@lists.infradead.org, holzheu@linux.vnet.ibm.com,
	dyoung@redhat.com
Subject: Re: [PATCH] kexec: unmap reserved pages for each error-return way
Date: Tue, 2 Feb 2016 21:56:32 +0800	[thread overview]
Message-ID: <20160202135632.GA4499@dhcp-128-25.nay.redhat.com> (raw)
In-Reply-To: <20160201214540.c0b4b8c2.akpm@linux-foundation.org>

On 02/01/16 at 09:45pm, Andrew Morton wrote:
> On Thu, 28 Jan 2016 11:57:22 +0300 Dmitry Safonov <dsafonov@virtuozzo.com> wrote:
> 
> > On 01/28/2016 09:29 AM, Minfei Huang wrote:
> > > On 01/27/16 at 02:48pm, Dmitry Safonov wrote:
> > >> For allocation of kimage failure or kexec_prepare or load segments
> > >> errors there is no need to keep crashkernel memory mapped.
> > >> It will affect only s390 as map/unmap hook defined only for it.
> > >> As on unmap s390 also changes os_info structure let's check return code
> > >> and add info only on success.
> > > Hi, Dmitry.
> > >
> > > Previously, I sent a patch to fix this issue. You can refer it in
> > > following link.
> > >
> > > http://lists.infradead.org/pipermail/kexec/2015-July/013960.html
> > Oh, scratch my patch - I'm fine with yours, wanted to do the similar thing
> > because it has dazzled me while I was debugging around.
> 
> There were a bunch of patches tossed around in that thread but I'm not
> sure that anything actually got applied?  Perhaps some resending is
> needed.
> 

Hi, Andrew.

I will work on it to update a new patch.

Thanks
Minfei

WARNING: multiple messages have this Message-ID (diff)
From: Minfei Huang <mhuang@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-s390@vger.kernel.org,
	Dmitry Safonov <dsafonov@virtuozzo.com>,
	heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org,
	ebiederm@xmission.com, 0x7f454c46@gmail.com,
	schwidefsky@de.ibm.com, holzheu@linux.vnet.ibm.com,
	dyoung@redhat.com, kexec@lists.infradead.org
Subject: Re: [PATCH] kexec: unmap reserved pages for each error-return way
Date: Tue, 2 Feb 2016 21:56:32 +0800	[thread overview]
Message-ID: <20160202135632.GA4499@dhcp-128-25.nay.redhat.com> (raw)
In-Reply-To: <20160201214540.c0b4b8c2.akpm@linux-foundation.org>

On 02/01/16 at 09:45pm, Andrew Morton wrote:
> On Thu, 28 Jan 2016 11:57:22 +0300 Dmitry Safonov <dsafonov@virtuozzo.com> wrote:
> 
> > On 01/28/2016 09:29 AM, Minfei Huang wrote:
> > > On 01/27/16 at 02:48pm, Dmitry Safonov wrote:
> > >> For allocation of kimage failure or kexec_prepare or load segments
> > >> errors there is no need to keep crashkernel memory mapped.
> > >> It will affect only s390 as map/unmap hook defined only for it.
> > >> As on unmap s390 also changes os_info structure let's check return code
> > >> and add info only on success.
> > > Hi, Dmitry.
> > >
> > > Previously, I sent a patch to fix this issue. You can refer it in
> > > following link.
> > >
> > > http://lists.infradead.org/pipermail/kexec/2015-July/013960.html
> > Oh, scratch my patch - I'm fine with yours, wanted to do the similar thing
> > because it has dazzled me while I was debugging around.
> 
> There were a bunch of patches tossed around in that thread but I'm not
> sure that anything actually got applied?  Perhaps some resending is
> needed.
> 

Hi, Andrew.

I will work on it to update a new patch.

Thanks
Minfei

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

  reply	other threads:[~2016-02-02 13:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 11:48 [PATCH] kexec: unmap reserved pages for each error-return way Dmitry Safonov
2016-01-27 11:48 ` Dmitry Safonov
2016-01-27 11:48 ` Dmitry Safonov
2016-01-27 19:15 ` Andrew Morton
2016-01-27 19:15   ` Andrew Morton
2016-01-27 19:15   ` Andrew Morton
2016-01-28 10:32   ` Michael Holzheu
2016-01-28 10:32     ` Michael Holzheu
2016-01-28 10:32     ` Michael Holzheu
2016-01-28 11:56     ` Xunlei Pang
2016-01-28 11:56       ` Xunlei Pang
2016-01-28 12:44       ` Michael Holzheu
2016-01-28 12:44         ` Michael Holzheu
2016-01-28 13:12         ` Xunlei Pang
2016-01-28 13:12           ` Xunlei Pang
2016-01-28 14:01           ` Michael Holzheu
2016-01-28 14:01             ` Michael Holzheu
     [not found]   ` <56A983F3.5010506@redhat.com>
     [not found]     ` <56A9D927.70402@virtuozzo.com>
2016-01-29  3:14       ` Xunlei Pang
2016-01-29  3:14         ` Xunlei Pang
2016-01-28  3:36 ` Xunlei Pang
2016-01-28  3:36   ` Xunlei Pang
2016-01-28  6:29 ` Minfei Huang
2016-01-28  6:29   ` Minfei Huang
2016-01-28  8:57   ` Dmitry Safonov
2016-01-28  8:57     ` Dmitry Safonov
2016-01-28  8:57     ` Dmitry Safonov
2016-02-02  5:45     ` Andrew Morton
2016-02-02  5:45       ` Andrew Morton
2016-02-02  5:45       ` Andrew Morton
2016-02-02 13:56       ` Minfei Huang [this message]
2016-02-02 13:56         ` Minfei Huang

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=20160202135632.GA4499@dhcp-128-25.nay.redhat.com \
    --to=mhuang@redhat.com \
    --cc=0x7f454c46@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dsafonov@virtuozzo.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.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 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.