From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: "Kurt C. Hackel" <kurt.hackel@oracle.com>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Re: dom0 boot failure with 256G
Date: Fri, 06 Jun 2008 17:33:19 -0700 [thread overview]
Message-ID: <4849D74F.6000309@oracle.com> (raw)
In-Reply-To: <4848FDED.76E4.0078.0@novell.com>
Jan Beulich wrote:
>>>> Mukesh Rathor <mukesh.rathor@oracle.com> 06.06.08 04:43 >>>
>> Jan Beulich wrote:
>>>> Trying to figure the hyp out, I notice phys addr is set as:
>>>>
>>>> d->arch.physaddr_bitsize =
>>>> fls((1UL << 32) - HYPERVISOR_COMPAT_VIRT_START(d)) - 1
>>>> + (PAGE_SIZE - 2);
>>>> which is set to 0x1019, totally baffling me. I'd expect it to be 32,
>>>> 36, or 64????????
>>> Of course it should be PAGE_SHIFT in here! c/s 14097 screwed this up
>>> - sorry, my fault.
>>>
>> Yup, that fixed it. Can you pl explain in couple sentences how we are getting
>> at the physaddr_bitsize here?
>
> The whole hypervisor hole is used solely for the (compatibility) m2p map
> when running on a 64-bit hypervisor. Hence the size of that hole, rounded
> down to a power of two, determines the address restriction a domain
> must be assigned. A kernel could theoretically specify being able to
> tolerate a larger hole (though XEN_ELFNOTE_HV_START_LOW), so to
> increase the physical address width it can get memory from.
>
>> I still don't understand why 37 is an OK size for a 32-PAE guest (i thought 36
>> was max).
>
> 36 was the original max, but even on native hardware you can go beyond
> that nowadays. On 64-bit Xen, this was a natural extension even
> independent of confirming hardware support of wider than 36-bit physical
> addresses for 32-bit code.
>
> Of course, we all realize that giving dom0 128G won't do any good, afair
> even native Linux can't reasonably deal with 64G (due to the huge
> memmap needed in lowmem). But allowing an as wide as possible range
> to get memory from for the domain is certainly very desirable (I am
> actually considering ideas on how to overcome even that limit, as in
> practical uses this is really undesirable to have, since there's no way
> to balloon out specific memory [i.e. such below the 37-bit address
> boundary] from other domains).
>
> Jan
Got it. Thanks a lot, appreciate your time.
Mukesh
prev parent reply other threads:[~2008-06-07 0:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 2:07 dom0 boot failure with 256G Mukesh Rathor
2008-06-05 4:00 ` Ian Pratt
2008-06-05 7:24 ` Keir Fraser
2008-06-05 12:16 ` Keir Fraser
2008-06-05 12:54 ` Jeremy Fitzhardinge
2008-06-05 12:58 ` Keir Fraser
2008-06-05 13:15 ` Jan Beulich
2008-06-05 13:17 ` Keir Fraser
2008-06-05 13:31 ` Jeremy Fitzhardinge
2008-06-06 2:48 ` Mukesh Rathor
2008-06-05 18:01 ` mukesh rathor
2008-06-05 7:30 ` Keir Fraser
2008-06-05 7:35 ` [PATCH] " Jan Beulich
2008-06-06 2:43 ` Mukesh Rathor
2008-06-06 7:05 ` Jan Beulich
2008-06-07 0:33 ` Mukesh Rathor [this message]
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=4849D74F.6000309@oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jbeulich@novell.com \
--cc=kurt.hackel@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.