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: "aq" <aquynh@xxxxxxxxx>, "Xen Dev" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] xm --version
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 6 Jun 2005 08:22:52 +0100
Delivery-date: Mon, 06 Jun 2005 07:22:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVqS5bEMzNOKhsCRJKmt0TF0jEkOAAG6jww
Thread-topic: [Xen-devel] [PATCH] xm --version
> 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? 

Also, isn't there a tools version field we could print as well?

> 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
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.


> cpu_mhz                : 1094
> memory                 : 511
> free_memory            : 122

Xen-devel mailing list