From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [RFC PATCH] PVH: cleanup of p2m upon p2m destroy
Date: Fri, 31 Jan 2014 18:38:38 -0800 [thread overview]
Message-ID: <20140131183838.27075db3@mantra.us.oracle.com> (raw)
In-Reply-To: <20131218165152.GO24792@deinos.phlegethon.org>
On Wed, 18 Dec 2013 17:51:52 +0100
Tim Deegan <tim@xen.org> wrote:
> At 11:09 +0100 on 18 Dec (1387361398), Tim Deegan wrote:
> > > An alternative might be to just create a link list then and walk
> > > it. In general, foreign mappings should be very small, so the
> > > overhead of 16 bytes per page for the link list might not be too
> > > bad. I will code it if there is no disagreement from any
> > > maintainer... everyone has different ideas :)...
> >
> > I think it would be best to walk the p2m trie (i.e. bounded by
> > amount of RAM, rather than max GFN) and do it preemptably. I'll
> > look into something like that for the mem_sharing loop today, and
> > foreign mapping code can reuse it.
>
> What I've ended up with is making p2m_change_entry_type_global()
> preemptible (which is a bigger task but will be needed as domains get
> bigger). Do you think that using that function to switch all mappings
> from p2m_foreign to p2m_invalid, appropriately late in the teardown,
> will be good enough for what you need?
>
> Cheers,
>
> Tim.
Finally, coming back to this, the answer is yes. Looks like all I need
to do is:
diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c
index 9faa663..268a8a2 100644
--- a/xen/arch/x86/mm/p2m.c
+++ b/xen/arch/x86/mm/p2m.c
@@ -470,6 +470,10 @@ void p2m_teardown(struct p2m_domain *p2m)
p2m_lock(p2m);
+ /* pvh: we must release refcnt on all foreign pages */
+ if ( is_pvh_domain(d) )
+ p2m_change_entry_type_global(d, p2m_map_foreign, p2m_invalid);
+
/* Try to unshare any remaining shared p2m entries. Safeguard
* Since relinquish_shared_pages should have done the work. */
for ( gfn=0; gfn < p2m->max_mapped_pfn; gfn++ )
In this call, the new atomic_write_ept_entry() will DTRT:
static inline void atomic_write_ept_entry(ept_entry_t *entryptr,
const ept_entry_t *new)
{
if ( p2m_is_foreign(new->sa_p2mt) )
{
struct page_info *page;
struct domain *fdom;
ASSERT(mfn_valid(new->mfn));
page = mfn_to_page(new->mfn);
fdom = page_get_owner(page);
get_page(page, fdom);
}
if ( p2m_is_foreign(entryptr->sa_p2mt) )
put_page(mfn_to_page(entryptr->mfn));
write_atomic(&entryptr->epte, new->epte);
}
If that sounds ok, I'm ready to submit dom0 PVH patches. Pl lmk.
thanks
Mukesh
next prev parent reply other threads:[~2014-02-01 2:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 1:47 [RFC PATCH] PVH: cleanup of p2m upon p2m destroy Mukesh Rathor
2013-12-17 8:42 ` Jan Beulich
2013-12-17 10:19 ` Tim Deegan
2013-12-18 2:44 ` Mukesh Rathor
2013-12-18 10:03 ` Jan Beulich
2013-12-18 11:32 ` Dietmar Hahn
2013-12-18 10:09 ` Tim Deegan
2013-12-18 16:51 ` Tim Deegan
2013-12-19 2:01 ` Mukesh Rathor
2013-12-19 10:50 ` Tim Deegan
2013-12-20 2:00 ` Mukesh Rathor
2013-12-20 9:22 ` Tim Deegan
2014-02-01 2:38 ` Mukesh Rathor [this message]
2014-02-03 10:12 ` Tim Deegan
2013-12-20 13:58 ` George Dunlap
2013-12-20 14:29 ` Tim Deegan
2013-12-18 1:01 ` Mukesh Rathor
2013-12-18 8:12 ` Jan Beulich
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=20140131183838.27075db3@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=JBeulich@suse.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).