mbox series

[0/3] x86: Add support for Zhaoxin processors

Message ID 1575862175-5044-1-git-send-email-MayShao@zhaoxin.com
Headers show
Series x86: Add support for Zhaoxin processors | expand

Message

May Shao(BJ-RD) Dec. 9, 2019, 3:29 a.m. UTC
This patch series fix Shanghai Zhaoxin processor CPU Vendor ID detection
problem in glibc sysdep module. Current glibc doesn't recognize Zhaoxin
CPU Vendor ID("CentaurHauls" and "Shanghai") and set kind to
arch_kind_other. These lead to incorrect result of __cache_sysconf(),
incorrect value for variables like __x86_shared_cache_size, and fail
of test case tst-get-cpu-features.

Background:
Shanghai Zhaoxin Semiconductor Co., Ltd("Zhaoxin"), established in 2013,
headquartered in Zhangjiang, Shanghai, China. Zhaoxin aims at providing
general-purpose x86 processors.

Related Zhaoxin Linux Kernel patch can be found at
https://lore.kernel.org/lkml/01042674b2f741b2aed1f797359bdffb@zhaoxin.com

MayShao (3):
  x86: Add CPU Vendor ID detection support for Zhaoxin processors
  x86: Add cache information support for Zhaoxin processors
  x86: Add the test case of __get_cpu_features support for Zhaoxin
    processors

 sysdeps/x86/cacheinfo.c            | 183 +++++++++++++++++++++++++++++++++++++
 sysdeps/x86/cpu-features.c         |  59 ++++++++++++
 sysdeps/x86/cpu-features.h         |   1 +
 sysdeps/x86/tst-get-cpu-features.c |   2 +
 4 files changed, 245 insertions(+)

--
2.7.4



保密声明:
本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.

Comments

Carlos O'Donell Dec. 9, 2019, 12:35 p.m. UTC | #1
On 12/8/19 10:29 PM, MayShao wrote:
> This patch series fix Shanghai Zhaoxin processor CPU Vendor ID detection
> problem in glibc sysdep module. Current glibc doesn't recognize Zhaoxin
> CPU Vendor ID("CentaurHauls" and "Shanghai") and set kind to
> arch_kind_other. These lead to incorrect result of __cache_sysconf(),
> incorrect value for variables like __x86_shared_cache_size, and fail
> of test case tst-get-cpu-features.
> 
> Background:
> Shanghai Zhaoxin Semiconductor Co., Ltd("Zhaoxin"), established in 2013,
> headquartered in Zhangjiang, Shanghai, China. Zhaoxin aims at providing
> general-purpose x86 processors.
What is the status of Zhaoxin's or your copyright assignment to the FSF?

Contributions to the glibc project require copyright assignment to the FSF.

Please see our contribution checklist:
https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment

You will need a corporate assignment, your employer will have to sign the
assignment paperwork.

I suggest you start by following this process:
http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future

And answering the question "Do you have an employer who might have a basis 
to claim to own your changes?" is the most important question, since it
starts the process of corporate copyright assignment.
May Shao(BJ-RD) Dec. 10, 2019, 7:22 a.m. UTC | #2
On 12/9/19 8:36 PM Carlos O'Donell wrote:
> On 12/8/19 10:29 PM, MayShao wrote:
> > This patch series fix Shanghai Zhaoxin processor CPU Vendor ID detection
> > problem in glibc sysdep module. Current glibc doesn't recognize Zhaoxin
> > CPU Vendor ID("CentaurHauls" and "Shanghai") and set kind to
> > arch_kind_other. These lead to incorrect result of __cache_sysconf(),
> > incorrect value for variables like __x86_shared_cache_size, and fail
> > of test case tst-get-cpu-features.
> >
> > Background:
> > Shanghai Zhaoxin Semiconductor Co., Ltd("Zhaoxin"), established in 2013,
> > headquartered in Zhangjiang, Shanghai, China. Zhaoxin aims at providing
> > general-purpose x86 processors.
> What is the status of Zhaoxin's or your copyright assignment to the FSF?
>
> Contributions to the glibc project require copyright assignment to the FSF.
>
> Please see our contribution checklist:
> https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_As
> signment
>
> You will need a corporate assignment, your employer will have to sign the
> assignment paperwork.
>
> I suggest you start by following this process:
> http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign
> .future
>
> And answering the question "Do you have an employer who might have a basis
> to claim to own your changes?" is the most important question, since it
> starts the process of corporate copyright assignment.
>
> --
> Cheers,
> Carlos.


Thank you for your reply and reminder.

I have just completed the above form and sent it to assign@gnu.org




保密声明:
本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.
Carlos O'Donell Dec. 10, 2019, 8 p.m. UTC | #3
On 12/10/19 2:22 AM, May Shao(BJ-RD) wrote:
> On 12/9/19 8:36 PM Carlos O'Donell wrote:
>> And answering the question "Do you have an employer who might have a basis
>> to claim to own your changes?" is the most important question, since it
>> starts the process of corporate copyright assignment.

> Thank you for your reply and reminder.
> 
> I have just completed the above form and sent it to assign@gnu.org

Thank you very much! I look forward to reviewing your patches! :-)