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 20:00:11 +0900 [thread overview]
Message-ID: <9cde8bff0506070400708ee85@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D2820D9@liverpoolst.ad.cl.cam.ac.uk>
On 6/7/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > 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)
>
> Xen supports hyperthreading just fine, and even does initial domain
> placement using an algorithm that understands it.
>
> In fact, it looks like we effectively lost the option to ever disable
> hyperthreading when the setup code got upgraded.
can you confirm that ht_per_core is also wrongly set? it is set (=1)
at arch/x86/setup.c or arch/ia64/smpboot.c, but never changed. but
this variable is used somewhere, and got reported in "xm info", for
example.
so all of its usage are also wrong when we use HT? (because in that
case ht_per_core must be 2)
>It would be nice if
> part of your patch removed any reference to 'noht', including in the
> documentation.
fine, i will submit a patch on this problem.
regards,
aq
next prev parent reply other threads:[~2005-06-07 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 10:48 [PATCH] xm --version Ian Pratt
2005-06-07 11:00 ` 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-06 8:14 Ian Pratt
2005-06-07 10:22 ` 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=9cde8bff0506070400708ee85@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.