March 2020 - Tc - mailweb.openeuler.org

Re: [PATCH 00/22] Add support for Hygon Dhyana Family 18h processor
by Hanjun Guo 18 Apr '20

18 Apr '20

Hi Pu Wen, On 2020/3/31 11:20, Pu Wen wrote: > As a new x86 CPU Vendor, Chengdu Haiguang IC Design Co., Ltd (Hygon) > is a Joint Venture between AMD and Haiguang Information Technology Co., > Ltd., and aims at providing high performance x86 processor for China > server market. > > The first generation Hygon's processor(Dhyana) originates from AMD > technology and shares most of the architecture with AMD's family 17h, > but with different CPU Vendor ID("HygonGenuine")/PCIE Device Vendor ID > (0x1D94)/Family series number (Family 18h). > > To enable the support of Linux kernel to Hygon's CPU, we added a new > vendor type (X86_VENDOR_HYGON, with value of 9) in arch/x86/include/ > asm/processor.h, and shared most of kernel support codes with AMD > family 17h. > > As Hygon will negotiate with AMD to make sure that only Hygon will > use family 18h, so try to minimize code modification and share most > codes with AMD under this consideration. > > This patch series have been applied and tested successfully on Hygon > Dhyana SoC silicon. Also tested on AMD EPYC (Family 17h) processor, > it works fine and makes no harm to the existing codes. > > This patch series are created for the current branch openEuler-1.0-LTS. Thanks a lot for your patchset, I took a detail look at this patchset, and it looks good to me, I'm pretty happy that this patchset was backported from mainline kernel and you are the maintainer. For this patchset, Reviewed-by: Hanjun Guo <guohanjun(a)huawei.com> BTW, do we need updates for compiler, glibc and other usersapce package to recognize Hygon processor or performance optimization? if yes, you can send those patches to openEuler as well. And I kindly invite you to create a new SIG for Hygon processor in openEuler [1]. Thanks Hanjun [1]: https://openeuler.org/zh/sig.html > > References: > [1] Linux kernel patches for Hygon Dhyana, merged in 4.20: > https://git.kernel.org/tip/c9661c1e80b609cd038db7c908e061f0535804ef > [2] MSR and CPUID definition: > https://www.amd.com/system/files/TechDocs/54945_PPR_Family_17h_Models_00h-0… > > Pu Wen (22): > x86/cpu: Create Hygon Dhyana architecture support file > x86/cpu: Get cache info and setup cache cpumap for Hygon Dhyana > x86/cpu/mtrr: Support TOP_MEM2 and get MTRR number > x86/smpboot: Do not use BSP INIT delay and MWAIT to idle on Dhyana > x86/events: Add Hygon Dhyana support to PMU infrastructure > x86/alternative: Init ideal_nops for Hygon Dhyana > x86/amd_nb: Check vendor in AMD-only functions > x86/pci, x86/amd_nb: Add Hygon Dhyana support to PCI and northbridge > x86/apic: Add Hygon Dhyana support > x86/bugs: Add Hygon Dhyana to the respective mitigation machinery > x86/mce: Add Hygon Dhyana support to the MCA infrastructure > x86/kvm: Add Hygon Dhyana support to KVM > x86/xen: Add Hygon Dhyana support to Xen > ACPI: Add Hygon Dhyana support > cpufreq: Add Hygon Dhyana support > EDAC, amd64: Add Hygon Dhyana support > tools/cpupower: Add Hygon Dhyana support > hwmon: (k10temp) Add Hygon Dhyana support > x86/CPU/hygon: Fix phys_proc_id calculation logic for multi-die > processors > i2c-piix4: Add Hygon Dhyana SMBus support > x86/amd_nb: Make hygon_nb_misc_ids static > NTB: Add Hygon Device ID > > Documentation/i2c/busses/i2c-piix4 | 2 + > MAINTAINERS | 6 + > arch/x86/Kconfig.cpu | 14 + > arch/x86/events/amd/core.c | 4 + > arch/x86/events/amd/uncore.c | 20 +- > arch/x86/events/core.c | 4 + > arch/x86/include/asm/amd_nb.h | 3 + > arch/x86/include/asm/cacheinfo.h | 1 + > arch/x86/include/asm/kvm_emulate.h | 4 + > arch/x86/include/asm/mce.h | 2 + > arch/x86/include/asm/processor.h | 3 +- > arch/x86/include/asm/virtext.h | 5 +- > arch/x86/kernel/alternative.c | 4 + > arch/x86/kernel/amd_nb.c | 49 ++- > arch/x86/kernel/apic/apic.c | 7 + > arch/x86/kernel/apic/probe_32.c | 1 + > arch/x86/kernel/cpu/Makefile | 1 + > arch/x86/kernel/cpu/bugs.c | 4 +- > arch/x86/kernel/cpu/cacheinfo.c | 31 +- > arch/x86/kernel/cpu/common.c | 4 + > arch/x86/kernel/cpu/cpu.h | 1 + > arch/x86/kernel/cpu/hygon.c | 413 ++++++++++++++++++ > arch/x86/kernel/cpu/mce/core.c | 20 +- > arch/x86/kernel/cpu/mce/severity.c | 3 +- > arch/x86/kernel/cpu/mtrr/cleanup.c | 3 +- > arch/x86/kernel/cpu/mtrr/mtrr.c | 2 +- > arch/x86/kernel/cpu/perfctr-watchdog.c | 2 + > arch/x86/kernel/smpboot.c | 4 +- > arch/x86/kvm/emulate.c | 11 +- > arch/x86/pci/amd_bus.c | 6 +- > arch/x86/xen/pmu.c | 12 +- > drivers/acpi/acpi_pad.c | 1 + > drivers/acpi/processor_idle.c | 1 + > drivers/cpufreq/acpi-cpufreq.c | 5 + > drivers/cpufreq/amd_freq_sensitivity.c | 9 +- > drivers/edac/amd64_edac.c | 10 +- > drivers/edac/mce_amd.c | 4 +- > drivers/hwmon/k10temp.c | 3 +- > drivers/i2c/busses/Kconfig | 1 + > drivers/i2c/busses/i2c-piix4.c | 15 +- > drivers/ntb/hw/amd/ntb_hw_amd.c | 1 + > include/linux/pci_ids.h | 2 + > tools/power/cpupower/utils/cpufreq-info.c | 6 +- > tools/power/cpupower/utils/helpers/amd.c | 4 +- > tools/power/cpupower/utils/helpers/cpuid.c | 8 +- > tools/power/cpupower/utils/helpers/helpers.h | 2 +- > tools/power/cpupower/utils/helpers/misc.c | 2 +- > .../utils/idle_monitor/mperf_monitor.c | 3 +- > 48 files changed, 668 insertions(+), 55 deletions(-) > create mode 100644 arch/x86/kernel/cpu/hygon.c >

3 3

【Meeting Notice】openEuler TC meeting Time: 2020-04-08 10:00-12:00
by Meeting Book 08 Apr '20

08 Apr '20

3 7

[Infra]Has the sychronization for SIG infor between gitee and website been implemented?
by Fred Li 31 Mar '20

31 Mar '20

Hi infra, I remembered I did submit an issue to request sychronization for SIG information between gitee.com/community/sig/sigs.yaml and website, but I couldn't find it. I check the current status but stil not sure it is done or not. Could anyone help to check? -- Regards Fred Li (李永乐)

1 0

about TC meeting topics
by myeuler 30 Mar '20

30 Mar '20

Hi, TC members, For the reason that more and more topics are added in meeting. I think we should do a ranking work. I propose we should arrange SIG apply topic in high priority in meeting. What about you guys?

2 1

申请增加HA SIG组
by 侯健 30 Mar '20

30 Mar '20

3 2

add to the list
by hxp 29 Mar '20

29 Mar '20

1 0

SIG组工作审视
by myeuler 27 Mar '20

27 Mar '20

Hi, All tc members, Please do the SIG work review according to this list: 1. xinwei hu : Virt, system-tool, storage, sig-kernel, sig-community 2. hong xie : sig-bounds_checking_function, sig-ai-bigdata, security-committee, Runtime, Programming-language 3. hanjun guo : Private, Packaging, oVirt, Others, Networking, 4. xiuqi Xie : Kernel, kae, iSulad, Infrastructure, doc 5. hailiang Zhang : Desktop, DB, Container, Computing 6. Xun Wang : Compiler, Base-service, A-Tune, atune 7 Wei Xiong : dev-util, Application, sig-template, sig-mate-desktop 请各位委员按照上述的分组对SIG组进行审视，审视的内容包含： 1. SIG组是否正常运作。是否有明确的负责人。 2. 相关的项目是否已经有输出，相关软件是否已经进入gitee仓。 3. 相关SIG的主页面是否有明确的介绍信息和完善的说明。下次TC meeting我们审视一下这些SIG的运作，一些SIG是否需要保留或者合并请各位委员给出建议和意见。谢谢。

2 1

Re: 新增RaspberryPi提案
by Hanjun Guo 27 Mar '20

27 Mar '20

谢谢，我初步看了代码，确实改动非常多（不仅仅是代码行数，还有改动的文件也非常多），没想到RaspberryPi有这么多代码没进主线。有几个问题想确认下： 1. 所有的RaspberryPi板子都要支持吗？我看有arm32的板子，目前openEuler不支持arm32，也没有相关的构建； 2. 里面有非常多的驱动，我们能否选一些关键的驱动先做支持？谢谢，郭寒军 On 2020/3/25 12:11, 方亚芬 wrote: > Here is our kernel source of RaspberryPi for openEuler : > https://gitee.com/eulixos/kernel/tree/openEuler1.0-base-raspi/ > > Yafen > >> -----原始邮件----- >> 发件人: "Hanjun Guo" <guohanjun(a)huawei.com> >> 发送时间: 2020-03-25 10:53:23 (星期三) >> 收件人: "方亚芬" <yafen(a)iscas.ac.cn>, tc(a)openeuler.org >> 抄送: "Xie XiuQi" <xiexiuqi(a)huawei.com> >> 主题: Re: [Tc] 新增RaspberryPi提案 >> >> +Cc Xiuqi >> >> Hi Yafen, >> >> Could you please provide the diff statistics for >> the RaspberryPi support? using "git diff --stat" or >> "git log --stat your_raspberrypi_commits" to get the data. >> >> I don't have email address from Jianmin, so did't cc >> him, sorry for that, please cc him if needed. >> >> Thanks >> Hanjun >> >> On 2020/3/13 20:44, 方亚芬 via Tc wrote: >>> openEuler技术委员会的老师，您好。我是中国科学院软件研究所智能软件研究中心的方亚芬，目前参与软件所与华为在openEuler方面的合作，负责openEuler向树莓派的移植部分工作。 >>> 申请在openEuler社区开通SIG：RaspberryPi，PR链接为：https://gitee.com/openeuler/community… 。 >>> >>> 烦请处理，谢谢。 >>> >>> >>> -- >>> 祝工作顺利，生活愉快。 >>> >>> ------------------------------------------ >>> 方亚芬 >>> 中国科学院软件研究所智能软件研究中心 >>> 邮箱：yafen(a)iscas.ac.cn <mailto:jiran@iscas.ac.cn> >>> 地址：北京市海淀区中关村南四街4号5楼 >>> >>> >>> _______________________________________________ >>> Tc mailing list -- tc(a)openeuler.org >>> To unsubscribe send an email to tc-leave(a)openeuler.org >>> > > > -- > 祝工作顺利，生活愉快。 > > > ------------------------------------------ > 方亚芬 > 中国科学院软件研究所智能软件研究中心 > 邮箱：yafen(a)iscas.ac.cn > 地址：北京市海淀区中关村南四街4号5楼 >

3 4

[会议纪要] RE: 【New Updating】 Topics RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00
by Zhanghailiang 25 Mar '20

25 Mar '20

今天TC会议议题纪要：议题1 Add WukongOS (WebOS)sig ->zhangpan 1. TC同意暂时关闭此PR，重新创建 WASI-sig，做底层技术储备，着重打造工具链 2. wasi和webos的趋势存在一致性，webos可以和wasi结合，但不一定绑定，后期在wasi或传统webos技术之上做出webos的demo 议题2: Add RaspberryPi SIG ->方亚芬会议纪要： 1. RaspberryPi针对内核的修改需要回合到openeuler kernel主线，以避免重新拉仓库导致后续openeuler kernel升级带来的维护等相关问题 2. RaspberryPi的用户态脚本可以单独出rpm包，打包流程参考openeuler新报引入流程 3. 针对内核修改代码自动化测试方法需要跟kernel maintainer对齐 4. 后续RaspberryPi出版本节奏与openeuler保持一致议题3：工具引入及社区治理 -> xiongwei (myeuler) 1. 统一引入所列的工具，TC原则上接收引入符合openeuler规范的工具，相关工具引入可以直接通过所属SIG组决定 2. SIG组运作情况例行审视，由xiongwei负责 3. 同意package语言包选择，后续考虑在引入新包时作为必填项议题4： Introduce some big data and ai develop runtime/framework -> zhengxian 纪要： 1.梳理提供基础能力首批引入哪些包，能实现openeuler中自洽，确认开源合规和依赖 2.开源合规问题可以直接咨询律师，其他问题可以在邮件组中讨论 3.具体引入包依照openeuler引入流程议题5： Add DPDK SIG -> humin 纪要： 1. DPDK sig在openEuler的开源定位是面向各种平台和网卡的，不应局限于某一个项目或某款硬件 2. TC同意PR更新后合入议题6： Add bounds_checking_function SIG -> zhaozhijian 纪要： 1、同意bounds_checking_function的申请。 2、刷新README.md文件，说明我们遵循的是C11标准，开源的函数比C11少的逻辑是什么，以及后续的规划是什么？议题7： A-Tune status report -> Shanshishi 纪要： 1、社区资料做分层改进，提供快速上手、白皮书、详细参考等 2、以用户真实需求驱动项目版本开发和演进 3、拓展用户，可以对商业产品与合作伙伴进行推荐吸引 4、开发需求要根据用户真实需求进行优先级调整议题8：Add UKUI sig -> Joey Ma 纪要：TC同意引入UKUI, 对应的PR审视后合入议题9：Add ebpf-xdp sig -> zhengxian --->未讨论，转入下次会议议题 From: Zhanghailiang via Tc [mailto:tc@openeuler.org] Sent: Wednesday, March 25, 2020 9:22 AM To: tc(a)openeuler.org Cc: Joey Ma <majunjiev(a)gmail.com>; humin (Q) <humin29(a)huawei.com>; zhaozhijian (A) <zhaozhijian(a)huawei.com>; myeuler(a)163.com; 方亚芬 <yafen(a)iscas.ac.cn>; Shanshishi <shanshishi(a)huawei.com>; 正心 <sinever(a)126.com> Subject: [Tc] 【New Updating】 Topics RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Hi all, This is all the topics I collected since last TC meeting, We will go through them in order in today’s meeting, If time is not enough, the remaining one will be put in next TC meeting. - Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 -> zhangpan - Add RaspberryPi SIG: https://gitee.com/openeuler/community/pulls/259 -->方亚芬 - 1. introduce some development tools packages in openEuler.->myEuler (熊伟） 2. apply to do some clean job in community. refine the organization of the web page. 3. set program language for each package repo https://gitee.com/openeuler/community/issues/I1C1PU - Introduce some big data and ai develop runtime/framework in openEuler: https://gitee.com/openeuler/community/pulls/217 -> zhengxian - Add DPDK SIG: https://gitee.com/openeuler/community/pulls/209 (humin) - Add bounds_checking_function SIG: https://gitee.com/openeuler/community/pulls/274 (zhaozhijian) - A-Tune status report （Shanshishi） - Add UKUI sig: https://gitee.com/openeuler/community/pulls/291 .( Joey Ma) - Add ebpf-xdp sig: https://gitee.com/openeuler/community/pulls/292 (zhengxian) Thanks, Hailiang From: Zhanghailiang via Tc [mailto:tc@openeuler.org] Sent: Tuesday, March 24, 2020 9:45 AM To: tc(a)openeuler.org<mailto:tc@openeuler.org> Cc: Shanshishi <shanshishi(a)huawei.com<mailto:shanshishi@huawei.com>> Subject: [Tc] 【Updating】 Topics RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Sorry, I have missed ShanShishi’s topic, added it here. - Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 -> zhangpan - Add RaspberryPi SIG: https://gitee.com/openeuler/community/pulls/259 -->方亚芬 - 1. introduce some development tools packages in openEuler.->myEuler (熊伟） 2. apply to do some clean job in community. refine the organization of the web page. 3. set program language for each package repo https://gitee.com/openeuler/community/issues/I1C1PU - Introduce some big data and ai develop runtime/framework in openEuler: https://gitee.com/openeuler/community/pulls/217 -> zhengxian - Add DPDK SIG: https://gitee.com/openeuler/community/pulls/209 (humin) - Add bounds_checking_function SIG: https://gitee.com/openeuler/community/pulls/274 (zhaozhijian) - A-Tune status report （Shanshishi） From: Zhanghailiang via Tc [mailto:tc@openeuler.org] Sent: Monday, March 23, 2020 2:54 PM To: Huxinwei <huxinwei(a)huawei.com<mailto:huxinwei@huawei.com>>; tc(a)openeuler.org<mailto:tc@openeuler.org> Cc: humin (Q) <humin29(a)huawei.com<mailto:humin29@huawei.com>>; zhaozhijian (A) <zhaozhijian(a)huawei.com<mailto:zhaozhijian@huawei.com>> Subject: [Tc] Re: Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 OK~ Updated topics: - Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 -> zhangpan - Add RaspberryPi SIG: https://gitee.com/openeuler/community/pulls/259 -->方亚芬 - 1. introduce some development tools packages in openEuler.->myEuler (熊伟） 2. apply to do some clean job in community. refine the organization of the web page. 3. set program language for each package repo https://gitee.com/openeuler/community/issues/I1C1PU - Introduce some big data and ai develop runtime/framework in openEuler: https://gitee.com/openeuler/community/pulls/217 -> zhengxian - Add DPDK SIG: https://gitee.com/openeuler/community/pulls/209 (humin) - Add bounds_checking_function SIG: https://gitee.com/openeuler/community/pulls/274 (zhaozhijian) - A-Tune status From: Huxinwei Sent: Monday, March 23, 2020 11:52 AM To: Zhanghailiang <zhang.zhanghailiang(a)huawei.com<mailto:zhang.zhanghailiang@huawei.com>>; tc(a)openeuler.org<mailto:tc@openeuler.org> Cc: humin (Q) <humin29(a)huawei.com<mailto:humin29@huawei.com>>; zhaozhijian (A) <zhaozhijian(a)huawei.com<mailto:zhaozhijian@huawei.com>> Subject: RE: Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 2 additional proposals, One for DPDK SIG, humin29(a)huawei.com<mailto:humin29@huawei.com> https://gitee.com/openeuler/community/pulls/209<javascript:;> One for bounds_checking_function, zhaozhijian(a)huawei.com<mailto:zhaozhijian@huawei.com> https://gitee.com/openeuler/community/pulls/274 Please kindly schedule. Thanks. From: Zhanghailiang via Tc [mailto:tc@openeuler.org] Sent: Monday, March 23, 2020 9:34 AM To: tc(a)openeuler.org<mailto:tc@openeuler.org> Cc: myeuler <myeuler(a)163.com<mailto:myeuler@163.com>>; 正心 <sinever(a)126.com<mailto:sinever@126.com>>; zhangpan (L) <zhangpan26(a)huawei.com<mailto:zhangpan26@huawei.com>>; 方亚芬 <yafen(a)iscas.ac.cn<mailto:yafen@iscas.ac.cn>> Subject: [Tc] Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Hi All, This is the topics we collected for 3.25 TC meeting: - Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 -> zhangpan - Add RaspberryPi SIG: https://gitee.com/openeuler/community/pulls/259 -->方亚芬 - 1. introduce some development tools packages in openEuler.->myEuler (熊伟） 2. apply to do some clean job in community. refine the organization of the web page. 3. set program language for each package repo https://gitee.com/openeuler/community/issues/I1C1PU - introduce some big data and ai develop runtime/framework in openEuler -> zhengxian Please let me know if you would like to add a topic. From: Zhanghailiang via Tc [mailto:tc@openeuler.org] Sent: Wednesday, March 11, 2020 2:56 PM To: tc(a)openeuler.org<mailto:tc@openeuler.org> Cc: zhangpan (L) <zhangpan26(a)huawei.com<mailto:zhangpan26@huawei.com>> Subject: [Tc] TC Call for agenda 2020-03-25 RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Hi Please, send any topic that you are interested in covering. We have already one topic for this call already: 1) Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 Thanks, Hailiang From: Meeting Book via Tc [mailto:tc@openeuler.org] Sent: Wednesday, March 11, 2020 2:37 PM To: tc(a)openeuler.org<mailto:tc@openeuler.org> Subject: [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Topic openEuler TC meeting Time 2020-03-25 10:00-12:00((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/627988019> Meeting ID 627 988 019 Convener 张海亮 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载ZOOM客户端入会。 Please click the conference link and download the ZOOM to join the conference. Huawei and all its affiliates respect your privacy and are committed to protecting it. When inviting you to join a video meeting, we will collect and use your personal information, including your name, device type, IP address, network type, microphone, speaker, camera, joining time, and leaving time. For more information about Huawei’s privacy policy, visit https://www.huawei.com/en/privacy-policy

1 0

[tc][package]About how to manage and maintain packages/dependencies
by Fred Li 25 Mar '20

25 Mar '20

Hi TC members, Infrastructure team and community members, Recently there are many issues about adding dependencies or new packages [1][2][3]. As a linux operating system, it is extremely critical to manage the dependencies. As we know, Technical committee is managing the packages management policy, however who maintain the new packages is not clear. I have draft idea on this. Please give your advice, opinions on how to maintain the dependencies. - policy. Dependencies are still packages, thus they follow the flow on how to introduce the packages into openEuler community. - Who to maintain: if the packages are new and only dependencies, probably one specific team is an option to do this. - How to automate: Infrastructure should provide a function on getting update from upstream automatically - Dependencies management: an expert should maintain the detailed work on how to choose for ISO and yum for each specific version of release. [1] https://gitee.com/openeuler/community-issue/issues/I1CBYV?from=project-issue [2] https://gitee.com/openeuler/community-issue/issues/I1BHND?from=project-issue [3] https://gitee.com/openeuler/community-issue/issues/I1CBW5?from=project-issue -- Regards Fred Li (李永乐)

2 1