All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: James Harper <james.harper@bendigoit.com.au>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: How to determine memory size in HVM
Date: Wed, 10 Jun 2009 09:24:11 +0100	[thread overview]
Message-ID: <C6552C3B.7C4E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D016DD68C@trantor>

On 09/06/2009 08:42, "James Harper" <james.harper@bendigoit.com.au> wrote:

> memory/target = 786432KB
> XENMEM_current_reservation = 198623 pages
> 
> 198623 << PAGE_SHIFT = 794492KB
> 794492KB - 786432KB = 8060KB
> 
> So I have 8060KB unaccounted for... I guess that's probably the
> framebuffer. According to Device Manager in Windows, the CL5446 device
> uses 64KB of memory at 0xA0000, 32MB at 0xF0000000, and 4KB at
> 0xF3000000. That's more than the extra 8MB, but it would make sense that
> the 32MB wouldn't all be mapped in if it wasn't required.

Yes, that's the framebuffer. It is variable size, in principle, though. I'm
not sure you can do better than read XENMEM_current_reservation and
memory/target at driver startup time, and keep the delta between them
constant.

 -- Keir

  reply	other threads:[~2009-06-10  8:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 14:12 How to determine memory size in HVM James Harper
2009-06-08 14:32 ` Keir Fraser
2009-06-09  1:59   ` James Harper
2009-06-09  5:38     ` Keir Fraser
2009-06-10 10:47       ` George Dunlap
2009-06-09  7:42   ` James Harper
2009-06-10  8:24     ` Keir Fraser [this message]
2009-06-10  9:39       ` James Harper
2009-06-10 13:07         ` Keir Fraser
2009-06-10 13:28           ` James Harper
2009-06-10 13:54             ` 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=C6552C3B.7C4E%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --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.