From: George Dunlap <george.dunlap@eu.citrix.com>
To: Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, keir.xen@gmail.com,
eddie.dong@intel.com, jun.nakajima@intel.com
Subject: Re: [V8 PATCH 5/8] pvh dom0: Add and remove foreign pages
Date: Tue, 8 Apr 2014 16:40:46 +0100 [thread overview]
Message-ID: <5344187E.3010601@eu.citrix.com> (raw)
In-Reply-To: <20140408141840.GD27003@deinos.phlegethon.org>
On 04/08/2014 03:18 PM, Tim Deegan wrote:
> At 15:07 +0100 on 08 Apr (1396966037), Jan Beulich wrote:
>>>>> On 08.04.14 at 16:01, <tim@xen.org> wrote:
>>> At 08:36 +0100 on 08 Apr (1396942615), Jan Beulich wrote:
>>>>>>> On 08.04.14 at 03:11, <mukesh.rathor@oracle.com> wrote:
>>>>> On Mon, 07 Apr 2014 07:57:56 +0100
>>>>> "Jan Beulich" <JBeulich@suse.com> wrote:
>>>>>> In the end I think we'll want to make them all report proper error
>>>>>> codes...
>>>>>
>>>>> Ok, how about the following patch then? If it's OK, I'd like to submit
>>>>> independently.
>>>>
>>>> Yes, I just now stumbled across this oddity too. Looks generally
>>>> like what we want
>>>
>>> While in general I like this, I'm worried about inverting the sense of
>>> the return code -- that seems like setting a trap for ourselves with
>>> backporting patches past this one.
>>>
>>> I'd be inclined to change the name of the function as a safety catch,
>>> though I can't immediately think of a good new name for set_p2m_entry.
>>> Maybe just truncate it to set_p2m()?
>>
>> That could mean a different thing. How about p2m_set_entry(),
>> at once matching most other P2M functions using p2m_ as their
>> prefix.
>
> Sure. I think the current implementation in p2m_pt might be using
> that name, but it could be given a more meaningful name at the same
> time.
Ack to the rename.
-George
next prev parent reply other threads:[~2014-04-08 15:43 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 1:39 [V8 PATCH 0/8] pvh dom0 Mukesh Rathor
2014-03-22 1:39 ` [V8 PATCH 1/8] pvh dom0: move some pv specific code to static functions Mukesh Rathor
2014-03-22 1:39 ` [V8 PATCH 2/8] pvh dom0: construct_dom0 changes Mukesh Rathor
2014-03-26 19:05 ` George Dunlap
2014-03-27 10:14 ` Jan Beulich
2014-03-27 10:55 ` George Dunlap
2014-03-27 11:03 ` George Dunlap
2014-03-27 15:04 ` Jan Beulich
2014-03-27 15:30 ` Tim Deegan
2014-04-05 0:53 ` Mukesh Rathor
2014-04-07 7:30 ` Jan Beulich
2014-04-07 9:27 ` George Dunlap
2014-03-22 1:39 ` [V8 PATCH 3/8] pvh dom0: Introduce p2m_map_foreign Mukesh Rathor
2014-03-24 9:00 ` Jan Beulich
2014-03-27 12:29 ` George Dunlap
2014-04-05 0:57 ` Mukesh Rathor
2014-03-22 1:39 ` [V8 PATCH 4/8] pvh dom0: make xsm_map_gmfn_foreign available for x86 Mukesh Rathor
2014-03-25 17:53 ` Daniel De Graaf
2014-03-22 1:39 ` [V8 PATCH 5/8] pvh dom0: Add and remove foreign pages Mukesh Rathor
2014-03-24 9:26 ` Jan Beulich
2014-04-05 1:17 ` Mukesh Rathor
2014-04-07 6:57 ` Jan Beulich
2014-04-08 1:11 ` Mukesh Rathor
2014-04-08 7:36 ` Jan Beulich
2014-04-08 14:01 ` Tim Deegan
2014-04-08 14:07 ` Jan Beulich
2014-04-08 14:18 ` Tim Deegan
2014-04-08 15:40 ` George Dunlap [this message]
2014-04-11 1:33 ` Mukesh Rathor
2014-04-11 8:02 ` Jan Beulich
2014-03-22 1:39 ` [V8 PATCH 6/8] pvh dom0: allow get_pg_owner for translated domains Mukesh Rathor
2014-03-24 9:31 ` Jan Beulich
2014-04-01 14:31 ` George Dunlap
2014-04-05 0:59 ` Mukesh Rathor
2014-03-22 1:39 ` [V8 PATCH 7/8] pvh dom0: add check for pvh in vioapic_range Mukesh Rathor
2014-03-24 9:34 ` Jan Beulich
2014-04-01 14:40 ` George Dunlap
2014-04-01 15:09 ` Jan Beulich
2014-04-05 1:00 ` Mukesh Rathor
2014-04-07 6:59 ` Jan Beulich
2014-04-07 9:28 ` George Dunlap
2014-04-08 1:00 ` Mukesh Rathor
2014-04-08 8:21 ` Jan Beulich
2014-03-22 1:39 ` [V8 PATCH 8/8] pvh dom0: add opt_dom0pvh to setup.c Mukesh Rathor
2014-03-24 9:35 ` Jan Beulich
2014-03-24 8:57 ` [V8 PATCH 0/8] pvh dom0 Jan Beulich
2014-03-24 21:36 ` Mukesh Rathor
2014-03-28 17:36 ` Roger Pau Monné
2014-03-28 19:48 ` Mukesh Rathor
2014-04-01 16:04 ` George Dunlap
2014-04-02 1:22 ` Mukesh Rathor
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=5344187E.3010601@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir.xen@gmail.com \
--cc=tim@xen.org \
--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).