linux-kernel - 答复: [tip:x86/cpu] x86/cpu: Create Zhaoxin processors architecture support file

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: <505e342c814e4b29ae2a23a6eaf63ea7@zhaoxin.com>
Date:   Tue, 25 Jun 2019 06:19:15 +0000
From:   Tony W Wang-oc <TonyWWang-oc@...oxin.com>
To:     Joe Perches <joe@...ches.com>,
        "Herry Yang(BJ-RD)" <HerryYang@...oxin.com>,
        "Cooper Yan(BJ-RD)" <CooperYan@...oxin.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "hpa@...or.com" <hpa@...or.com>,
        "lenb@...nel.org" <lenb@...nel.org>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "Qiyuan Wang(BJ-RD)" <QiyuanWang@...oxin.com>,
        "mingo@...nel.org" <mingo@...nel.org>,
        David Wang <DavidWang@...oxin.com>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "rjw@...ysocki.net" <rjw@...ysocki.net>,
        "linux-tip-commits@...r.kernel.org" 
        <linux-tip-commits@...r.kernel.org>
Subject: 答复: [tip:x86/cpu] x86/cpu: Create Zhaoxin processors architecture support file

On Sun, Jun 23, 2019, Joe Perches wrote:
> > x86/cpu: Create Zhaoxin processors architecture support file
> >
> []
> > diff --git a/arch/x86/kernel/cpu/zhaoxin.c b/arch/x86/kernel/cpu/zhaoxin.c
> []
> > +static void init_zhaoxin_cap(struct cpuinfo_x86 *c)
> > +{
> > +	u32  lo, hi;
> > +
> > +	/* Test for Extended Feature Flags presence */
> > +	if (cpuid_eax(0xC0000000) >= 0xC0000001) {
> > +		u32 tmp = cpuid_edx(0xC0000001);
> > +
> > +		/* Enable ACE unit, if present and disabled */
> > +		if ((tmp & (ACE_PRESENT | ACE_ENABLED)) == ACE_PRESENT) {
> 
> trivia:
> 
> Perhaps this is more intelligible for humans to read
> and it deduplicates the comment as:
> 
> 		if ((tmp & ACE_PRESENT) && !(tmp & ACE_ENABLED))
> 
> The compiler produces the same object code.
> 

Thanks for the trivia, I will change this in the next version patch set.

Thanks
TonyWWang-oc