From: "Xia, Hongyan" <hongyxia@amazon.com>
To: "jbeulich@suse.com" <jbeulich@suse.com>,
"Grall, Julien" <jgrall@amazon.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"wl@xen.org" <wl@xen.org>,
"roger.pau@citrix.com" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v2 1/2] x86/mm: factor out the code for shattering an l3 PTE
Date: Wed, 11 Dec 2019 11:28:15 +0000 [thread overview]
Message-ID: <eeb762add75c87db90a3c93a35a7f2149e81c6f7.camel@amazon.com> (raw)
In-Reply-To: <d365aecc-0611-dc17-d63c-850e0a3363da@amazon.com>
On Wed, 2019-12-11 at 11:10 +0000, Julien Grall wrote:
> Hi Hongyan,
> ...
>
> While this involves more instructions, how often do we expect the
> code
> to be called?
>
> Cheers,
>
I don't expect this to be called very often in the current Xen.
Although with direct map removal, a lot of the memory allocations
(mostly xenheap allocations) will be mapped and unmapped on-demand and
there is a much higher change of merging/shattering.
However, the series moved all PTEs from xenheap to domheap, and we
might see other things moved to domheap in the future, so we might not
have many things left on xenheap anyway.
Hongyan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-11 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 11:48 [Xen-devel] [PATCH v2 0/2] Refactor super page shattering Hongyan Xia
2019-12-09 11:48 ` [Xen-devel] [PATCH v2 1/2] x86/mm: factor out the code for shattering an l3 PTE Hongyan Xia
2019-12-10 15:20 ` Jan Beulich
2019-12-11 10:28 ` Xia, Hongyan
2019-12-11 11:10 ` Julien Grall
2019-12-11 11:28 ` Xia, Hongyan [this message]
2019-12-11 11:47 ` Julien Grall
2019-12-11 11:02 ` Xia, Hongyan
2019-12-09 11:48 ` [Xen-devel] [PATCH v2 2/2] x86/mm: factor out the code for shattering an l2 PTE Hongyan Xia
2019-12-10 15:27 ` Jan Beulich
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=eeb762add75c87db90a3c93a35a7f2149e81c6f7.camel@amazon.com \
--to=hongyxia@amazon.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.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 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.