From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xensource.com
Cc: David Vrabel <david.vrabel@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] x86/xen: page fault and context switch performance (v2)
Date: Mon, 9 Jul 2012 11:39:04 +0100 [thread overview]
Message-ID: <1341830348-15529-1-git-send-email-david.vrabel@citrix.com> (raw)
This series improves the performance of Xen PV guests when doing page
faults (32-bit guests only) and context switches.
Can an x86 maintainer ack patch 3 (x86: add desc_equal() to compare
GDT descriptors) so this series can go via Konrad's tree? The other
patches are Xen-specific.
Changes since v1:
- fix (very!) slow boot on x86_64 by avoiding hypercalls when building
the initial page tables. These updates were mostly a) done to
unpinned pages and b) often had invalid MFNs that Xen warns about.
- When building the initial page tables, zero PTEs for pages without
an MFN yet.
- add desc_equal() instead of open coding it.
David
next reply other threads:[~2012-07-09 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 10:39 David Vrabel [this message]
2012-07-09 10:39 ` [PATCH 1/4] xen/mm: do direct hypercall in xen_set_pte() if batching is unavailable David Vrabel
2012-07-09 10:39 ` [PATCH 2/4] xen/mm: zero PTEs for non-present MFNs in the initial page table David Vrabel
2012-07-09 10:39 ` [PATCH 3/4] x86: add desc_equal() to compare GDT descriptors David Vrabel
2012-07-11 19:21 ` Konrad Rzeszutek Wilk
2012-07-17 15:22 ` David Vrabel
2012-07-17 15:57 ` H. Peter Anvin
2012-07-09 10:39 ` [PATCH 4/4] x86/xen: avoid updating TLS descriptors if they haven't changed David Vrabel
2012-07-09 14:38 ` [Xen-devel] [PATCH 0/4] x86/xen: page fault and context switch performance (v2) 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=1341830348-15529-1-git-send-email-david.vrabel@citrix.com \
--to=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--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 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).