linux-kernel - Re: [PATCH v2 01/11] msm: Add CPU queries

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1295983549.25496.33.camel@c-dwalke-linux.qualcomm.com>
Date:	Tue, 25 Jan 2011 11:25:49 -0800
From:	Daniel Walker <dwalker@...eaurora.org>
To:	David Brown <davidb@...eaurora.org>
Cc:	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 01/11] msm: Add CPU queries

On Tue, 2011-01-25 at 11:17 -0800, David Brown wrote:
> On Tue, Jan 25 2011, Daniel Walker wrote:
> 
> > On Mon, 2011-01-24 at 16:57 -0800, David Brown wrote:
> >> MSM7201 and MSM7601 are identical as far as Linux is concerned.  Same
> >> goes for MSM8250 and MSM8650.  Our dev boards are a somewhat random mix
> >> of the two, and it doesn't matter which one you use.
> >> 
> >> MSM8960 is a completely different chip, it just shares a similar name,
> >> to other chips.
> >
> > If you break it down without the "x" then you can recreate the "x"
> > variant with the actual numerical identifier .. For 8660/8960 you just
> > would do as much of a unification as with the others.. You could still
> > use 8x60 to identify those two, you just wouldn't use it as often.
> 
> There isn't any unification to do here.  There are two issues.  We make
> some chips in groups where we have _identical_ silicon on the Linux
> side, but happen to have different numbers.  That's what the X is
> about.  There are other cases where we have completely different silicon
> that happen to have similar numbers.
> 
> The whole point of the cpu_is tests is to tell us exactly which chip we
> are on.  If there is _anything_ different between two chips, that query
> needs to be different.  If there is any kind of unification, it can be
> done at a higher level.  Otherwise, you have no way of making the
> distinction that needs to be made.

I suggesting we do it across the board because consistency is a good
thing .. It also allows us to use 8x60 when 8660 and 8960 are actually
similar .. You can't deny that 8960 is similar to 8660 because your
patches show some duplication due to it.

Daniel


-- 

Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/