xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, julien.grall@linaro.org, tim@xen.org,
	Ian Campbell <ian.campbell@citrix.com>,
	stefano.stabellini@eu.citrix.com
Subject: [PATCH v3 8/8] tools: arm: increase size of region set aside for guest grant table
Date: Mon, 28 Apr 2014 14:02:12 +0100	[thread overview]
Message-ID: <1398690132-5651-8-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1398690109.29700.82.camel@kazak.uk.xensource.com>

The current size is sufficient for the default maximum grant table size
(32-frames), but increase the reserved region to 16M/4096 pages to allow for
the use of the gnttab_max_nr_frames command line option.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Julien Grall <julien.grall@linaro.org>
---
v2: New patch
---
 xen/include/public/arch-arm.h |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/xen/include/public/arch-arm.h b/xen/include/public/arch-arm.h
index 749b7b3..9f923dc 100644
--- a/xen/include/public/arch-arm.h
+++ b/xen/include/public/arch-arm.h
@@ -369,8 +369,11 @@ typedef uint64_t xen_callback_t;
 #define GUEST_GICC_BASE   0x03002000ULL
 #define GUEST_GICC_SIZE   0x00000100ULL
 
+/* 16MB == 4096 pages reserved for guest to use as a region to map its
+ * grant table in.
+ */
 #define GUEST_GNTTAB_BASE 0x38000000ULL
-#define GUEST_GNTTAB_SIZE 0x00020000ULL
+#define GUEST_GNTTAB_SIZE 0x01000000ULL
 
 #define GUEST_MAGIC_BASE  0x39000000ULL
 #define GUEST_MAGIC_SIZE  0x01000000ULL
-- 
1.7.10.4

  parent reply	other threads:[~2014-04-28 13:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 13:01 [PATCH v3 0/8] xen: arm: support up to (almost) 1TB of guest RAM Ian Campbell
2014-04-28 13:02 ` [PATCH v3 1/8] tools: libxl: use uint64_t not unsigned long long for addresses Ian Campbell
2014-05-02 14:34   ` Ian Jackson
2014-04-28 13:02 ` [PATCH v3 2/8] tools: arm: report an error if the guest RAM is too large Ian Campbell
2014-05-02 14:35   ` Ian Jackson
2014-04-28 13:02 ` [PATCH v3 3/8] tools: arm: move magic pfns out of guest RAM region Ian Campbell
2014-05-02 14:36   ` Ian Jackson
2014-04-28 13:02 ` [PATCH v3 4/8] tools: arm: rearrange guest physical address space to increase max RAM Ian Campbell
2014-05-02 14:36   ` Ian Jackson
2014-04-28 13:02 ` [PATCH v3 5/8] tools: arm: prepare for multiple banks of guest RAM Ian Campbell
2014-05-02 14:37   ` Ian Jackson
2014-05-02 15:32     ` Ian Campbell
2014-04-28 13:02 ` [PATCH v3 6/8] tools: arm: refactor code to setup guest p2m and fill it with RAM Ian Campbell
2014-05-02 14:42   ` Ian Jackson
2014-05-02 15:34     ` Ian Campbell
2014-05-02 15:46       ` Ian Jackson
2014-04-28 13:02 ` [PATCH v3 7/8] tools: arm: support up to (almost) 1TB of guest RAM Ian Campbell
2014-05-02 14:50   ` Ian Jackson
2014-05-02 15:35     ` Ian Campbell
2014-04-28 13:02 ` Ian Campbell [this message]
2014-05-02 14:57   ` [PATCH v3 8/8] tools: arm: increase size of region set aside for guest grant table Ian Jackson

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=1398690132-5651-8-git-send-email-ian.campbell@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).