All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@elte.hu>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] x86: add brk allocation for very, very early allocations
Date: Fri, 27 Feb 2009 10:43:43 -0800	[thread overview]
Message-ID: <49A8345F.8020800@zytor.com> (raw)
In-Reply-To: <49A829CE.9020509@goop.org>

Jeremy Fitzhardinge wrote:
> I'd like to add a mechanism like this so I can dynamically allocate some
> Xen-related structures, rather than statically allocating them in the bss,
> both so that Xen has less overhead when it isn't being used, and so I can
> scale better to things like memory size.
> 
> I think this is more widely useful; it would supplant dmi_alloc_data[], for
> example, and I'm sure there's other cases.
> 
> This is fundimentally the same as head_32.S's extension of the bss to build
> the initial kernel mapping, but 64-bit doesn't currently do anything
> analogous
> to this.
> 
> Unfortunately when I use this code as-is I'm getting crashes when the slab
> allocator starts up.  I think this is all correct, but I'm wondering if
> there's something I'm overlooking which is broken in principle.

First of all, I like the concept.  As far as getting crashes, I suspect
what you're finding is some use of this type of extended memory space
that just isn't documented.  I would try this in a simulator, setting a
watchpoint on _end to see if you get any hits before the slab allocator
starts.

	-hpa
-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2009-02-27 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 17:58 [PATCH RFC] x86: add brk allocation for very, very early allocations Jeremy Fitzhardinge
2009-02-27 18:43 ` H. Peter Anvin [this message]
2009-02-27 19:17 ` H. Peter Anvin
2009-02-27 19:26   ` Jeremy Fitzhardinge
2009-02-27 20:26 ` Yinghai Lu
2009-02-27 21:02   ` Jeremy Fitzhardinge
2009-02-27 21:05   ` H. Peter Anvin
2009-02-27 21:19     ` Jeremy Fitzhardinge
2009-02-27 21:28       ` H. Peter Anvin
2009-02-27 21:41         ` Jeremy Fitzhardinge

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=49A8345F.8020800@zytor.com \
    --to=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.