From: "Jan Beulich" <JBeulich@suse.com>
To: JulienGrall <julien.grall@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [RFC 0/3] xen/arm: Support XENMEM_exchange
Date: Tue, 22 Dec 2015 09:16:19 -0700 [thread overview]
Message-ID: <5679856302000078000C2571@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1450369919-22989-1-git-send-email-julien.grall@citrix.com>
>>> On 17.12.15 at 17:31, <julien.grall@citrix.com> wrote:
> I've looked at reworking XENMEM_exchange to avoid mfn_to_gmfn. My idea would
> be to allocate a temporary array to store the GFN between the two loops.
> However, the array would be quite large (the max default is 18 on ARM),
> so I don't know if it's acceptable.
This would quite clearly not be acceptable, yet I don't have an
alternative suggestion other then implementing M2P on ARM, which
you have already named as not an option.
Otoh I'm not sure what two loops you talk about - I find exactly
one use of mfn_to_gmfn() in memory_exchange(), and latching
the GFN earlier would be wrong (as it might change in parallel to
your processing).
Jan
prev parent reply other threads:[~2015-12-22 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 16:31 [RFC 0/3] xen/arm: Support XENMEM_exchange Julien Grall
2015-12-17 16:31 ` [RFC 1/3] xen/common: memory: Introduce check_range_domain_direct_mapped Julien Grall
2015-12-17 16:31 ` [RFC 2/3] xen/common: memory: Add support for direct mapped domain in XEMEM_exchange Julien Grall
2015-12-22 16:18 ` Jan Beulich
2015-12-17 16:31 ` [RFC 3/3] xen/common: memory: Move steal_page in common code Julien Grall
2015-12-22 16:20 ` Jan Beulich
2015-12-22 16:16 ` Jan Beulich [this message]
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=5679856302000078000C2571@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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.