linux-kernel - Re: [PATCH -v1.1] x86, boot: Further compress CPUs bootup message

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]

Date:	Sun, 29 Sep 2013 08:44:56 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>
CC:	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	huawei.libin@...wei.com, wangyijing@...wei.com,
	fenghua.yu@...el.com, tglx@...utronix.de, guohanjun@...wei.com,
	paul.gortmaker@...driver.com, linux-tip-commits@...r.kernel.org
Subject: Re: [PATCH -v1.1] x86, boot: Further compress CPUs bootup message

If the goal is to feed this to the field width in printf, which I would think would be the dominant use, then you do have to account for the minus sign.

Borislav Petkov <bp@...en8.de> wrote:
>On Sat, Sep 28, 2013 at 04:13:29PM -0700, H. Peter Anvin wrote:
>> For negative numbers presumably we need to d++ for the minus sign,
>no?
>
>That's easy - the function is called num_digits, so we count only
>digits.
>
>The real question is, is there a use case where we would need to count
>the sign too or only the digits?
>
>And since I can't be clairvoyant, I'll leave it to future generations
>to
>decide what to do with the sign.
>
>:-)

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.
--
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/