linux-kernel - 答复: 答复: [PATCH 1/2] x86/mce: new centaur CPUs support MCE broadcasting

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 for Android: free password hash cracker in your pocket

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

Date:   Sun, 8 Apr 2018 10:18:05 +0800
From:   David Wang <davidwang@...oxin.com>
To:     'Borislav Petkov' <bp@...en8.de>
CC:     <tony.luck@...el.com>, <tglx@...utronix.de>, <mingo@...hat.com>,
        <hpa@...or.com>, <x86@...nel.org>, <linux-edac@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>,
        "'Bruce Chang (VAS)'" <BruceChang@...-alliance.com>,
        "'Cooper Yan(BJ-RD)'" <CooperYan@...oxin.com>,
        "'Qiyuan Wang(BJ-RD)'" <QiyuanWang@...oxin.com>,
        'Benjamin Pan' <BenjaminPan@...tech.com>,
        'Luke Lin' <LukeLin@...cpu.com>,
        "'Tim Guo(BJ-RD)'" <TimGuo@...oxin.com>
Subject: 答复: 答复: [PATCH 1/2] x86/mce: new centaur CPUs support MCE broadcasting

> -----邮件原件-----
> 发件人: Borislav Petkov [mailto:bp@...en8.de]
> 发送时间: 2018年4月4日 19:18
> 收件人: David Wang <DavidWang@...oxin.com>
> 抄送: tony.luck@...el.com; tglx@...utronix.de; mingo@...hat.com;
> hpa@...or.com; x86@...nel.org; linux-edac@...r.kernel.org;
> linux-kernel@...r.kernel.org; Bruce Chang (VAS)
> <BruceChang@...-alliance.com>; Cooper Yan(BJ-RD)
> <CooperYan@...oxin.com>; Qiyuan Wang(BJ-RD)
> <QiyuanWang@...oxin.com>; Benjamin Pan <BenjaminPan@...tech.com>;
> Luke Lin <LukeLin@...cpu.com>; Tim Guo(BJ-RD) <TimGuo@...oxin.com>
> 主题: Re: 答复: [PATCH 1/2] x86/mce: new centaur CPUs support MCE
> broadcasting
> 
> On Wed, Apr 04, 2018 at 02:34:52AM +0000, David Wang wrote:
> > Those are new processors and main usage of CentaurHauls CPUs in recent
> > years is for limited and/or embedded instead of distribution markets.
> > So there is no plan or resource to create such document for public
> > access. Is public spec mandatory for code check-in? We can provide
> > platforms for verification instead.
> 
> Nah, not needed. As long as the code paths don't break anything else and as
> long as we can CC you to fix bugs people report, we're good. :-)
> 
> Btw, please do not top-post on a public ML.

I got it.
Thanks.

---
David

> 
> Thx.
> 
> --
> Regards/Gruss,
>     Boris.
> 
> Good mailing practices for 400: avoid top-posting and trim the reply.