All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Jan Beulich <jbeulich@novell.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: Re: Xenheap disappearance: (was: xen_phys_start for32b)
Date: Fri, 16 Jan 2009 15:16:06 -0800 (PST)	[thread overview]
Message-ID: <c626e006-c44b-47ae-a8e5-654f728098d7@default> (raw)
In-Reply-To: <49704F4D.76E4.0078.0@novell.com>

 -----Original Message-----
> From: Jan Beulich [mailto:jbeulich@novell.com]
> Sent: Friday, January 16, 2009 1:12 AM
> >>> Keir Fraser <keir.fraser@eu.citrix.com> 15.01.09 19:51 >>>
> >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. :-)
> 
> I'd hope that too, because the patch as is must not go in, as 
> it would break
> other assumptions afaics: At present, the tools balloon out 
> of Dom0 exactly
> the amount needed for creating pv domains (I think there's 
> some slack for
> hvm ones), so the fact that the domain heap now serves 
> xmalloc requires
> that there always be some extra space available in Xen (also to serve
> dynamic allocations). Additionally I think the minimum even a 
> temporary
> patch like this should do is fall back to allocating from the 
> Xen heap when
> the domain heap is unable the supply the requested amount.

Jan --

I'm not sure what you are getting at.  Are you saying that
creating a domain takes (big)MB from domheap, then later
(little)KB from xenheap, and if we combine domheap and xenheap,
the tools might launch a domain when available memory is
greater than (big)MB but smaller than (big)MB+(small)KB,
and that will result in the tools thinking the domain
can launch but it won't?  I suppose that's possible,
but exceedingly unlikely.  And I think Keir's plan will
have the same problem.  Sounds like a tools bug, not a
reason to avoid modernizing Xen memory management.

Dan

  reply	other threads:[~2009-01-16 23:16 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
2009-01-16  8:11                           ` Re: Xenheap disappearance: (was: xen_phys_start for32b) Jan Beulich
2009-01-16 23:16                             ` Dan Magenheimer [this message]
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=c626e006-c44b-47ae-a8e5-654f728098d7@default \
    --to=dan.magenheimer@oracle.com \
    --cc=jbeulich@novell.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.