public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: FabF <fabian.frederick@skynet.be>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.7-mm3] cpuflags reviewed
Date: Tue, 29 Jun 2004 01:37:23 +0100	[thread overview]
Message-ID: <20040629003723.GA30230@redhat.com> (raw)
In-Reply-To: <1088416506.2395.9.camel@localhost.localdomain>

On Mon, Jun 28, 2004 at 11:55:06AM +0200, FabF wrote:
 > Andrew,
 > 
 > 	Here's cpuflags v2 (x86 version) :
 > 
 > [/proc/cpuflags snippet]
 > no  sse2
 > no  ss
 > no  ht
 > no  tm
 > no  ia64
 > no  pbe
 > yes syscall
 > yes mp
 > no  nx
 > yes mmxext
 > no  lm
 > yes 3dnowext

This can be done just as easily (if not easier) in userspace.
I see no value in adding a duplicate flag mechanism to the kernel.

		Dave


  reply	other threads:[~2004-06-29  0:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28  9:55 [PATCH 2.6.7-mm3] cpuflags reviewed FabF
2004-06-29  0:37 ` Dave Jones [this message]
     [not found] <200406290842.i5T8g42d030759@outmx008.isp.belgacom.be>
2004-06-29 15:11 ` Dave Jones

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=20040629003723.GA30230@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=fabian.frederick@skynet.be \
    --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