xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH v1 3/8]: PVH startup changes (enlighten.c)
Date: Thu, 4 Oct 2012 18:25:18 -0700	[thread overview]
Message-ID: <20121004182518.76e9624a@mantra.us.oracle.com> (raw)
In-Reply-To: <1349339920.650.220.camel@zakaz.uk.xensource.com>

On Thu, 4 Oct 2012 09:38:40 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:

> On Wed, 2012-10-03 at 23:37 +0100, Mukesh Rathor wrote:
> > On Wed, 3 Oct 2012 12:58:22 +0100
> > Ok, finally, focussing on this, the issue with pfn in dom0 is that
> > I need pfn allocated in construct_dom0() and be mapped so that the
> > guest can just do :
> > 
> > HYPERVISOR_shared_info=(struct shared_info
> > *)__va(xen_start_info->shared_info);
> > 
> > How about following I am experimenting with right now:
> > 
> > in construct_dom0():
> > 
> >     vstartinfo_end   = (vstartinfo_start +
> >                         sizeof(struct start_info) +
> >                         sizeof(struct dom0_vga_console_info));
> > 
> >     if ( is_hybrid_domain(d) ) {
> >         start_info_pfn_addr = round_pgup(vstartinfo_end) - v_start;
> >         vstartinfo_end   += PAGE_SIZE;
> >     }
> > 
> > I can then put (PFN: start_info_pfn_addr)->(MFN:
> > virt_to_maddr(d->shared_info)) in the p2m, and dom0 just has to do
> > __va(), like domU does now.  I wont' need to special case dom0 then.
> > 
> > Do you foresee any problems with this approach?
> 
> Hard to say without all the surrounding context but it seems plausible
> to me.


Ok, above works. So no dom0 special case in linux now to map shared_page.

thanks
Mukesh

      reply	other threads:[~2012-10-05  1:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 19:16 [PATCH v1 3/8]: PVH startup changes (enlighten.c) Mukesh Rathor
2012-09-24 12:07 ` Stefano Stabellini
2012-09-24 22:43   ` Mukesh Rathor
2012-09-25 10:03     ` Stefano Stabellini
2012-09-26  1:04       ` Mukesh Rathor
2012-09-26 11:33         ` Stefano Stabellini
2012-09-26 11:44           ` Ian Campbell
2012-10-03  1:36           ` Mukesh Rathor
2012-10-03  2:03             ` Mukesh Rathor
2012-10-03 11:58               ` Stefano Stabellini
2012-10-03 12:05                 ` Ian Campbell
2012-10-03 12:36                   ` Stefano Stabellini
2012-10-05  1:35                   ` Mukesh Rathor
2012-10-05  9:23                     ` Ian Campbell
2012-10-08 12:41                       ` Konrad Rzeszutek Wilk
2012-10-09  1:07                         ` Mukesh Rathor
2012-10-03 22:37                 ` Mukesh Rathor
2012-10-04  8:38                   ` Ian Campbell
2012-10-05  1:25                     ` 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=20121004182518.76e9624a@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=konrad.wilk@oracle.com \
    /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).