Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>
Cc: Kees Cook <keescook@chromium.org>, Cong Ding <dinggnu@gmail.com>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>, Michael Davidson <md@google.com>,
	Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Yinghai Lu <yinghai@kernel.org>,
	Mathias Krause <minipli@googlemail.com>
Subject: Re: [GIT PULL] x86/kaslr for v3.14
Date: Fri, 07 Feb 2014 15:20:32 -0800	[thread overview]
Message-ID: <52F56A40.60707@zytor.com> (raw)
In-Reply-To: <20140207231626.GA3840@dhcp-16-126.nay.redhat.com>

On 02/07/2014 03:16 PM, Dave Young wrote:
> 
> Hi Vivek,
> 
> Chaowang <chaowang@redhat.com> is looking into passing setup_data SETUP_E820_EXT
> instead of using exactmap. Previously Thomas Renninger tried passing them in e820.
> I did not find the old thread, but I remember it's not enough because of the
> 128 entries limitation. 
> 

THERE IS NO SUCH LIMITATION.

Only 128 slots fit in struct boot_params, but additional entries can be
added to the setup_data linked list.

	-hpa


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

  reply	other threads:[~2014-02-07 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201401201647.s0KGlZdh004167@tazenda.hos.anvin.org>
     [not found] ` <CAFLxGvxO1MPDDjEh3FU5Gv2-eb6zBJxYtTnKdABDTTpbMxxYAw@mail.gmail.com>
     [not found]   ` <52E5EFAF.3060609@linux.intel.com>
     [not found]     ` <CAFLxGvxJ0A6hZ52RWffkg_zXXScyPn10P4HcKvdAXfE43h32Eg@mail.gmail.com>
     [not found]       ` <52E601DA.7010605@zytor.com>
     [not found]         ` <20140130220708.GP9951@redhat.com>
     [not found]           ` <CAGXu5jKp0j71ucE7uOWRa+gQM1Wzp=_KdByJK4XnACTwiCW4ow@mail.gmail.com>
     [not found]             ` <20140207144914.GA5949@redhat.com>
     [not found]               ` <52F503FD.8080607@linux.intel.com>
2014-02-07 16:24                 ` [GIT PULL] x86/kaslr for v3.14 Vivek Goyal
2014-02-07 23:16                   ` Dave Young
2014-02-07 23:20                     ` H. Peter Anvin [this message]
2014-02-07 23:28                       ` Dave Young
     [not found]               ` <52F52EDA.4080007@linux.intel.com>
2014-02-07 19:44                 ` Kees Cook

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=52F56A40.60707@zytor.com \
    --to=hpa@zytor.com \
    --cc=dinggnu@gmail.com \
    --cc=dyoung@redhat.com \
    --cc=hpa@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md@google.com \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=minipli@googlemail.com \
    --cc=richard.weinberger@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vgoyal@redhat.com \
    --cc=yinghai@kernel.org \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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