From: Julien Grall <julien.grall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Tiejun Chen <tiejun.chen@intel.com>,
Malcolm Crossley <malcolm.crossley@citrix.com>,
Keir Fraser <keir@xen.org>
Subject: Re: [PATCH 3/4 RFC] x86/p2m: use large pages for MMIO mappings
Date: Wed, 16 Sep 2015 11:02:15 +0100 [thread overview]
Message-ID: <55F93E27.7080106@citrix.com> (raw)
In-Reply-To: <55F7E63702000078000A2BD6@prv-mh.provo.novell.com>
Hi Jan,
On 15/09/2015 08:34, Jan Beulich wrote:
> When mapping large BARs (e.g. the frame buffer of a graphics card) the
> overhead or establishing such mappings using onle 4k pages has,
> particularly after the XSA-125 fix, become unacceptable. Alter the
> XEN_DOMCTL_memory_mapping semantics once again, so that there's no
> longer a fixed amount of guest frames that represents the upper limit
> of what a single invocation can map. Instead bound execution time by
> limiting the number of iterations (regardless of page size).
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> RFC reasons:
> - ARM side unimplemented (and hence libxc for now made cope with both
> models), the main issue (besides my inability to test any change
> there) being the many internal uses of map_mmio_regions())
I will give a look to this bits.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-09-16 10:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55F70C9A02000078000A2A58@prv-mh.provo.novell.com>
2015-09-15 7:13 ` [PATCH 0/4] x86/p2m: use large pages for MMIO mappings Jan Beulich
2015-09-15 7:30 ` [PATCH 1/4] x86/EPT: always return proper order value from ept_get_entry() Jan Beulich
2015-09-16 7:15 ` Tian, Kevin
2015-09-17 16:13 ` Andrew Cooper
2015-09-15 7:31 ` [PATCH 2/4] x86/NPT: always return proper order value from p2m_pt_get_entry() Jan Beulich
2015-09-15 7:35 ` Jan Beulich
2015-09-15 7:32 ` Jan Beulich
2015-09-17 16:14 ` Andrew Cooper
2015-09-15 7:34 ` [PATCH 3/4 RFC] x86/p2m: use large pages for MMIO mappings Jan Beulich
2015-09-16 10:02 ` Julien Grall [this message]
2015-09-17 16:37 ` Andrew Cooper
2015-09-17 17:59 ` Jan Beulich
2015-09-22 8:32 ` Jan Beulich
2015-09-29 11:33 ` Julien Grall
2015-09-29 11:44 ` Jan Beulich
2015-09-29 12:16 ` Julien Grall
2015-09-29 12:46 ` Jan Beulich
2015-09-29 12:52 ` Julien Grall
2015-09-29 13:00 ` Jan Beulich
2015-09-29 13:06 ` Julien Grall
2015-09-29 13:27 ` Jan Beulich
2015-09-30 10:15 ` Julien Grall
2015-09-15 7:37 ` [PATCH 4/4] x86/PoD: shorten certain operations on higher order ranges Jan Beulich
2015-09-23 17:10 ` George Dunlap
2015-09-23 17:16 ` George Dunlap
2015-09-24 8:42 ` 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=55F93E27.7080106@citrix.com \
--to=julien.grall@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=malcolm.crossley@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tiejun.chen@intel.com \
--cc=wei.liu2@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.