All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@gmail.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
	fenghua.yu@intel.com, Liujiang <jiang.liu@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-mm@kvack.org,
	Hanjun Guo <guohanjun@huawei.com>,
	WuJianguo <wujianguo@huawei.com>
Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Tue, 19 Feb 2013 13:56:55 -0800	[thread overview]
Message-ID: <CA+8MBbKuBheEj9t8whJBc=S7NdxCF8MvuD2Ajm7suP=7JC01fg@mail.gmail.com> (raw)
In-Reply-To: <5113450C.1080109@huawei.com>

Foolishly sent an earlier reply from Outlook which appears
to have mangled/lost it. Trying again ...

> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M"

Is this where the real problem begins?  Should we insist that users
provide crashkernel
parameters rounded to GRANULE boundaries?

-Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Luck <tony.luck-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Xishi Qiu <qiuxishi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Matt Fleming
	<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	fenghua.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	Liujiang <jiang.liu-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Andrew Morton
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	Hanjun Guo <guohanjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	WuJianguo <wujianguo-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Tue, 19 Feb 2013 13:56:55 -0800	[thread overview]
Message-ID: <CA+8MBbKuBheEj9t8whJBc=S7NdxCF8MvuD2Ajm7suP=7JC01fg@mail.gmail.com> (raw)
In-Reply-To: <5113450C.1080109-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

Foolishly sent an earlier reply from Outlook which appears
to have mangled/lost it. Trying again ...

> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M"

Is this where the real problem begins?  Should we insist that users
provide crashkernel
parameters rounded to GRANULE boundaries?

-Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Luck <tony.luck@gmail.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
	fenghua.yu@intel.com, Liujiang <jiang.liu@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-mm@kvack.org,
	Hanjun Guo <guohanjun@huawei.com>,
	WuJianguo <wujianguo@huawei.com>
Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Tue, 19 Feb 2013 13:56:55 -0800	[thread overview]
Message-ID: <CA+8MBbKuBheEj9t8whJBc=S7NdxCF8MvuD2Ajm7suP=7JC01fg@mail.gmail.com> (raw)
In-Reply-To: <5113450C.1080109@huawei.com>

Foolishly sent an earlier reply from Outlook which appears
to have mangled/lost it. Trying again ...

> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M"

Is this where the real problem begins?  Should we insist that users
provide crashkernel
parameters rounded to GRANULE boundaries?

-Tony

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Tony Luck <tony.luck@gmail.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
	fenghua.yu@intel.com, Liujiang <jiang.liu@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-mm@kvack.org,
	Hanjun Guo <guohanjun@huawei.com>,
	WuJianguo <wujianguo@huawei.com>
Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Tue, 19 Feb 2013 21:56:55 +0000	[thread overview]
Message-ID: <CA+8MBbKuBheEj9t8whJBc=S7NdxCF8MvuD2Ajm7suP=7JC01fg@mail.gmail.com> (raw)
In-Reply-To: <5113450C.1080109@huawei.com>

Foolishly sent an earlier reply from Outlook which appears
to have mangled/lost it. Trying again ...

> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel\x1024M-:600M"

Is this where the real problem begins?  Should we insist that users
provide crashkernel
parameters rounded to GRANULE boundaries?

-Tony

  parent reply	other threads:[~2013-02-19 21:56 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  3:52 [PATCH] ia64/mm: fix a bad_page bug when crash kernel booting Xishi Qiu
2013-01-29  3:52 ` Xishi Qiu
2013-01-29  3:52 ` Xishi Qiu
2013-01-29  3:52 ` Xishi Qiu
2013-02-04 16:32 ` Matt Fleming
2013-02-04 16:32   ` Matt Fleming
2013-02-04 16:32   ` Matt Fleming
2013-02-05  3:48   ` Xishi Qiu
2013-02-05  3:48     ` Xishi Qiu
2013-02-05  3:48     ` Xishi Qiu
2013-02-05  3:48     ` Xishi Qiu
2013-02-07  2:32   ` [PATCH V2] " Xishi Qiu
2013-02-07  2:32     ` Xishi Qiu
2013-02-07  2:32     ` Xishi Qiu
2013-02-07  2:32     ` Xishi Qiu
2013-02-07  6:09     ` [PATCH V3] " Xishi Qiu
2013-02-07  6:09       ` Xishi Qiu
2013-02-07  6:09       ` Xishi Qiu
2013-02-07  6:09       ` Xishi Qiu
2013-02-13  0:11       ` Tony Luck
2013-02-13  0:11         ` Tony Luck
2013-02-13  0:11         ` Tony Luck
2013-02-13  0:11         ` Tony Luck
2013-02-13  0:19         ` Andrew Morton
2013-02-13  0:19           ` Andrew Morton
2013-02-13  0:19           ` Andrew Morton
2013-02-13  0:19           ` Andrew Morton
2013-02-13  0:32           ` Tony Luck
2013-02-13  0:32             ` Tony Luck
2013-02-13  0:32             ` Tony Luck
2013-02-13  0:22         ` Andrew Morton
2013-02-13  0:22           ` Andrew Morton
2013-02-13  0:22           ` Andrew Morton
2013-02-13  0:22           ` Andrew Morton
2013-02-13 10:07       ` Matt Fleming
2013-02-13 10:07         ` Matt Fleming
2013-02-13 10:07         ` Matt Fleming
2013-02-16  1:55         ` Xishi Qiu
2013-02-16  1:55           ` Xishi Qiu
2013-02-16  1:55           ` Xishi Qiu
2013-02-16  1:55           ` Xishi Qiu
2013-02-19 21:38       ` Luck, Tony
2013-02-19 21:38         ` Luck, Tony
2013-02-19 21:38         ` Luck, Tony
2013-02-19 21:56       ` Tony Luck [this message]
2013-02-19 21:56         ` Tony Luck
2013-02-19 21:56         ` Tony Luck
2013-02-19 21:56         ` Tony Luck
2013-02-20  1:38         ` Xishi Qiu
2013-02-20  1:38           ` Xishi Qiu
2013-02-20  1:38           ` Xishi Qiu
2013-02-21 18:21           ` Tony Luck
2013-02-21 18:21             ` Tony Luck
2013-02-21 18:21             ` Tony Luck

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='CA+8MBbKuBheEj9t8whJBc=S7NdxCF8MvuD2Ajm7suP=7JC01fg@mail.gmail.com' \
    --to=tony.luck@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fenghua.yu@intel.com \
    --cc=guohanjun@huawei.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matt.fleming@intel.com \
    --cc=qiuxishi@huawei.com \
    --cc=wujianguo@huawei.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.