On 02/01/16 at 09:45pm, Andrew Morton wrote:
> On Thu, 28 Jan 2016 11:57:22 +0300 Dmitry Safonov
> 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
On Thu, 28 Jan 2016 11:57:22 +0300 Dmitry Safonov
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
On 2016/01/28 at 17:02, Dmitry Safonov wrote:
> On 01/28/2016 05:58 AM, Xunlei Pang wrote:
>> Hi Dmitry,
>>
>> On 2016/01/28 at 03:15, Andrew Morton wrote:
>>> On Wed, 27 Jan 2016 14:48:31 +0300 Dmitry Safonov
>>> wrote:
>>>
For allocation of kimage failure or kexec_prepare or load segment
On Thu, 28 Jan 2016 21:12:54 +0800
Xunlei Pang wrote:
> On 2016/01/28 at 20:44, Michael Holzheu wrote:
> > On Thu, 28 Jan 2016 19:56:56 +0800
> > Xunlei Pang wrote:
> >
> >> On 2016/01/28 at 18:32, Michael Holzheu wrote:
> >>> On Wed, 27 Jan 2016 11:15:46 -0800
> >>> Andrew Morton wrote:
> >>>
On 2016/01/28 at 20:44, Michael Holzheu wrote:
> On Thu, 28 Jan 2016 19:56:56 +0800
> Xunlei Pang wrote:
>
>> On 2016/01/28 at 18:32, Michael Holzheu wrote:
>>> On Wed, 27 Jan 2016 11:15:46 -0800
>>> Andrew Morton wrote:
>>>
On Wed, 27 Jan 2016 14:48:31 +0300 Dmitry Safonov
wrote:
>>>
On Thu, 28 Jan 2016 19:56:56 +0800
Xunlei Pang wrote:
> On 2016/01/28 at 18:32, Michael Holzheu wrote:
> > On Wed, 27 Jan 2016 11:15:46 -0800
> > Andrew Morton wrote:
> >
> >> On Wed, 27 Jan 2016 14:48:31 +0300 Dmitry Safonov
> >> wrote:
> >>
> >>> For allocation of kimage failure or kexec_pre
On 2016/01/28 at 18:32, Michael Holzheu wrote:
> On Wed, 27 Jan 2016 11:15:46 -0800
> Andrew Morton wrote:
>
>> On Wed, 27 Jan 2016 14:48:31 +0300 Dmitry Safonov
>> wrote:
>>
>>> For allocation of kimage failure or kexec_prepare or load segments
>>> errors there is no need to keep crashkernel me
On Wed, 27 Jan 2016 11:15:46 -0800
Andrew Morton wrote:
> On Wed, 27 Jan 2016 14:48:31 +0300 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
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
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 c
On 2016/01/27 at 19:48, 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 c
On Wed, 27 Jan 2016 14:48:31 +0300 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 str
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.
Signed
13 matches
Mail list logo
