xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>,
	Jan Beulich <JBeulich@suse.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH V11 4/5] p2m: Always use hostp2m when clipping rangesets
Date: Thu, 20 Dec 2018 15:22:17 +0000	[thread overview]
Message-ID: <3f4ea207-2c8a-3f05-9608-6fd64479aa76@citrix.com> (raw)
In-Reply-To: <6e9d24c0-92d0-43be-d490-f3ccaba7e8be@bitdefender.com>

On 12/20/18 3:14 PM, Razvan Cojocaru wrote:
> On 12/20/18 4:49 PM, Jan Beulich wrote:
>>>>> On 20.12.18 at 15:38, <george.dunlap@citrix.com> wrote:
>>> Can we just for now take the text as I proposed it?  You can argue about
>>> the right thing to do when we do the alleged clean-up.
>>
>> With the "We should probably return an error ..." part dropped
>> or replaced by e.g. "We should revisit this" this would be okay
>> with me. But you're the maintainer of the code anyway...
> 
> Is the change something that can be done on commit (if there are no
> other objections of course), or should I re-submit the series with the
> comment changed?

Well I haven't given a review of your changes to v4 yet; this was just
trying to answer Jan's question about what ideal interface would be.

If it's just comments I can fix things up on check-in.

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-12-20 15:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  9:18 [PATCH V11 0/5] Fix VGA logdirty related display freezes with altp2m Razvan Cojocaru
2018-12-05  9:18 ` [PATCH V11 1/5] x86/p2m: allocate logdirty_ranges for altp2ms Razvan Cojocaru
2018-12-05  9:18 ` [PATCH V11 2/5] x86/p2m: refactor p2m_reset_altp2m() Razvan Cojocaru
2018-12-05  9:18 ` [PATCH V11 3/5] x86/altp2m: fix display frozen when switching to a new view early Razvan Cojocaru
2018-12-20 15:31   ` George Dunlap
2018-12-05  9:18 ` [PATCH V11 4/5] p2m: Always use hostp2m when clipping rangesets Razvan Cojocaru
2018-12-05 16:30   ` Jan Beulich
2018-12-13 10:22     ` Razvan Cojocaru
2018-12-13 10:43       ` Jan Beulich
2018-12-19 17:26         ` George Dunlap
2018-12-20  8:20           ` Jan Beulich
2018-12-20 12:59             ` George Dunlap
2018-12-20 13:52               ` Jan Beulich
2018-12-20 14:38                 ` George Dunlap
2018-12-20 14:49                   ` Jan Beulich
2018-12-20 15:14                     ` Razvan Cojocaru
2018-12-20 15:22                       ` George Dunlap [this message]
2018-12-20 15:01                   ` Jan Beulich
2018-12-20 16:09   ` George Dunlap
2018-12-20 16:25     ` Razvan Cojocaru
2018-12-20 16:31   ` George Dunlap
2018-12-20 16:46     ` Razvan Cojocaru
2018-12-05  9:18 ` [PATCH V11 5/5] p2m: change_type_range: Only invalidate mapped gfns Razvan Cojocaru
2018-12-20 16:17   ` George Dunlap

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=3f4ea207-2c8a-3f05-9608-6fd64479aa76@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=roger.pau@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).