From: aq <aquynh@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Xen Dev <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xm --version
Date: Tue, 7 Jun 2005 19:22:25 +0900 [thread overview]
Message-ID: <9cde8bff0506070322977620@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282081@liverpoolst.ad.cl.cam.ac.uk>
On 6/6/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > > 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?
>
> Ideally the architecture should come from Xen rather than the dom0
> kernel, but I guess this isn't a big deal right now since we don't
> support running 32 bit paravirt guests on a 64 bit hypervisor, and even
> if we did you probably wouldn't want to do it for dom0.
>
> > >
> > > 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 problem?
>
> I guess its more interesting to know the xend or libxc version, but I
> guess we can assume them to all come from the same package/rpm. We
> probably need to add a version identifier to the tools.
>
> > > > 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"
>
> 2 sockets * 2 cores * 2 hyperthreads = 8 logical CPUs.
>
> Xen doesn't currently distinguish between sockets and cores, so for the
> moment the interface should just return 'sockets_per_node = 4'. We can
> fix Xen up later.
>
Ian, i look at the xen source code, and looks like "noht" option is
never used anywhere? also ht_per_core is always set to 1? does xen
really support HyperThreading now ? (i doubt that)
regards,
aq
next prev parent reply other threads:[~2005-06-07 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 8:14 [PATCH] xm --version Ian Pratt
2005-06-07 10:22 ` aq [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-09 1:18 Ian Pratt
2005-06-09 8:57 ` aq
2005-06-07 10:48 Ian Pratt
2005-06-07 11:00 ` aq
2005-06-06 7:22 Ian Pratt
2005-06-06 7:47 ` aq
2005-06-06 8:10 ` Keir Fraser
2005-06-06 3:54 aq
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=9cde8bff0506070322977620@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.