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:08:30 +0100 [thread overview]
Message-ID: <20080721170830.GG4501@implementation.uk.xensource.com> (raw)
In-Reply-To: <1216660393.17572.30.camel@ec4t16cg-1518809>
Sandesh, le Mon 21 Jul 2008 22:43:13 +0530, a écrit :
> > > Once the domU is running how can i change them?
> >
> > What for?
> basically right after shutdown with poweroff = 'preserve' option i want
> to reboot the domU without having to going through the whole domain
> building process. So i need to load the different domU segments again,
> or at least the pt_base mapping.
Well the problem is that the domU most probably has destroyed it
completely already.
> > > like how will i know which entries in the dom0 pgtables corresponds to
> > > kernel_seg or ramdisk_seg and so on..
> >
> > 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?
Yes. No need for anybody else to access it (except PV interfaces, but
then the MFNs or grants are explicitely given by the domU).
Samuel
next prev parent reply other threads:[~2008-07-21 17:08 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 [this message]
2008-07-21 17:36 ` Sandesh
2008-07-21 17:36 ` Samuel Thibault
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=20080721170830.GG4501@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.