From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, 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>, Tim Deegan <tim@xen.org>,
Jun Nakajima <jun.nakajima@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v3] x86/p2m: use large pages for MMIO mappings
Date: Mon, 18 Jan 2016 17:00:24 +0000 [thread overview]
Message-ID: <1453136424.6020.200.camel@citrix.com> (raw)
In-Reply-To: <569D263702000078000C82AA@prv-mh.provo.novell.com>
On Mon, 2016-01-18 at 09:51 -0700, Jan Beulich wrote:
> > > > On 18.01.16 at 17:32, <ian.campbell@citrix.com> wrote:
> > I must confess I'm not entirely following what the various proposals
> > are,
>
> What is currently implemented by the patch is that, upon error on
> iteration N the hypervisor would clean up on a best effort basis and
> return the error indicator. In the alternative suggested model it
> wouldn't do any cleanup and return N to indicate how far success
> was seen; only in the event that N=0 would an error code be
> returned.
>
> > but FWIW I have no in-principal problem with the caller (by which I
> > think
> > you mean the tools?)
>
> Yes.
>
> > having to cleanup partial success in order to allow
> > incremental attempts to set things up with smaller and smaller page
> > sizes.
>
> Except that in the new x86 model we're not talking about decreasing
> page size, but just the splitting the hypervisor does in place of true
> preemption. Decreasing page size would actually be harmful to the
> goal of using large pages for the mappings.
Ah, I assumed it was to allow things to progress if no large pages were
actually around. Doing it for preemption purposes sounds ok too I guess.
Ian.
prev parent reply other threads:[~2016-01-18 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 10:04 [PATCH v3] x86/p2m: use large pages for MMIO mappings Jan Beulich
2016-01-15 10:09 ` Ian Campbell
2016-01-15 10:47 ` Jan Beulich
2016-01-15 13:57 ` Ian Campbell
2016-01-15 14:39 ` Jan Beulich
2016-01-15 14:55 ` Ian Campbell
2016-01-18 8:11 ` Jan Beulich
2016-01-18 16:32 ` Ian Campbell
2016-01-18 16:51 ` Jan Beulich
2016-01-18 17:00 ` Ian Campbell [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=1453136424.6020.200.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--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.