[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070228083055.GA8866@elte.hu>
Date: Wed, 28 Feb 2007 09:30:55 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Andi Kleen <ak@....de>, Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org,
xen-devel@...ts.xensource.com, Chris Wright <chrisw@...s-sol.org>,
Zachary Amsden <zach@...are.com>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [patch 06/26] Xen-paravirt_ops: paravirt_ops: allocate a fixmap slot
* Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> > Yes. vmalloc would have the annoying side-effect of actually
> > allocating some pages which would be shadowed by the remapping, but
> > I guess get_vm_area would do the job. I'll give it a go.
>
> Hm, this is a bit awkward. We need to map the shared info page fairly
> early - say, around paging_init - but we're still on the bootmem
> allocator at that point, so get_vm_area isn't usable yet. Using a
> fixmap keeps things simple. It seems to me that having a single
> fixmap available is useful for this kind of simple/early mapping, and
> if someone needs to map something larger, then they can put it off
> until get_vm_area() is available...
fair enough. Please rename it to FIX_PARAVIRT_BOOTUP - you can still
rely on it being available later on too, but we'd like to give everyone
the right fundamental idea about this: it's meant to be a limited,
inflexible interface for bootstrap only.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists