All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: xen-devel@lists.xensource.com, Ewan Mellor <ewan@xensource.com>,
	"Andrew D. Ball" <aball@linux.vnet.ibm.com>
Cc: Akio Takebe <takebe_akio@jp.fujitsu.com>
Subject: Re: [RFC] Is this process running on which machine?
Date: Tue, 28 Nov 2006 13:00:14 +0900	[thread overview]
Message-ID: <2C712A1B5A045takebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <F2C711DDF97053takebe_akio@jp.fujitsu.com>

Hi,

I remake it again.
I tested native, dom0, domU, domVTx on x86.
If you have comments, please give me.

----------------------------------------------------------
#!/bin/bash
declare -i IS_HVM=0
declare -i IS_PARA=0

check_hvm()
{
        IS_X86HVM="$(strings /proc/acpi/dsdt | grep int-xen)"
        if [ x"${IS_X86HVM}" != x ]; then
                echo "x86hvm"
                IS_HVM=1
        fi
}

check_para()
{
        if $(grep -q control_d /proc/xen/capabilities); then
                echo "dom0"
                IS_PARA=1
        else
                echo "domU"
                IS_PARA=1
        fi
}

#### main ####
if [ -f /proc/acpi/dsdt ]; then 
        check_hvm
fi
if [ ${IS_HVM} -eq 0 ]; then
        if [ -f /proc/xen/capabilities ] ; then
                check_para
        fi
fi
if [ ${IS_HVM} -eq 0 -a ${IS_PARA} -eq 0 ]; then
        echo "native"
fi
----------------------------------------------------------

Best Regards,

Akio Takebe

      reply	other threads:[~2006-11-28  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18  9:10 [RFC] Is this process running on which machine? Akio Takebe
2006-11-18 13:53 ` Ewan Mellor
2006-11-20  1:57   ` Akio Takebe
2006-11-20  3:37     ` Akio Takebe
2006-11-21  3:03       ` Andrew D. Ball
2006-11-21  8:52         ` Akio Takebe
2006-11-27  4:39           ` Akio Takebe
2006-11-28  4:00             ` Akio Takebe [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=2C712A1B5A045takebe_akio@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=aball@linux.vnet.ibm.com \
    --cc=ewan@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.