All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Sandesh <sandesh.ahiremath@wipro.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: doubt on domU segment mappings
Date: Mon, 21 Jul 2008 18:36:29 +0100	[thread overview]
Message-ID: <20080721173629.GI4501@implementation.uk.xensource.com> (raw)
In-Reply-To: <1216661791.17572.43.camel@ec4t16cg-1518809>

Sandesh, le Mon 21 Jul 2008 23:06:31 +0530, a écrit :
> On Mon, 2008-07-21 at 18:08 +0100, Samuel Thibault wrote:
> > > or at least the pt_base mapping.
> > 
> > Well the problem is that the domU most probably has destroyed it
> > completely already.
> can't i preserve them, at least the base pointers??? :)
> can u just point to me where these segment mappings are recreated in
> domU(linux 2.6.18.1).

Linux domU starts in head-xen.S's startup_32, which calls start_kernel,
which itself becomes the idle thread, so I guess it actually preserves
it.  As for the pt_base address, you can get it from linux itself from
the xen_start_info structure.  There is no way to get that from other
domains.

> > > > Again, dom0 doesn't map them any more, it doesn't need them any
> > more.
> > > then how will the domU kernel memory is accessed? are they mapped to
> > the
> > > domU pg_tables?
> so even pt_base becomes invalid once domU has booted?? 

DomU is free to do so, yes.

Samuel

  reply	other threads:[~2008-07-21 17:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 16:50 doubt on domU segment mappings Sandesh
2008-07-21 16:42 ` Samuel Thibault
2008-07-21 17:04   ` Sandesh
2008-07-21 16:55     ` Samuel Thibault
2008-07-21 17:13       ` Sandesh
2008-07-21 17:08         ` Samuel Thibault
2008-07-21 17:36           ` Sandesh
2008-07-21 17:36             ` Samuel Thibault [this message]
2008-07-21 18:51       ` Sandesh
2008-07-21 18:51         ` Samuel Thibault
2008-07-21 17:08     ` Sandesh
2008-07-21 17:00       ` Samuel Thibault
2008-07-21 17:14         ` Sandesh

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=20080721173629.GI4501@implementation.uk.xensource.com \
    --to=samuel.thibault@eu.citrix.com \
    --cc=sandesh.ahiremath@wipro.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.