From: Keir Fraser <keir@xensource.com>
To: Jambunathan K <jambunathan@netxen.com>
Cc: xen-devel@lists.xensource.com, sanjeev@netxen.com
Subject: Re: xen_create_contiguous_region - Regarding
Date: Tue, 10 Apr 2007 10:17:07 +0100 [thread overview]
Message-ID: <C24114A3.D036%keir@xensource.com> (raw)
In-Reply-To: <461B2DF5.8050902@netxen.com>
On 10/4/07 07:25, "Jambunathan K" <jambunathan@netxen.com> wrote:
> xen_create_contiguous_region (as in Xen-3.0.4) can be instructed to make
> 2 kinds of allocations - from either MEMZONE_DOM or MEMZONE_DMADOM. Two
> zones are delineated by max_dma_mfn as dictated by dma_size.
>
> A "MEMF_dma" request to __alloc_domheap_pages is assured to be satisfied
> from the MEMZONE_DMADOM.
>
> The role of address_bits apparently stops at discreetly choosing between
> one of the above 2 zones.
This is an implementation detail inside the hypervisor. The fact that Xen
3.0.4 actually doesn't track each separate bit-width of memory separately
should not affect your use of the guest memory-allocation interfaces. The
fact that when you try to allocate 35-bit memory you actually are limited to
31-bit memory is simply a limitation you'll have to work with for 3.0.4. Xen
3.0.5 will not have this limitation.
-- Keir
prev parent reply other threads:[~2007-04-10 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 10:46 xen_create_contiguous_region - Regarding Jambunathan K
2007-04-06 11:07 ` Keir Fraser
2007-04-06 12:54 ` Jambunathan K
2007-04-09 13:17 ` Jambunathan K
2007-04-09 13:24 ` Keir Fraser
2007-04-10 6:25 ` Jambunathan K
2007-04-10 9:17 ` Keir Fraser [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=C24114A3.D036%keir@xensource.com \
--to=keir@xensource.com \
--cc=jambunathan@netxen.com \
--cc=sanjeev@netxen.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.