From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: xen-devel@lists.xenproject.org
Cc: George.Dunlap@eu.citrix.com, keir.xen@gmail.com, tim@xen.org,
JBeulich@suse.com
Subject: [V12 PATCH 0/4] pvh dom0 patches...
Date: Fri, 9 May 2014 17:50:39 -0700 [thread overview]
Message-ID: <1399683043-29112-1-git-send-email-mukesh.rathor@oracle.com> (raw)
Hi,
Centimeters to the finish line with the champagne bottle on the desk
staring at me, please find v12 of the pvh dom0 patches based on
c/s: 9ce8b15
git tree: git://oss.oracle.com/git/mrathor/xen.git branch: dom0pvh-v12
Changed in v12 from v11:
patch 1: none
patch 2:
- Because of p2m_is_changeable change in p2m_change_type_range, BUG_ON
for foreign type is no longer needed.
- ept_change_entry_type_global() is redone, so remove BUG_ON.
patch 3:
- re merge changes in p2m-ept.c as lot of emt functions are changed on
refresh.
- add ASSERT in atomic_write_ept_entry and add skip_foriegn.
- Revert back to using rcu* and not export get_pg_owner in p2m_add_foreign
- fix rc being unset in p2m_add_foreign if get_page_from_gfn fails.
patch 4: none
thanks,
Mukesh
next reply other threads:[~2014-05-10 0:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 0:50 Mukesh Rathor [this message]
2014-05-10 0:50 ` [V12 PATCH 1/4] pvh dom0: construct_dom0 changes Mukesh Rathor
2014-05-10 0:50 ` [V12 PATCH 2/4] pvh dom0: Add checks and restrictions for p2m_is_foreign Mukesh Rathor
2014-05-10 0:50 ` [V12 PATCH 3/4] pvh dom0: Add and remove foreign pages Mukesh Rathor
2014-05-12 10:34 ` Jan Beulich
2014-05-13 1:02 ` Mukesh Rathor
2014-05-13 7:09 ` Jan Beulich
2014-05-14 0:55 ` Mukesh Rathor
2014-05-14 6:59 ` Jan Beulich
2014-05-15 1:59 ` Mukesh Rathor
2014-05-15 8:02 ` Jan Beulich
2014-05-16 1:39 ` Mukesh Rathor
2014-05-10 0:50 ` [V12 PATCH 4/4] dom0: add opt_dom0pvh to setup.c 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=1399683043-29112-1-git-send-email-mukesh.rathor@oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.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).