linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Eckenfels <be-mail2007@lina.inka.de>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: ht CPU flag
Date: Fri, 18 May 2007 21:45:54 +0200	[thread overview]
Message-ID: <20070518194554.GA8088@lina.inka.de> (raw)
In-Reply-To: <20070518190709.GB28957@linux-os.sc.intel.com>

On Fri, May 18, 2007 at 12:07:09PM -0700, Siddha, Suresh B wrote:
> On Fri, May 18, 2007 at 11:45:59AM -0700, H. Peter Anvin wrote:
> > IIRC, the HT flag is also reported for multicore CPUs.
> 
> Yes. Thats correct.

And for some Single-Core Non-HT CPUs.

Gruss
Bernd
-- 
  (OO)     -- Bernd_Eckenfels@Mörscher_Strasse_8.76185Karlsruhe.de --
 ( .. )    ecki@{inka.de,linux.de,debian.org}  http://www.eckes.org/
  o--o   1024D/E383CD7E  eckes@IRCNet  v:+497211603874  f:+49721151516129
(O____O)  When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!

  reply	other threads:[~2007-05-18 19:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 16:47 ht CPU flag eugene
2007-05-18 17:54 ` Bernd Eckenfels
2007-05-18 18:45   ` H. Peter Anvin
2007-05-18 19:07     ` Siddha, Suresh B
2007-05-18 19:45       ` Bernd Eckenfels [this message]
2007-05-18 19:17 ` Chris Snook
2007-05-18 19:33   ` eugene
2007-05-18 19:51     ` Chris Snook
2007-05-19  5:18       ` eugene
2007-05-19  6:18         ` H. Peter Anvin
2007-05-19  8:33           ` eugene
2007-05-19 16:38             ` Bernd Eckenfels
2007-05-19 18:11             ` H. Peter Anvin
2007-05-19 12:13           ` eugene
2007-05-19 16:41             ` Bernd Eckenfels
2007-05-18 20:32     ` Bernd Eckenfels
2007-05-18 23:20       ` H. Peter Anvin
2007-05-19 21:07       ` eugene

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=20070518194554.GA8088@lina.inka.de \
    --to=be-mail2007@lina.inka.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).