From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George.Dunlap@eu.citrix.com, tim@xen.org, eddie.dong@intel.com,
keir.xen@gmail.com, jun.nakajima@intel.com,
xen-devel@lists.xenproject.org
Subject: Re: [V9 PATCH 6/8] pvh dom0: Add and remove foreign pages
Date: Tue, 22 Apr 2014 17:28:13 -0700 [thread overview]
Message-ID: <20140422172813.001e1de8@mantra.us.oracle.com> (raw)
In-Reply-To: <5356364D020000780000A8EF@nat28.tlf.novell.com>
On Tue, 22 Apr 2014 08:28:45 +0100
"Jan Beulich" <JBeulich@suse.com> wrote:
> >>> On 22.04.14 at 02:19, <mukesh.rathor@oracle.com> wrote:
> > On Wed, 16 Apr 2014 18:37:42 -0700
> > Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> >
> >> On Wed, 16 Apr 2014 17:00:35 +0100
> >> "Jan Beulich" <JBeulich@suse.com> wrote:
> >>
............
> > /* following will take a refcnt on the mfn */
> > page = get_page_from_gfn(fdom, fgfn, &p2mt, P2M_ALLOC);
> > - if ( !page || !p2m_is_valid(p2mt) )
> > + if ( !page || !p2m_is_strict_ram(p2mt) )
> > {
> > if ( page )
> > put_page(page);
> > diff --git a/xen/include/asm-x86/p2m.h b/xen/include/asm-x86/p2m.h
> > index 47604da..e0bf6dc 100644
> > --- a/xen/include/asm-x86/p2m.h
> > +++ b/xen/include/asm-x86/p2m.h
> > @@ -165,6 +165,7 @@ typedef unsigned int p2m_query_t;
> >
> > /* Useful predicates */
> > +#define p2m_is_strict_ram(_t) (p2m_to_mask(_t) &
> > p2m_to_mask(p2m_ram_rw))
>
> Not sure - this now precludes mapping log-dirty or r/o pages, i.e. I
> think you went from too relaxed to too strict. I think the question
> needs answering in a more abstract fashion first, i.e. without code
> written immediately: Which pages absolutely need to be foreign-
> mappable and which ones can safely get foreign-mapped. My first
> thought would be P2M_RAM_TYPES & ~P2M_HOLE_TYPES, with
> P2M_HOLE_TYPES contained in P2M_RAM_TYPES generating a kind
> of -EAGAIN notification while triggering the re-creation of the page
> (which already is an indication that instead of P2M_HOLE_TYPES it
> might well need to be P2M_PAGING_TYPES).
The current use case is p2m_ram_rw, my approach would be start with
minimum and add more as needed when features like migration, passthru, etc
are added. My understanding of the various p2m types is limited, so I
am at your mercy here to advise what types to anticipate. IMO, just
checking for P2M_RAM_TYPES might suffice, I can additionally add check
to make sure it's not P2M_HOLE_TYPES. Please lmk.
thanks
mukesh
next prev parent reply other threads:[~2014-04-23 0:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 0:12 [V9 PATCH 0/8] pvh dom0 patches Mukesh Rathor
2014-04-16 0:12 ` [V9 PATCH 1/8] pvh dom0: move some pv specific code to static functions Mukesh Rathor
2014-04-16 0:12 ` [V9 PATCH 2/8] pvh dom0: construct_dom0 changes Mukesh Rathor
2014-04-16 0:12 ` [V9 PATCH 3/8] pvh dom0: Introduce p2m_map_foreign Mukesh Rathor
2014-04-16 0:12 ` [V9 PATCH 4/8] pvh dom0: Add checks and restrictions for p2m_is_foreign Mukesh Rathor
2014-04-16 15:28 ` Jan Beulich
2014-04-16 0:12 ` [V9 PATCH 5/8] pvh dom0: make xsm_map_gmfn_foreign available for x86 Mukesh Rathor
2014-04-16 14:29 ` Daniel De Graaf
2014-04-16 0:12 ` [V9 PATCH 6/8] pvh dom0: Add and remove foreign pages Mukesh Rathor
2014-04-16 16:00 ` Jan Beulich
2014-04-17 1:37 ` Mukesh Rathor
2014-04-17 6:50 ` Jan Beulich
2014-04-17 12:36 ` Tim Deegan
2014-04-17 13:58 ` Jan Beulich
2014-04-19 0:59 ` Mukesh Rathor
2014-04-21 16:10 ` Jan Beulich
2014-04-24 2:21 ` Mukesh Rathor
2014-04-24 6:44 ` Jan Beulich
2014-04-24 9:46 ` Tim Deegan
2014-04-25 2:09 ` Mukesh Rathor
2014-04-25 6:49 ` Jan Beulich
2014-04-25 23:23 ` Mukesh Rathor
2014-04-26 0:06 ` Mukesh Rathor
2014-04-28 7:23 ` Jan Beulich
2014-04-25 8:55 ` Tim Deegan
2014-04-25 23:29 ` Mukesh Rathor
2014-04-26 1:34 ` Mukesh Rathor
2014-04-28 8:54 ` Jan Beulich
2014-04-28 9:09 ` Tim Deegan
2014-04-22 0:19 ` Mukesh Rathor
2014-04-22 7:28 ` Jan Beulich
2014-04-23 0:28 ` Mukesh Rathor [this message]
2014-04-23 9:03 ` Jan Beulich
2014-04-23 16:13 ` Andres Lagar-Cavilla
2014-04-24 16:37 ` Tim Deegan
2014-04-16 0:12 ` [V9 PATCH 7/8] pvh dom0: check for vioapic null ptr in vioapic_range Mukesh Rathor
2014-04-16 16:05 ` Jan Beulich
2014-04-17 1:44 ` Mukesh Rathor
2014-04-17 6:54 ` Jan Beulich
2014-04-22 0:59 ` Mukesh Rathor
2014-04-22 7:33 ` Jan Beulich
2014-04-23 0:11 ` Mukesh Rathor
2014-04-23 9:07 ` Jan Beulich
2014-04-23 21:18 ` Mukesh Rathor
2014-04-24 6:49 ` Jan Beulich
2014-04-24 23:28 ` Mukesh Rathor
2014-05-06 0:19 ` Mukesh Rathor
2014-05-06 7:44 ` Jan Beulich
2014-05-07 1:07 ` Mukesh Rathor
2014-05-07 6:47 ` Jan Beulich
2014-05-07 23:52 ` Mukesh Rathor
2014-05-08 6:33 ` Jan Beulich
2014-04-16 0:12 ` [V9 PATCH 8/8] pvh dom0: add opt_dom0pvh to setup.c Mukesh Rathor
2014-04-16 12:57 ` Konrad Rzeszutek Wilk
2014-04-16 13:01 ` Andrew Cooper
2014-04-16 16:09 ` Jan Beulich
2014-04-16 14:57 ` [V9 PATCH 0/8] pvh dom0 patches Roger Pau Monné
2014-04-16 21:15 ` Mukesh Rathor
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=20140422172813.001e1de8@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).