All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, 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>, TimDeegan <tim@xen.org>,
	Jun Nakajima <jun.nakajima@intel.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v7] x86/p2m: use large pages for MMIO mappings
Date: Wed, 10 Feb 2016 10:19:03 +0000	[thread overview]
Message-ID: <56BB0E97.6060804@citrix.com> (raw)
In-Reply-To: <1455098769.19857.137.camel@citrix.com>

On 10/02/16 10:06, Ian Campbell wrote:
> On Tue, 2016-02-09 at 05:35 -0700, Jan Beulich wrote:
>>> On 09.02.16 at 13:17, <george.dunlap@citrix.com> wrote:
>>> I don't think sometimes returning the number of things you did and
>>> sometimes returning zero makes any sense.  My suggestion would be
>>> either
>>> make "nr_mfns" bidirectional (as similar fields are in the other
>>> domctls) and return 0 on either full or partial success, or just return
>>> the number of mfns actually mapped either on full or partial success.
>>
>> As said - I can see your point, and I've been considering the
>> alternatives and had to decide for one. Since I've already got
>> Ian's approval for the currently implementation, and since we're
>> at v7 and I've already spent way more time on this than I had
>> expected, I hope you understand that I'm a little hesitant to
>> make more changes (perhaps even requiring re-obtaining acks,
>> which has by itself been taking long enough for this patch) than
>> absolutely necessary to get this in.
>>
>> So - Ian, do you think the alternative proposed by George
>> would make for a meaningfully better interface?
> 
> I can see his point, but for a domctl I don't think I'd be inclined to
> insist on changing it, given the reasons you explain above for not wanting
> to at this stage.
> 
> I'd most likely be inclined to ack a follow up patch (from whomsoever is
> motivated enough to produce one) which revved the API again though.

Yes, I can certainly understand just geting this off the plate.

If we fix the mmio_ro page size checks / assertion, I'm fine with the
current interface.

 -George

      reply	other threads:[~2016-02-10 10:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 15:15 [PATCH v7] x86/p2m: use large pages for MMIO mappings Jan Beulich
2016-02-02 15:27 ` Andrew Cooper
2016-02-02 15:41   ` Jan Beulich
2016-02-08 18:04 ` George Dunlap
2016-02-09  8:42   ` Jan Beulich
2016-02-09 10:56     ` George Dunlap
2016-02-09 11:48       ` Jan Beulich
2016-02-09 12:17         ` George Dunlap
2016-02-09 12:35           ` Jan Beulich
2016-02-10 10:06             ` Ian Campbell
2016-02-10 10:19               ` George Dunlap [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=56BB0E97.6060804@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@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.