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: <a44ae5cd1001061006i63579096me4d598b06cc358f9@mail.gmail.com>
Date:	Wed, 6 Jan 2010 13:06:46 -0500
From:	Miles Lane <miles.lane@...il.com>
To:	Bruno Prémont <bonbons@...ux-vserver.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	David Airlie <airlied@...ux.ie>,
	Sylvain Meyer <sylvain.meyer@...ldonline.fr>,
	linux-fbdev@...r.kernel.org
Subject: Re: 2.6.33-rc3 -- Intel 945GME (inteldrmfb) -- Two Tux images 
	displayed are side by side (should only show one).

On Wed, Jan 6, 2010 at 12:59 PM, Bruno Prémont
<bonbons@...ux-vserver.org> wrote:
> On Wed, 06 January 2010 Miles Lane <miles.lane@...il.com> wrote:
>> For a long time I have gotten two pictures of Tux showing up when I
>> include the Tux display option in my custom kernel builds.  I don't
>> know how many kernel revisions ago it was when I started noticing
>> this.  It seems like it might have been early in the 2.6 series
>> kernels.
>
> Unless your system has exactly one CPU without hyperthreading and with
> exactly one core this is the correct bahavior, one tux per logical CPU.
>
> If you just want a single tux you can run your kernel on a system with
> only one logical CPU, boot it with maxcpus=1 or rebuild it with
> CONFIG_SMP=n... though in those case you will not be able to benefit
> from all of your CPU's resources..
>
> Bruno

Oh!  Well, that explains it.  That is truly weird functionality.  Is
Tux a de facto
CPU presence indicator?  It doesn't make any sense to me, if so.

         Miles
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ