This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] xm --version

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xm --version
From: aq <aquynh@xxxxxxxxx>
Date: Mon, 6 Jun 2005 16:47:14 +0900
Cc: Xen Dev <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 06 Jun 2005 07:47:27 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p9y2ju+tmOM66RJSHrRHCSW0o3ppKxi/gcllA86HCjNW+vBxZV8Wa6uoXw3AALo4iaJYpLgAfcy9RcSsgljXb4v5bXrYwHKOTSp44svi8ZHpN/qJnhASkp1PabZmfQ8z06u9+RIDX6mC6lnQafyxsUWz4G3Lr+f7PJ/YbWVqpQQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282080@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D282080@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 6/6/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> > This patch adds to xm a long-missing function: showing xen
> > version and few extra information (thanks go to Keir and Mark
> > for some suggestions). Here is the ouput of "xm info" after
> > applying the patch (against -unstable ChangeSet@xxxxxx):
> Thanks, but I'd like to make another couple of suggestions:
> > ---
> > #xm info
> > system                 : Linux
> > host                   : ubuntu
> > xen_release            : 3.0-devel
> > xen_compile_by         : root@localdomain
> > xen_compiler           : gcc version 3.3.5 (Debian 1:3.3.5-8ubuntu2)
> > xen_compile_date       : Mon Jun  6 00:30:22 EST 2005
> > dom0_release           :
> > dom0_version           : #3 Mon Jun 6 00:32:05 EST 2005
> > machine                : i686
> Where does 'machine' come from? Shouldn't it be x86_32?

this is not what the patch does, but in the original code. actually
"machine" is from "uname" syscall, run in dom0. libxc just gets the
result from "uname", together with dom0_release, dom0_version.

should we fix it to x86_32 or x86_64?

> Also, isn't there a tools version field we could print as well?
yes, that is fine, but where to get the xm version? lets put it
somewhere into xm code? i am not sure where to put it. and actually
what is the current version of xm? we better ask Mike to help this

> > cores                  : 1
> > hyperthreads_per_core  : 1
> I'd like to add a bit more information here, to take of ccNUMA systems
> with multicore and hyperthreadsing, e.g. for a system with 2 dual core
> hyperthreaded Xeons:
> logical_cpus            : 8

sorry for my ignorance (never play with 2 or more cpus system before,
poor me!), how come 2 dual core hyperthreaded Xeons has "8 logical
cpus"? you must meant "4 logical cpus"

> hyperthreads_per_core   : 2
> cores_per_socket                : 2
> sockets_per_node                : 2
> nodes                           : 1
> This information should reflect the running system, rather than the
> capabilities of the hardware. i.e. if someone has booted with 'noht'
> then hyperthreads_per_core should be 1 regardless of the hardware. This
> will clean up some other code in Xen that uses the flag.

i see, but how about applying this patch now, and solve what you
propose above later? i will investigate this problem.


Xen-devel mailing list