From: jd <jdsw2002@yahoo.com>
To: Keir Fraser <keir@xensource.com>,
Ian Campbell <Ian.Campbell@XenSource.com>
Cc: xendevel <xen-devel@lists.xensource.com>, jd <jdsw2002@yahoo.com>
Subject: Re: determining if kernel is dom0 kernel or not.
Date: Wed, 11 Jul 2007 15:04:17 -0700 (PDT) [thread overview]
Message-ID: <785281.94335.qm@web35804.mail.mud.yahoo.com> (raw)
In-Reply-To: <C2BB0C95.AA8F%keir@xensource.com>
Cool. This is what I was looking for.
Optional :
Any history behind it containing 'control_d' ?
Control Dom ?
Thanks
/Jd
--- Keir Fraser <keir@xensource.com> wrote:
> On 11/7/07 21:38, "Ian Campbell"
> <Ian.Campbell@XenSource.com> wrote:
>
> > On Wed, 2007-07-11 at 20:18 +0100, Keir Fraser
> wrote:
> >> If you want to detect dom0 specifically then
> that's trickier --
> >> /proc/xen/privcmd for example exists even in a
> domU, if the kernel is
> >> dom0-capable. You'd have to be root and then try
> a privileged hypercall. :-)
> >
> > Doesn't /proc/xen/capabilities contain something
> different on dom0 vs.
> > domU?
>
> Oh yes, of course. It contains 'control_d' if you
> are dom0.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
next prev parent reply other threads:[~2007-07-11 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 18:40 determining if kernel is dom0 kernel or not jd
2007-07-11 19:18 ` Keir Fraser
2007-07-11 20:38 ` Ian Campbell
2007-07-11 21:39 ` Keir Fraser
2007-07-11 22:04 ` jd [this message]
2007-07-12 13:35 ` Mark Williamson
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=785281.94335.qm@web35804.mail.mud.yahoo.com \
--to=jdsw2002@yahoo.com \
--cc=Ian.Campbell@XenSource.com \
--cc=keir@xensource.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.