All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Julien Grall <julien.grall@citrix.com>, Tim Deegan <tim@xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: [PATCH v2 0/8] xen: arm: Use super pages in p2m
Date: Wed, 11 Jun 2014 17:37:20 +0100	[thread overview]
Message-ID: <1402504640.16332.50.camel@kazak.uk.xensource.com> (raw)

The following series adds support for superpage mappings (1G and 2M) in
the p2m for dom0 and domU.

At the moment it is not possible to allocate 1G regions to guests,
because this is gated on multipage_allocation_permitted() which
currently (incorrectly) returns false for dom0 on ARM. This is fixed by
Arianna's "arch/arm: domain build: let dom0 access I/O memory of mapped
devices" (which initialises iomem_caps for dom0).

On a 32-bit platform this causes the overhead of kernbench vs. native to
drop from 8-9% to 1.5-3% (it's basically the same for both dom0 and
domU).

I couldn't get my 64-bit platform to boot natively for some reason but
in absolute terms kernbench improved by ~5% (domU) to ~15% (dom0).

Changes in v2:
 - Juliens review comments
 - Added "xen: arm: allocate more than one bank for 1:1 domain 0 if 
   needed" (not strictly related...)

Ian.

             reply	other threads:[~2014-06-11 16:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 16:37 Ian Campbell [this message]
2014-06-11 16:39 ` [PATCH v2 1/8] xen: arm: dump vcpu gic info in arch_dump_vcpu_info Ian Campbell
2014-06-11 16:39 ` [PATCH v2 2/8] tools/libxc: pull min/max_t into xc_private.h Ian Campbell
2014-06-11 21:14   ` Julien Grall
2014-06-11 16:39 ` [PATCH v2 3/8] tools: arm: allocate large pages to guests Ian Campbell
2014-06-11 21:26   ` Julien Grall
2014-06-12  7:19     ` Ian Campbell
2014-06-12  8:47       ` Julien Grall
2014-06-11 16:40 ` [PATCH v2 4/8] xen: arm: only put_page for p2m operations which require it Ian Campbell
2014-06-11 21:31   ` Julien Grall
2014-06-12  7:27     ` Ian Campbell
2014-06-11 16:40 ` [PATCH v2 5/8] xen: arm: handle superpage mappings in p2m_lookup Ian Campbell
2014-06-11 16:40 ` [PATCH v2 6/8] xen: arm: add some helpers for assessing p2m pte Ian Campbell
2014-06-11 21:39   ` Julien Grall
2014-06-12  7:27     ` Ian Campbell
2014-06-11 16:40 ` [PATCH v2 7/8] xen: arm: use superpages in p2m when pages are suitably aligned Ian Campbell
2014-06-11 22:19   ` Julien Grall
2014-06-12  7:30     ` Ian Campbell
2014-06-12  9:00       ` Julien Grall
2014-06-13 14:08         ` Ian Campbell
2014-06-13 17:45           ` Julien Grall
2014-06-16  8:26             ` Jan Beulich
2014-06-16  9:53             ` Ian Campbell
2014-06-12 13:57   ` Stefano Stabellini
2014-06-13 14:15     ` Ian Campbell
2014-06-11 16:40 ` [PATCH v2 8/8] xen: arm: allocate more than one bank for 1:1 domain 0 if needed Ian Campbell
2014-06-11 22:47   ` Julien Grall
2014-06-12  7:31     ` Ian Campbell
2014-06-17 17:58   ` Julien Grall
2014-06-18  8:27     ` Ian Campbell
2014-06-18  9:10       ` Julien Grall
2014-06-18  9:36         ` Ian Campbell
2014-06-12  7:20 ` [PATCH v2 0/8] xen: arm: Use super pages in p2m Ian Campbell

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=1402504640.16332.50.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=stefano.stabellini@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 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.