From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v4] hypercall/mem: Introduce XENMEM_machphys_compat_mfn_list
Date: Tue, 29 Apr 2014 10:59:59 +0100 [thread overview]
Message-ID: <535F781F.1080508@citrix.com> (raw)
In-Reply-To: <535F9406020000780000D460@nat28.tlf.novell.com>
On 29/04/14 10:59, Jan Beulich wrote:
>>>> On 29.04.14 at 11:46, <andrew.cooper3@citrix.com> wrote:
>> Changes in v4:
>> * Use same visibility as XENMEM_machphys_mfn_list. Leave note about next
>> subop.
> I'm fine with this now with one possible minor correction (could be done
> while committing, so no need to resubmit just because of this):
>
>> --- a/xen/include/public/memory.h
>> +++ b/xen/include/public/memory.h
>> @@ -187,6 +187,16 @@ typedef struct xen_machphys_mfn_list xen_machphys_mfn_list_t;
>> DEFINE_XEN_GUEST_HANDLE(xen_machphys_mfn_list_t);
>>
>> /*
>> + * For a compat toolstack domain, this is identical to
>> + * XENMEM_machphys_mfn_list.
>> + *
>> + * For a non compat toolstack domain, this functions similarly to
>> + * XENMEM_machphys_mfn_list, but returns the mfns making up the compatibility
>> + * m2p table.
>> + */
>> +#define XENMEM_machphys_compat_mfn_list 25
> I think it is now at least misleading to say "toolstack domain" in the
> comment above - in both cases I'd prefer this to just say "caller".
>
> Jan
>
Ok - I am happy with that.
~Andrew
prev parent reply other threads:[~2014-04-29 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 9:46 [PATCH v4] hypercall/mem: Introduce XENMEM_machphys_compat_mfn_list Andrew Cooper
2014-04-29 9:59 ` Jan Beulich
2014-04-29 9:59 ` Andrew Cooper [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=535F781F.1080508@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.