From: "Jan Beulich" <JBeulich@suse.com>
To: "Razvan Cojocaru" <rcojocaru@bitdefender.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
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: [Xen-devel] [PATCH] x86/altp2m: move altp2m_get_effective_entry() under CONFIG_HVM
Date: Tue, 14 May 2019 10:27:45 -0600 [thread overview]
Message-ID: <5CDAEC81020000780022ED86@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190514162745.CDqTc5F_gsM72vPiQwzI-Zu1o4jJZ-8meaD_c6RCwWk@z> (raw)
In-Reply-To: <1557850437-27656-1-git-send-email-rcojocaru@bitdefender.com>
>>> On 14.05.19 at 18:13, <rcojocaru@bitdefender.com> wrote:
> All its callers live inside #ifdef CONFIG_HVM sections.
>
> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Thanks!
> --- a/xen/include/asm-x86/p2m.h
> +++ b/xen/include/asm-x86/p2m.h
> @@ -514,6 +514,7 @@ static inline unsigned long mfn_to_gfn(struct domain *d, mfn_t mfn)
> return mfn_x(mfn);
> }
>
> +#ifdef CONFIG_HVM
> #define AP2MGET_prepopulate true
> #define AP2MGET_query false
>
> @@ -525,6 +526,7 @@ static inline unsigned long mfn_to_gfn(struct domain *d, mfn_t mfn)
> int altp2m_get_effective_entry(struct p2m_domain *ap2m, gfn_t gfn, mfn_t *mfn,
> p2m_type_t *t, p2m_access_t *a,
> bool prepopulate);
> +#endif
>
> /* Deadlock-avoidance scheme when calling get_gfn on different gfn's */
> struct two_gfns {
I don't think these adjustments are strictly needed, but at least for
now they of course also don't hurt.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-14 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 16:13 [PATCH] x86/altp2m: move altp2m_get_effective_entry() under CONFIG_HVM Razvan Cojocaru
2019-05-14 16:13 ` [Xen-devel] " Razvan Cojocaru
2019-05-14 16:27 ` Jan Beulich [this message]
2019-05-14 16:27 ` Jan Beulich
2019-05-15 6:53 ` Wei Liu
2019-05-15 6:53 ` [Xen-devel] " Wei Liu
2019-05-15 8:55 ` George Dunlap
2019-05-15 8:55 ` [Xen-devel] " George Dunlap
2019-05-15 9:28 ` Wei Liu
2019-05-15 9:28 ` [Xen-devel] " Wei Liu
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=5CDAEC81020000780022ED86@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.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).