mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: akpm@osdl.org, "Dave Jones" <davej@redhat.com>,
	zwane@holomorphy.com, "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, zach@vmware.com
Subject: Re: x86-fix-cmpxchg.patch added to -mm tree
Date: Mon, 12 Sep 2005 10:23:20 +0300	[thread overview]
Message-ID: <200509121023.20520.vda@ilport.com.ua> (raw)
In-Reply-To: <43253F2E0200007800024DD4@sinclair.provo.novell.com>

On Monday 12 September 2005 09:41, Jan Beulich wrote:
> >>> Dave Jones <davej@redhat.com> 10.09.05 02:30:38 >>>
> >On Fri, Sep 09, 2005 at 05:06:56PM -0700, Andrew Morton wrote:
> >
> > > - cmpxchg8b gets disabled when the minimum specified hardware
> architectur
> > >   doesn't support it (like was already happening for the byte,
> word, and
> > >   long ones).
> > >
> > > +config X86_CMPXCHG64
> > > +	bool
> > > +	depends on !M386 && !M486 && !MCYRIXIII && !MGEODEGX1
> > > +	default y
> >
> >This is wrong.  All the Winchip/CyrixIII CPUs do indeed have cx8.
> >Though cpuid will report that it's missing until We explicitly enable
> >it in init_c3().  Whilst it's "disabled" however, the instruction does
> >run perfectly fine.   This was done because Win NT wouldn't boot if it
> >found a non Intel CPU which had cx8 iirc.

Can this be added to comments in the right place?

> >I'm not familiar with the Geode enough to answer definitively.
> >Alan seems to be the Geode-guru, and may still have datasheets for
> that.
> 
> Resubmitting adjusted patch (taking into account also Alan's later
> response).
--
vda

      reply	other threads:[~2005-09-12  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200509100006.j8A06rZm020089@shell0.pdx.osdl.net>
     [not found] ` <20050910003038.GH5283@redhat.com>
2005-09-12  6:41   ` Jan Beulich
2005-09-12  7:23     ` Denis Vlasenko [this message]

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=200509121023.20520.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=JBeulich@novell.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zach@vmware.com \
    --cc=zwane@holomorphy.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

all inboxes | Powered by JetHome®