xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Tim Deegan <tim@xen.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v3] xen: fix setup of PVH Dom0 memory map
Date: Tue, 27 May 2014 18:02:15 -0700	[thread overview]
Message-ID: <20140527180215.4a81f4ed@mantra.us.oracle.com> (raw)
In-Reply-To: <538327F90200007800015A45@mail.emea.novell.com>

On Mon, 26 May 2014 10:39:37 +0100
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 23.05.14 at 17:27, <roger.pau@citrix.com> wrote:
> > This patch adds the holes removed by MMIO regions to the end of the
> > memory map for PVH Dom0, so the guest OS doesn't have to manually
> > populate this memory.
> > 
> > Also, provide a suitable e820 memory map for PVH Dom0, that matches
> > the underlying p2m map. This means that PVH guests should always use
> > XENMEM_memory_map in order to obtain the e820, even when running as
> > Dom0.
> > 
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> 
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> 
> But before considering for committing I'd want Mukesh's
> agreement with at least the general approach.
> 
> Jan

Ok, I'm in agreement with this approach. Will need to change code on
linux side, but shouldn't be too bad.

thanks
mukesh

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2014-05-28  1:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 15:27 [PATCH v3] xen: fix setup of PVH Dom0 memory map Roger Pau Monne
2014-05-26  9:39 ` Jan Beulich
2014-05-27 11:40   ` David Vrabel
2014-05-28  1:02   ` Mukesh Rathor [this message]

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=20140527180215.4a81f4ed@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=roger.pau@citrix.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).