From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Juergen Gross <jgross@suse.com>
Cc: David Vrabel <david.vrabel@citrix.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
boris.ostrovsky@oracle.com, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, andrew.cooper3@citrix.com
Subject: Re: [PATCH V4 00/10] xen: Switch to virtual mapped linear p2m list
Date: Tue, 2 Dec 2014 13:54:46 -0500 [thread overview]
Message-ID: <20141202185446.GD32622@laptop.dumpdata.com> (raw)
In-Reply-To: <547C64F3.9050005@suse.com>
On Mon, Dec 01, 2014 at 01:54:11PM +0100, Juergen Gross wrote:
> On 12/01/2014 12:31 PM, David Vrabel wrote:
> >On 28/11/14 10:53, Juergen Gross wrote:
> >>Paravirtualized kernels running on Xen use a three level tree for
> >>translation of guest specific physical addresses to machine global
> >>addresses. This p2m tree is used for construction of page table
> >>entries, so the p2m tree walk is performance critical.
> >>
> >>By using a linear virtual mapped p2m list accesses to p2m elements
> >>can be sped up while even simplifying code. To achieve this goal
> >>some p2m related initializations have to be performed later in the
> >>boot process, as the final p2m list can be set up only after basic
> >>memory management functions are available.
> >
> >What are the results of the testing I asked for?
>
> You asked for those replying to the patch introducing the linear
> mapping. So I added the description of the tested scenarios in the
> patch description of that patch.
>
> >If Konrad or Boris are happy with this series I think it can go into 3.19.
>
> Great, thanks!
I am happy.
>
>
> Juergen
>
next prev parent reply other threads:[~2014-12-02 18:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 10:53 [PATCH V4 00/10] xen: Switch to virtual mapped linear p2m list Juergen Gross
2014-11-28 10:53 ` [PATCH V4 1/9] xen: fix some style issues in p2m.c Juergen Gross
2014-11-28 10:53 ` [PATCH V4 2/9] xen: Make functions static Juergen Gross
2014-11-28 10:53 ` [PATCH V4 03/10] xen: use common page allocation function in p2m.c Juergen Gross
2014-11-28 10:53 ` [PATCH V4 04/10] xen: Delay remapping memory of pv-domain Juergen Gross
2014-11-28 10:53 ` [PATCH V4 05/10] xen: Delay m2p_override initialization Juergen Gross
2014-11-28 10:53 ` [PATCH V4 06/10] xen: Delay invalidating extra memory Juergen Gross
2014-11-28 10:53 ` [PATCH V4 07/10] x86: Introduce function to get pmd entry pointer Juergen Gross
2014-11-28 10:53 ` [PATCH V4 08/10] xen: Hide get_phys_to_machine() to be able to tune common path Juergen Gross
2014-11-28 10:53 ` [PATCH V4 09/10] xen: switch to linear virtual mapped sparse p2m list Juergen Gross
2014-11-28 10:53 ` [PATCH V4 10/10] xen: Speed up set_phys_to_machine() by using read-only mappings Juergen Gross
2014-12-01 11:31 ` [PATCH V4 00/10] xen: Switch to virtual mapped linear p2m list David Vrabel
2014-12-01 12:54 ` Juergen Gross
2014-12-02 18:54 ` Konrad Rzeszutek Wilk [this message]
2014-12-04 15:44 ` [Xen-devel] " David Vrabel
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=20141202185446.GD32622@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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