From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
xen-devel@lists.xensource.com
Subject: Re: Re: Xenheap disappearance: (was: xen_phys_start for 32b)
Date: Thu, 15 Jan 2009 18:51:10 +0000 [thread overview]
Message-ID: <C595361E.2103F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <96d6ebb0-6ee2-494b-8a53-da25eba119d2@default>
On 15/01/2009 18:15, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>> Xmalloc/xfree can use alloc_domheap_pages always on x86/64.
>> A temporary
>> ifdef inside xmalloc is better than an extra xmalloc interface.
>
> OK, I see. So what you want is xmalloc to be the only interface.
> And "temporary" means until Xen no longer supports 32-bit at all?
I mean until I get rid of restricted xenheap for x86/64 (and you've caused
me to go look at that patch again now, so hopefully I can get it debugged
and in next week).
> Will you take this patch then? I think this patch meets your
> objectives and is greatly simplified.
This is indeed the patch I had in mind.
>> Also, this will be a small patch you can carry in your own
>> patchset for now.
>
> I'm just trying to contribute to your stated objective:
>
>> Xenheap will disappear entirely on x86/64 in future.
>
> and trying to get the syntax/semantics pinned down. Is
> this not what you intended to implement for 3.4? Or did
> you have something entirely different in mind?
I think the patch you attached will work just fine for you for now. If your
stuff goes in before getting rid of xenheap restrictions on x86/64, then I
would take this patch at that time. But I think that's unlikely. Well, I
hope it is, unless I stall on my xenheap patch again. :-)
-- Keir
next prev parent reply other threads:[~2009-01-15 18:51 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
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 [this message]
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=C595361E.2103F%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=dan.magenheimer@oracle.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.