Signed-off-by: Nx_xiny <1301913191@qq.com>
Change-Id: I0e0b59cdc22b292ccf0a790010c037d43793a934

背景：重复执行内存测试用例约几百次，系统大概率出现卡死现象，经分析知，系统卡在
内存spinlock锁中，CPU1在获取内存spinlock锁后打印异常信息，此时循环buffer满了，
CPU0此时进入异常且尝试拿取内存spinlock锁，两个核都处于锁中断锁任务状态，CPU1
写事件触发调度打印输出失败，进而在write接口中死循环无法退出，导致两个核都卡住。
方案：在write接口中增加一个判断条件：当前核处于锁任务状态且循环buffer满了时候，
直接退出循环，丢弃打印信息（持有spinlock锁后一般禁止输出打印信息）。

close #I4F7PO
Signed-off-by: NHaryslee <lihao189@huawei.com>
Change-Id: I3f49a1bb211821e9c5d1d220d6867962d6a45a79

修复社区反馈问题Percpu结构体注释错误，排查下其他拼写错误。

close #I4GMLH
Signed-off-by: Nkenneth <zhushangyuan@huawei.com>

close: #I4DAKM
Signed-off-by: Nzff <zhangfanfan2@huawei.com>
Change-Id: I5acc8b2b632633b0717eb4186773e6cae35ea0e4

1.内核打印的地方支持异常时重定向打印信息
2.excinfo 命令中申请的内存64对齐
Close #I482S5
Signed-off-by: Nzhushengle <zhushengle@huawei.com>
Change-Id: I4e8a971cc5b14f62d573bb160682089d9d50e64e

当console层的打印缓冲buffer满且打印任务被饿死时，函数ConsoleOutput会出现在for循环中
不退出的情况，导致中断打印时卡死

close: #I4C9GC
Signed-off-by: Nzff <zhangfanfan2@huawei.com>
Change-Id: I70b9d7c848dce7d351c5679e7b08049df27a6f10

1. 原kernel/common目录下属于内核拓展组件，统一移入kernel/extend管理
2. Kconfig分层，各模块自己的配置放到自己目录下管理
3. 原platform下不属于平台的公共代码抽到kernel/common下，只留板级链接脚本和一些编译脚本指向device目录下触发平台相关的编译
4. 对外公共头文件统一抽到对外include路径
5. 废弃宏，头文件清理

close: #I48KI4
Signed-off-by: Narvinzzz <zhaotianyu9@huawei.com>
Change-Id: I0cf5ea81c92a8fa7b113da9cbdc8b7bc935f5aae

add BUILD.gn for all kernel modules
Signed-off-by: NCaoruihong <crh.cao@huawei.com>
Change-Id: I018446427bf64615f2596d47862b219659b58b34

support turn off as many features as possible.
current only libc and posix and bsd can not be turned off.
Signed-off-by: NCaoruihong <crh.cao@huawei.com>
Change-Id: I1e97570c67593207a56dc11f357eca4b4a018bfd

storage medium is separated from the shell module.

Change-Id: Id56939001d70bb92d9cc02bd7c9f55ca8b61cf5b

Change-Id: I052d930d54e63179b17b77f02c107a015f3cfc3f

Change-Id: Ia6c1f6302407a707b3ec9b805f4c92d8a7970b86