All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: x86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM
Date: Sat, 21 Oct 2017 00:20:33 -0700	[thread overview]
Message-ID: <CAE9FiQU+R4Z+3xS9SjUk2i2D8Ht6uhP_pd8maguQOen1UqpgZg@mail.gmail.com> (raw)
In-Reply-To: <20171020055254.GA7095@dhcp-128-65.nay.redhat.com>

On Thu, Oct 19, 2017 at 10:52 PM, Dave Young <dyoung@redhat.com> wrote:
> Now crashkernel=X will fail if there's not enough memory at low region
> (below 896M) when trying to reserve large memory size.  One can use
> crashkernel=xM,high to reserve it at high region (>4G) but it is more
> convinient to improve crashkernel=X to:
>
>  - First try to reserve X below 896M (for being compatible with old
>    kexec-tools).
>  - If fails, try to reserve X below 4G (swiotlb need to stay below 4G).
>  - If fails, try to reserve X from MAXMEM top down.
>
> It's more transparent and user-friendly.

ok with me.

But looks like last time Vivek did not like this idea.

WARNING: multiple messages have this Message-ID (diff)
From: Yinghai Lu <yinghai@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: x86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM
Date: Sat, 21 Oct 2017 00:20:33 -0700	[thread overview]
Message-ID: <CAE9FiQU+R4Z+3xS9SjUk2i2D8Ht6uhP_pd8maguQOen1UqpgZg@mail.gmail.com> (raw)
In-Reply-To: <20171020055254.GA7095@dhcp-128-65.nay.redhat.com>

On Thu, Oct 19, 2017 at 10:52 PM, Dave Young <dyoung@redhat.com> wrote:
> Now crashkernel=X will fail if there's not enough memory at low region
> (below 896M) when trying to reserve large memory size.  One can use
> crashkernel=xM,high to reserve it at high region (>4G) but it is more
> convinient to improve crashkernel=X to:
>
>  - First try to reserve X below 896M (for being compatible with old
>    kexec-tools).
>  - If fails, try to reserve X below 4G (swiotlb need to stay below 4G).
>  - If fails, try to reserve X from MAXMEM top down.
>
> It's more transparent and user-friendly.

ok with me.

But looks like last time Vivek did not like this idea.

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

  reply	other threads:[~2017-10-21  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20  5:52 x86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM Dave Young
2017-10-20  5:52 ` Dave Young
2017-10-21  7:20 ` Yinghai Lu [this message]
2017-10-21  7:20   ` Yinghai Lu
2017-10-23  2:04   ` Dave Young
2017-10-23  2:04     ` Dave Young
2017-10-24  5:27 ` Dave Young
2017-10-24  5:27   ` Dave Young

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=CAE9FiQU+R4Z+3xS9SjUk2i2D8Ht6uhP_pd8maguQOen1UqpgZg@mail.gmail.com \
    --to=yinghai@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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.