From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>, xen-devel@lists.xensource.com
Cc: "Cihula, Joseph" <joseph.cihula@intel.com>
Subject: RE: Xenheap disappearance: (was: xen_phys_start for 32b)
Date: Thu, 8 Jan 2009 17:53:36 +0000 (GMT) [thread overview]
Message-ID: <e2e04b62-ea48-4b14-acb8-67558f08bf23@default> (raw)
In-Reply-To: <C58B7211.20DBD%keir.fraser@eu.citrix.com>
> >> Xenheap will disappear entirely on x86/64 in future. So long
> >> term is that
> >> i386 and x86/64 are actually to diverge significantly in this area.
> >
> > What's the ETA on this? I've got a big patch in preparation built
> > on 3.3. that does gymnastics to get around xenheap limitations
> > and have been holding off updating it to unstable, hoping for
> > this xenheap change (to avoid re-re-duplicating the wheel).
>
> How difficult has it been to work around? Is it just pointing
> xmalloc() at
> the domheap instead of xenheap?
Not difficult. I just do a lot of dynamic memory allocation in
my patch and those kinds of problems can be difficult to track
down, so I was hoping to avoid changing the interface twice.
I previously posted the patch I am currently using here:
http://lists.xensource.com/archives/html/xen-devel/2008-08/msg01142.html
However, after thinking on this a bit, I'm thinking I may just
change all my code to just use domheap allocation and restrict
usage to just 64-bit hypervisors. So unless you plan to rewrite
the domheap interface when xenheap-in-64-bit goes away (or unless
I'm told that 32-bit hypervisor support is a must), I guess I can
remove my dependency on xenheap-in-64-bit going away.
Dan
next prev parent reply other threads:[~2009-01-08 17:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 6:36 xen_phys_start for 32b Cihula, Joseph
2009-01-06 8:42 ` Keir Fraser
2009-01-06 18:29 ` Cihula, Joseph
2009-01-06 22:12 ` Keir Fraser
2009-01-06 22:19 ` Cihula, Joseph
2009-01-07 8:54 ` Keir Fraser
2009-01-07 15:13 ` Cihula, Joseph
2009-01-07 15:40 ` Keir Fraser
2009-01-07 21:37 ` Cihula, Joseph
2009-01-07 23:27 ` Keir Fraser
2009-01-08 0:17 ` Xenheap disappearance: (was: xen_phys_start for 32b) Dan Magenheimer
2009-01-08 9:04 ` Keir Fraser
2009-01-08 17:53 ` Dan Magenheimer [this message]
2009-01-14 22:45 ` Dan Magenheimer
2009-01-15 0:27 ` Dan Magenheimer
2009-01-15 1:48 ` Dan Magenheimer
2009-01-15 8:38 ` Keir Fraser
2009-01-15 8:41 ` Keir Fraser
2009-01-15 18:15 ` Dan Magenheimer
2009-01-15 18:51 ` Keir Fraser
2009-01-16 8:11 ` Re: Xenheap disappearance: (was: xen_phys_start for32b) Jan Beulich
2009-01-16 23:16 ` Dan Magenheimer
2009-01-19 8:22 ` Re: Xenheap disappearance: (was: xen_phys_startfor32b) Jan Beulich
2009-01-19 20:04 ` Dan Magenheimer
2009-01-20 9:11 ` Re: Xenheap disappearance: (was:xen_phys_startfor32b) Jan Beulich
2009-01-20 9:16 ` Keir Fraser
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=e2e04b62-ea48-4b14-acb8-67558f08bf23@default \
--to=dan.magenheimer@oracle.com \
--cc=joseph.cihula@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.