From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen: allocate page for shared info page from low memory
Date: Wed, 14 Jun 2017 12:58:10 -0400 [thread overview]
Message-ID: <a6d0bfa0-5ddb-25bd-34c4-24b8e041f006@oracle.com> (raw)
In-Reply-To: <20170612115356.8312-1-jgross@suse.com>
On 06/12/2017 07:53 AM, Juergen Gross wrote:
> In a HVM guest the kernel allocates the page for mapping the shared
> info structure via extend_brk() today. This will lead to a drop of
> performance as the underlying EPT entry will have to be split up into
> 4kB entries as the single shared info page is located in hypervisor
> memory.
>
> The issue has been detected by using the libmicro munmap test:
> unmapping 8kB of memory was faster by nearly a factor of two when no
> pv interfaces were active in the HVM guest.
>
> So instead of taking a page from memory which might be mapped via
> large EPT entries use a page which is already mapped via a 4kB EPT
> entry: we can take a page from the first 1MB of memory as the video
> memory at 640kB disallows using larger EPT entries.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> arch/x86/xen/enlighten_hvm.c | 31 ++++++++++++++++++++++++-------
> arch/x86/xen/enlighten_pv.c | 2 --
> 2 files changed, 24 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/xen/enlighten_hvm.c b/arch/x86/xen/enlighten_hvm.c
> index a6d014f47e52..c19477b6e43a 100644
> --- a/arch/x86/xen/enlighten_hvm.c
> +++ b/arch/x86/xen/enlighten_hvm.c
> @@ -1,5 +1,6 @@
> #include <linux/cpu.h>
> #include <linux/kexec.h>
> +#include <linux/memblock.h>
>
> #include <xen/features.h>
> #include <xen/events.h>
> @@ -10,9 +11,11 @@
> #include <asm/reboot.h>
> #include <asm/setup.h>
> #include <asm/hypervisor.h>
> +#include <asm/e820/api.h>
>
> #include <asm/xen/cpuid.h>
> #include <asm/xen/hypervisor.h>
> +#include <asm/xen/page.h>
>
> #include "xen-ops.h"
> #include "mmu.h"
> @@ -22,20 +25,34 @@ void __ref xen_hvm_init_shared_info(void)
> {
> int cpu;
> struct xen_add_to_physmap xatp;
> - static struct shared_info *shared_info_page;
> + u64 pa;
> +
> + if (HYPERVISOR_shared_info == &xen_dummy_shared_info) {
> + /*
> + * Search for a free page starting at 4kB physical address.
> + * Low memory is preferred to avoid an EPT large page split up
> + * by the mapping.
> + * Starting below X86_RESERVE_LOW (usually 64kB) is fine as
> + * the BIOS used for HVM guests is well behaved and won't
> + * clobber memory other than the first 4kB.
> + */
> + for (pa = PAGE_SIZE;
> + !e820__mapped_all(pa, pa + PAGE_SIZE, E820_TYPE_RAM) ||
> + memblock_is_reserved(pa);
> + pa += PAGE_SIZE)
> + ;
Is it possible to never find a page here?
-boris
> +
> + memblock_reserve(pa, PAGE_SIZE);
> + HYPERVISOR_shared_info = __va(pa);
> + }
>
> - if (!shared_info_page)
> - shared_info_page = (struct shared_info *)
> - extend_brk(PAGE_SIZE, PAGE_SIZE);
> xatp.domid = DOMID_SELF;
> xatp.idx = 0;
> xatp.space = XENMAPSPACE_shared_info;
> - xatp.gpfn = __pa(shared_info_page) >> PAGE_SHIFT;
> + xatp.gpfn = virt_to_pfn(HYPERVISOR_shared_info);
> if (HYPERVISOR_memory_op(XENMEM_add_to_physmap, &xatp))
> BUG();
>
> - HYPERVISOR_shared_info = (struct shared_info *)shared_info_page;
> -
> /* xen_vcpu is a pointer to the vcpu_info struct in the shared_info
> * page, we use it in the event channel upcall and in some pvclock
> * related functions. We don't need the vcpu_info placement
> diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
> index f33eef4ebd12..a9a67ecf2c07 100644
> --- a/arch/x86/xen/enlighten_pv.c
> +++ b/arch/x86/xen/enlighten_pv.c
> @@ -89,8 +89,6 @@
>
> void *xen_initial_gdt;
>
> -RESERVE_BRK(shared_info_page_brk, PAGE_SIZE);
> -
> static int xen_cpu_up_prepare_pv(unsigned int cpu);
> static int xen_cpu_dead_pv(unsigned int cpu);
>
next prev parent reply other threads:[~2017-06-14 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 11:53 Juergen Gross
2017-06-14 16:58 ` Boris Ostrovsky [this message]
2017-06-14 17:11 ` Juergen Gross
2017-06-14 17:30 ` Boris Ostrovsky
2017-07-23 20:25 ` Boris Ostrovsky
2017-07-25 3:58 ` Boris Ostrovsky
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=a6d0bfa0-5ddb-25bd-34c4-24b8e041f006@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®