From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>, WeiLiu <wei.liu2@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2/2] x86/mm: Use mfn_t for make_cr3()
Date: Wed, 30 Aug 2017 09:47:21 -0600 [thread overview]
Message-ID: <59A6FA290200007800175AC2@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20170830130824.wmnetvv4iajkgvoi@citrix.com>
>>> On 30.08.17 at 15:08, <wei.liu2@citrix.com> wrote:
> On Wed, Aug 30, 2017 at 01:19:33PM +0100, Andrew Cooper wrote:
>> No functional change.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> Reviewed-by: Wei Liu <wei.liu2@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
As a side note, I can see instances of mmfn here too, but here (other
than in patch 1) the first m quite clearly stands for "monitor". There's
nothing formally called "monitor" on that other path, though.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-30 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 12:19 [PATCH 1/2] x86/mm: Use mfn_t for new_guest_cr3() Andrew Cooper
2017-08-30 12:19 ` [PATCH 2/2] x86/mm: Use mfn_t for make_cr3() Andrew Cooper
2017-08-30 13:08 ` Wei Liu
2017-08-30 15:47 ` Jan Beulich [this message]
2017-08-30 18:59 ` Tim Deegan
2017-09-01 17:30 ` George Dunlap
2017-08-30 13:08 ` [PATCH 1/2] x86/mm: Use mfn_t for new_guest_cr3() Wei Liu
2017-08-30 15:45 ` Jan Beulich
2017-08-30 15:57 ` Andrew Cooper
2017-08-30 16:04 ` Jan Beulich
2017-09-01 17:29 ` 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=59A6FA290200007800175AC2@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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.