mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	jerry.hoemann@hp.com, Pekka Enberg <penberg@kernel.org>,
	Rob Landley <rob@landley.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, x86 maintainers <x86@kernel.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"list@ebiederm.org:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	"list@ebiederm.org:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	linux-efi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Early use of boot service memory
Date: Mon, 18 Nov 2013 10:29:18 -0800	[thread overview]
Message-ID: <528A5C7E.5080007@zytor.com> (raw)
In-Reply-To: <20131118152255.GA32168@redhat.com>

On 11/18/2013 07:22 AM, Vivek Goyal wrote:
> 
> And if that's true, then reserving 72M extra due to crashkernel=X,high
> should not be a big issue in KVM guests. It will still be an issue on
> physical servers though.
> 

Yes, but there it is a single instance and not a huge amount of RAM.

	-hpa



  reply	other threads:[~2013-11-18 18:30 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12  2:15 Jerry Hoemann
2013-11-12  2:15 ` [PATCH 1/3] efi: " Jerry Hoemann
2013-11-12  2:15 ` [PATCH 2/3] x86: avoid efi_reserve_boot_services Jerry Hoemann
2013-11-12  2:15 ` [PATCH 3/3] x86, efi: Early use of boot service memory Jerry Hoemann
2013-11-12 10:37 ` [PATCH 0/3] " Pekka Enberg
2013-11-12 17:55   ` jerry.hoemann
2013-11-12 18:48     ` Pekka Enberg
2013-11-12 21:52       ` jerry.hoemann
2013-11-12 18:58 ` H. Peter Anvin
2013-11-13 22:45   ` jerry.hoemann
2013-11-13 22:49     ` H. Peter Anvin
2013-11-13 23:57       ` jerry.hoemann
2013-11-14  0:05         ` H. Peter Anvin
2013-11-14  1:40           ` jerry.hoemann
2014-08-01  9:54           ` Yuhong Bao
2013-11-14  8:24         ` Pekka Enberg
2013-11-14 18:04           ` jerry.hoemann
2013-11-14 18:44             ` Pekka Enberg
2013-11-14 18:45               ` H. Peter Anvin
2013-11-15  0:50               ` jerry.hoemann
2013-11-15  6:24                 ` Ingo Molnar
2013-11-15  6:55                   ` Yinghai Lu
2013-11-15  6:59                     ` H. Peter Anvin
2013-11-15 14:07                       ` Vivek Goyal
2013-11-15 17:33                         ` Yinghai Lu
2013-11-15 17:40                           ` H. Peter Anvin
2013-11-15 18:30                             ` Vivek Goyal
2013-11-15 18:46                               ` H. Peter Anvin
2013-11-15 19:16                                 ` H. Peter Anvin
2013-11-18 15:22                                   ` Vivek Goyal
2013-11-18 18:29                                     ` H. Peter Anvin [this message]
2013-11-18 18:52                                       ` Vivek Goyal
2013-11-19  1:32                               ` H. Peter Anvin
2013-11-19  3:02                                 ` Yinghai Lu
2013-11-15 18:03                           ` Vivek Goyal
2013-11-15 22:24                             ` Yinghai Lu
2013-11-15 22:55                               ` jerry.hoemann
2013-11-15 23:43                                 ` Yinghai Lu
2013-11-18 15:32                               ` Vivek Goyal
2013-11-18 19:34                                 ` Yinghai Lu
2013-11-18 19:39                                   ` Vivek Goyal
2013-11-15 18:16                       ` jerry.hoemann
2013-11-15 19:13                   ` jerry.hoemann
2013-11-18 15:42                     ` Vivek Goyal
2013-11-15  8:36                 ` Pekka Enberg
2013-11-14 15:26       ` Vivek Goyal

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=528A5C7E.5080007@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=jerry.hoemann@hp.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=penberg@kernel.org \
    --cc=rob@landley.net \
    --cc=tglx@linutronix.de \
    --cc=vgoyal@redhat.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome