From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: RE: Xenheap disappearance: (was: xen_phys_start for 32b)
Date: Wed, 14 Jan 2009 22:45:15 +0000 (GMT) [thread overview]
Message-ID: <414df624-72b4-4367-aa38-979286b39a88@default> (raw)
In-Reply-To: <C58B7211.20DBD%keir.fraser@eu.citrix.com>
> How difficult has it been to work around? Is it just pointing
> xmalloc() at
> the domheap instead of xenheap?
>
> -- Keir
Thinking about this a bit more, unless you plan to stop
supporting 32-bit Xen anytime soon, the semantic differences
probably warrant adding a second interface, let's call
it admalloc() (ad == anonymous domain), that should only be
used in 64-bit-only code where it can be guaranteed that
usage of pointers to the alloc'ed memory need not be bracketed
with (ugly) map/unmap_domain_page() calls.
So I'd suggest adding _admalloc() and adfree() to xmalloc_tlsf.c
and when ifdef x86_64, _xmalloc and xfree simply get redefined
to _admalloc/adfree in xmalloc_tlsf.h.
If this sounds sensible, I will spin a patch as I'm the one keen
to get this settled.
Thanks,
Dan
next prev parent reply other threads:[~2009-01-14 22:45 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
2009-01-14 22:45 ` Dan Magenheimer [this message]
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=414df624-72b4-4367-aa38-979286b39a88@default \
--to=dan.magenheimer@oracle.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.