From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Tim Deegan <tim@xen.org>
Cc: JBeulich@suse.com, George.Dunlap@eu.citrix.com,
eddie.dong@intel.com, keir.xen@gmail.com, jun.nakajima@intel.com,
xen-devel@lists.xenproject.org
Subject: Re: [V10 PATCH 3/4] pvh dom0: Add and remove foreign pages
Date: Thu, 1 May 2014 18:45:18 -0700 [thread overview]
Message-ID: <20140501184518.2ebccdb8@mantra.us.oracle.com> (raw)
In-Reply-To: <20140501161908.GI86038@deinos.phlegethon.org>
On Thu, 1 May 2014 18:19:08 +0200
Tim Deegan <tim@xen.org> wrote:
> Hi,
>
> Nearly there, except that the teardown code is now gone, with nothing
> replacing it. Ideally we'd have some logic to find active EPT L1
> tables and undo the foreign refcounts. If not that, then:
> - a hard-coded check, in p2m_add_foreign I suppose, that only allows
> foreign mappings to be added to a p2m for the hardware domain,
> with a pvh fixme comment explaining why; and
> - another pvh fixme comment in the p2m teardown code to say that
> once non-hardware domains can have foreign mappings there will
> have to be some cleanup code to handle them.
Added fixmes...
> Also, in the inner refcounting logic:
>
> At 18:06 -0700 on 29 Apr (1398791207), Mukesh Rathor wrote:
> > diff --git a/xen/arch/x86/mm/p2m-ept.c b/xen/arch/x86/mm/p2m-ept.c
> > index c0bfc50..11474e8 100644
> > --- a/xen/arch/x86/mm/p2m-ept.c
> > +++ b/xen/arch/x86/mm/p2m-ept.c
> > @@ -36,8 +36,6 @@
> >
> > #define
> > atomic_read_ept_entry(__pepte) \
> > ( (ept_entry_t) { .epte = read_atomic(&(__pepte)->epte) } )
> > -#define atomic_write_ept_entry(__pepte,
> > __epte) \
> > - write_atomic(&(__pepte)->epte, (__epte).epte)
> >
> > #define is_epte_present(ept_entry) ((ept_entry)->epte & 0x7)
> > #define is_epte_superpage(ept_entry) ((ept_entry)->sp)
> > @@ -46,6 +44,46 @@ static inline bool_t is_epte_valid(ept_entry_t
> > *e) return (e->epte != 0 && e->sa_p2mt != p2m_invalid);
> > }
> >
> > +/* returns : 0 for success, -errno otherwise */
> > +static int atomic_write_ept_entry(ept_entry_t *entryptr,
> > ept_entry_t new,
> > + int level)
> > +{
> > + bool_t same_mfn = (new.mfn == entryptr->mfn);
> > + unsigned long oldmfn = INVALID_MFN;
> > +
> > + if ( level )
> > + {
>
> ASSERT(!(new.sp && p2m_is_foreign(new.sa_p2mt))) here?
Yeah, I debated adding p2m_is_foreign ASSERT, but didn't because iirc
Jan had said he wanted to use up the non-leaf bits for something else
in future. I suppose I can add it, it would be easy
to find it anyways.... BTW, there is no path allowing
superpage for foreign at present.
> > + write_atomic(&entryptr->epte, new.epte);
> > + return 0;
> > + }
> > +
> > + if ( unlikely(p2m_is_foreign(new.sa_p2mt)) && !same_mfn )
> > + {
> > + struct domain *fdom;
> > +
> > + if ( !mfn_valid(new.mfn) )
> > + return -EINVAL;
> > +
> > + fdom = page_get_owner(mfn_to_page(new.mfn));
>
> This needs a matching put_pg_owner() once you're done with it.
Doing page_get_owner, not get_pg_owner here, so don't think so, right?
thanks,
Mukesh
next prev parent reply other threads:[~2014-05-02 1:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 1:06 [V10 PATCH 0/4] pvh dom0 patches Mukesh Rathor
2014-04-30 1:06 ` [V10 PATCH 1/4] pvh dom0: construct_dom0 changes Mukesh Rathor
2014-05-06 15:18 ` Roger Pau Monné
2014-04-30 1:06 ` [V10 PATCH 2/4] pvh dom0: Add checks and restrictions for p2m_is_foreign Mukesh Rathor
2014-05-01 16:14 ` Tim Deegan
2014-04-30 1:06 ` [V10 PATCH 3/4] pvh dom0: Add and remove foreign pages Mukesh Rathor
2014-05-01 16:19 ` Tim Deegan
2014-05-02 1:45 ` Mukesh Rathor [this message]
2014-05-02 8:38 ` Jan Beulich
2014-05-02 8:55 ` Tim Deegan
2014-05-02 23:35 ` Mukesh Rathor
2014-05-05 7:46 ` Jan Beulich
2014-05-08 12:16 ` Tim Deegan
2014-05-08 13:25 ` Jan Beulich
2014-05-08 22:58 ` Mukesh Rathor
2014-04-30 1:06 ` [V10 PATCH 4/4] dom0: add opt_dom0pvh to setup.c Mukesh Rathor
2014-04-30 14:11 ` [V10 PATCH 0/4] pvh dom0 patches Roger Pau Monné
2014-04-30 18:12 ` Mukesh Rathor
2014-05-01 1:19 ` Mukesh Rathor
2014-05-02 11:05 ` Roger Pau Monné
2014-05-02 12:31 ` Jan Beulich
2014-05-02 14:06 ` Roger Pau Monné
2014-05-02 14:16 ` Jan Beulich
2014-05-02 14:35 ` Roger Pau Monné
2014-05-02 15:41 ` Jan Beulich
2014-05-02 16:13 ` Roger Pau Monné
2014-05-02 19:35 ` Konrad Rzeszutek Wilk
2014-05-03 0:01 ` Mukesh Rathor
2014-05-05 8:52 ` Roger Pau Monné
2014-05-06 0:28 ` Mukesh Rathor
2014-05-06 7:13 ` Roger Pau Monné
2014-05-06 8:09 ` Jan Beulich
2014-05-07 1:00 ` Mukesh Rathor
2014-05-07 7:50 ` Jan Beulich
2014-05-07 9:48 ` Roger Pau Monné
2014-05-07 11:34 ` Jan Beulich
2014-05-08 10:27 ` Roger Pau Monné
2014-05-08 10:44 ` Jan Beulich
2014-05-08 15:00 ` Roger Pau Monné
2014-05-08 15:20 ` Jan Beulich
2014-05-07 13:25 ` Konrad Rzeszutek Wilk
2014-05-08 0:04 ` Mukesh Rathor
2014-05-08 6:37 ` Jan Beulich
2014-05-08 19:15 ` Mukesh Rathor
2014-05-07 13:20 ` Konrad Rzeszutek Wilk
2014-05-07 13:38 ` Roger Pau Monné
2014-05-08 0:12 ` Mukesh Rathor
2014-05-08 10:52 ` George Dunlap
2014-05-08 13:15 ` David Vrabel
2014-05-08 22:29 ` Mukesh Rathor
2014-05-08 0:07 ` Mukesh Rathor
2014-05-06 19:38 ` Konrad Rzeszutek Wilk
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=20140501184518.2ebccdb8@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=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).