xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>, Xen-devel@lists.xensource.com
Cc: keir.xen@gmail.com, tim@xen.org, JBeulich@suse.com
Subject: Re: [V3 PATCH 9/9] pvh dom0: add opt_dom0pvh to setup.c
Date: Wed, 27 Nov 2013 15:00:43 +0000	[thread overview]
Message-ID: <5296091B.4070704@eu.citrix.com> (raw)
In-Reply-To: <1385519230-21132-10-git-send-email-mukesh.rathor@oracle.com>

On 11/27/2013 02:27 AM, Mukesh Rathor wrote:
> Add opt_dom0pvh. Note, pvh dom0 is disabled until the fixme in
> domain_build.c is resolved. The fixme is added by patch title:
> "PVH dom0: construct_dom0 changes"

So it's been asked before but I haven't seen an answer yet: What exactly 
is the problem here, and when might it be fixed?

  -George

  reply	other threads:[~2013-11-27 15:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  2:27 [V3 PATCH 0/9]: PVH dom0 Mukesh Rathor
2013-11-27  2:27 ` [V3 PATCH 1/9] PVH dom0: iommu related changes Mukesh Rathor
2013-11-27  2:27 ` [V3 PATCH 2/9] PVH dom0: create add_mem_mapping_for_xlate() function Mukesh Rathor
2013-12-02 12:16   ` Jan Beulich
2013-11-27  2:27 ` [V3 PATCH 3/9] PVH dom0: move some pv specific code to static functions Mukesh Rathor
2013-12-02 12:30   ` Jan Beulich
2013-11-27  2:27 ` [V3 PATCH 4/9] dom0: construct_dom0 changes Mukesh Rathor
2013-12-02 12:36   ` Jan Beulich
2013-11-27  2:27 ` [V3 PATCH 5/9] PVH dom0: implement XENMEM_add_to_physmap_range for x86 Mukesh Rathor
2013-12-02 12:47   ` Jan Beulich
2013-12-03  0:05     ` Mukesh Rathor
2013-12-03  7:48       ` Jan Beulich
2013-12-03 19:49         ` Mukesh Rathor
2013-12-04  8:03           ` Jan Beulich
2013-11-27  2:27 ` [V3 PATCH 6/9] PVH dom0: Introduce p2m_map_foreign Mukesh Rathor
2013-11-27  2:27 ` [V3 PATCH 7/9] pvh: change xsm_add_to_physmap Mukesh Rathor
2013-11-27 16:46   ` Daniel De Graaf
2013-11-27 20:29     ` Mukesh Rathor
2013-11-29  9:21       ` Jan Beulich
2013-12-02 12:55   ` Jan Beulich
2013-11-27  2:27 ` [V3 PATCH 8/9] pvh dom0: Add and remove foreign pages Mukesh Rathor
2013-12-02 12:57   ` Jan Beulich
2013-11-27  2:27 ` [V3 PATCH 9/9] pvh dom0: add opt_dom0pvh to setup.c Mukesh Rathor
2013-11-27 15:00   ` George Dunlap [this message]
2013-11-27 20:12     ` Mukesh Rathor
2013-11-28 11:54       ` George Dunlap
2013-11-29  9:29         ` Jan Beulich
2013-12-02 13:00   ` Jan Beulich
2013-12-02 15:09   ` Roger Pau Monné
2013-12-02 19:30     ` Mukesh Rathor
2013-12-02 19:38       ` Roger Pau Monné
2013-12-02 20:38         ` Mukesh Rathor
2013-12-02 20:46           ` Mukesh Rathor
2013-12-03  2:33             ` Mukesh Rathor
2013-12-03 10:30               ` Roger Pau Monné
2013-12-03 19:51                 ` Mukesh Rathor
2013-12-03 10:54         ` Jan Beulich
2013-11-28 12:07 ` [V3 PATCH 0/9]: PVH dom0 George Dunlap
2013-11-29  9:17   ` Jan Beulich
2013-12-02 11:39     ` George Dunlap
2013-12-01 23:53   ` 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=5296091B.4070704@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=keir.xen@gmail.com \
    --cc=mukesh.rathor@oracle.com \
    --cc=tim@xen.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).