public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: test11-pre5 breaks vmware
Date: 15 Nov 2000 12:12:15 -0800	[thread overview]
Message-ID: <8uuqmv$el4$1@cesium.transmeta.com> (raw)
In-Reply-To: <CF021B54DF0@vcnet.vc.cvut.cz> <Pine.LNX.4.21.0011151454590.10690-100000@godzilla.spiteful.org>

Followup to:  <Pine.LNX.4.21.0011151454590.10690-100000@godzilla.spiteful.org>
By author:    Scott Murray <scott@spiteful.org>
In newsgroup: linux.dev.kernel
> > 
> > Oh. I did not compiled 11-test5, as G450 finally arrived ;-) OK,
> > I'll release patch for vmware, as I cannot stop kernel developers
> > from changing field names :-)
> 
> Actually, I know of at least one other shipping commercial product
> (Sitraka's JProbe Java Profiler) that will require patching because of
> this change.  It seems unwise to be changing field names in commonly
> used /proc files like cpuinfo at this point in time.
> 

The problem with "flags" is that it no longer contains quite the same
information.  Since the semantics of the field changed slightly,
changing the field name is sometimes more correct.

Also, if a piece of software needs raw CPUID information (unlike the
"cooked" one provided by recent kernels) it should use
/dev/cpu/*/cpuid.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-15 20:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15 17:47 test11-pre5 breaks vmware Petr Vandrovec
2000-11-15 20:05 ` Scott Murray
2000-11-15 20:12   ` H. Peter Anvin [this message]
2000-11-15 20:49     ` Michel LESPINASSE
2000-11-15 20:50       ` H. Peter Anvin
2000-11-16  0:29     ` Albert D. Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2000-11-15 22:39 Petr Vandrovec
2000-11-15 17:57 Petr Vandrovec
2000-11-14 12:47 More modutils: It's probably worse Petr Vandrovec
2000-11-15  1:59 ` test11-pre5 breaks vmware Tigran Aivazian

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='8uuqmv$el4$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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