初始化调度时间不以g_sysSchedStartTime是否为0为界限，而以g_sysSchedStartTime是否为64位最大值
为界限，避免特殊以下场景：调度开启时系统时间为0，导致初始化的g_sysSchedStartTime还是0，导致
调度启动后获取的调度时间轴始终为0.
Close  #I45HP5
Signed-off-by: Nzhushengle <zhushengle@huawei.com>
Change-Id: I5272c79f06b53361ee7b931081d3a3276db59073

killpg：给进程组发信号
waitid：等待进程结束
修改测试用例到full里面

Change-Id: Ice058ab4a6eede8ecbaacea0894c2161e3b9dce2
Signed-off-by: Nwjj <502004968@qq.com>

背景：进程加载的时候，先预申请一个页用作参数拷贝，另外通过mmap方式申请
额外的虚拟栈空间，此时便有两个地址连续的区间。
方案：新增内部接口OsStackAlloc，用于申请一个连续的虚拟地址区间，并对其
中指定区间做物理内存的映射。

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

   DoNanoSleep 接口以微秒为单位，纳秒级别的在转换成微秒时被整除为0，
导致转换成tick时为0，导致延时时触发yield，导致延时时间超大
Close #I3Z9DP
Signed-off-by: Nzhushengle <zhushengle@huawei.com>
Change-Id: Ib662fdc80707be6040b2bb06a1b457344bd48b30

方案描述：
    1.周期软件定时器超时添加一个startTime字段，用于记录当前软件定时器的开始计时的时间，
    在定时器响应时，开始时间修改为上一次响应的结束时间(消除了中断执行时间对软件定时器
    的影响)。
    2.在执行tick中断的过程当中，持有tick动态计算锁，保证在该过程中不会触发tick周期
    的计算，在tick中断结束时统一计算设置。 --- 提升tick中断的执行效率
    3.在设置tick周期时，减掉tick中断执行的时间，减小周期动态化带来的时间误差
    4.新增LOSCFG_BASE_CORE_TICK_PER_SECOND_MINI配置宏，用于配置tick中断的最小响应精度
Close #I43UQJ
Signed-off-by: Nzhushengle <zhushengle@huawei.com>
Change-Id: Icd1159a1890046b13602b7a18dcd6234d5c61a89

Close #I446CX
Signed-off-by: Nzhushengle <zhushengle@huawei.com>
Change-Id: I49e80ffe1a7b579b82aaf45f599623b287eb8e98

close #I41P8Y
Signed-off-by: NJerryH <huangjieliang@huawei.com>
Change-Id: I01833cf617bbc695543a865dbb994c6c22d4a0a8

fix some spell issues in files under folder kernel/base/core:
change Recyle to Recycle, ilde to idle and Porcess to Process

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

add setrlimit,gethostname,gethostid and capability

Change-Id: I0d5f23cb87ec2731fb79e7c5cfbe1ce109ac158a

fix compile errors in minimal compilation
Signed-off-by: NCaoruihong <crh.cao@huawei.com>
Change-Id: I48f4f7b27c684e2c747c1949776c5c4f9e383dec

LiteOS_a中有部分配置宏进行了重复冗余定义，导致当头文件未被包含时，极易引入错误，
故对menuconfig配置宏进行统一处理，均使用#ifdef/#ifndef作为预编译判断方式

Close #I3YEGS

Change-Id: Ife6db770cc66de1d6199a4f3ba3950e9bfd0e71a
Signed-off-by: Nboxi <lewis.liulei@huawei.com>

　kill进程时，会将因为liteipc阻塞的线程唤醒，使其调度并自动退出，由于liteipc阻塞机制为
循环阻塞方式，会导致将因liteipc阻塞的线程唤醒后又进入等待中。此处在唤醒因liteipc阻塞的
线程后检查是否已有kill标志，如果有使其按接收数据失败退出，在返回用户态之前，该线程会进
入退出流程，结束运行。

Close #I3XX7K
Signed-off-by: Nzhushengle <zhushengle@huawei.com>
Change-Id: Iec4e298dff4aefd2994289067a35cb5673e323f9

write "clear pathcahe" to clear pathcaches and vnodes
write "clear pagecache" to clear pagecaches
write "clear all" to clear both pathcaches and pagechaches
the cache in use will not be cleared

close: #I3XLPH
Signed-off-by: Nmucor <mucorwang@gmail.com>

add /proc/fs_cache to display vnode, path cache, page cache.
also change some bad virable name

close: #I3WWBD
Signed-off-by: Nmucor <mucorwang@gmail.com>

add /proc/fs_cache to display vnode, path cache, page cache.
also change some bad virable name

close: #I3WESD
Signed-off-by: Nmucor <mucorwang@gmail.com>

rename function OsCreateUserVmSpace to fix typo

close https://gitee.com/openharmony/kernel_liteos_a/issues/I3QD42Signed-off-by: kenneth <459864689@qq.com>

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

【背景】当前timer_create接口不支持以SIGEV_THREAD的方式创建多个定时器

【修改方案】
1、内核timer_create接口在创建software timers相应的线程时，使用线程
taskCB所携带的信息识别各个线程的信号并依据该信息分别派发出信号。
2、关于用户任务操作许可验证的修改，现在允许同一用户线程向其自身派发信
号，软件定时器计时结束，向用户态发送相应的信号，完成用户态线程的回调。

【影响】
对现有的产品暂无影响。

re #I3SRFI
Signed-off-by: yansira <yansira@hotmail.com>
Change-Id: Ia23f5ef01975bf867dd7f5db797a30c264c50501

背景: 当前信号实现原理是在系统调用结束和中断结束时检查是否有信号处理,
      如果有信号处理就切去处理信号，信号处理结束后回来继续按原来流程执行。
问题：当用户态线程在执行系统调用或缺页异常时，运行在内核态，如果此时有信
      号需要处理，且该线程已经持有了部分内核资源(如：锁，内存等), 此时如
      果有中断发生，则在中断结束时，就会去处理该信号，此时用户态线程持有
      了内核未释放的资源跑到了用户态去运行，如果该线程在用户态出现问题,
      那么它持有的内核资源就无法被释放了。
方案：用户态线程在执行系统调用和缺页异常时暂时屏蔽信号，防止此时有中断去
      处理信号，等系统调用结束或缺页异常结束时再去处理信号。
解决的问题：
  1. 执行系统调用或缺页异常时屏蔽信号，防止中断去处理信号
  2.解决无法kill 因为用户态的锁、ipc等阻塞的用户态线程
  3.进程退出方式转变为: 依次通过kill去杀死该进程的所有线程

Close #I3S0N0

Change-Id: I0c48b9c89382826191b8a9326c71b57ba84124c2

close: #I3SDKY

Change-Id: I5ed9356ce2b55b6e07c3f192cdbc4a4f6fbfaa58

close: #I3I768

Change-Id: I4f801df4abe1a9afdf43391c28276e96a5e81513

correct function name OsSchedSetIdleTaskSchedParam

close https://gitee.com/openharmony/kernel_liteos_a/issues/I3RQ6J

Close #I3OAFR

Change-Id: I25b14572809b6fabb9e9d17de89a99047c02a59b

correct some typos in los_task.c and other files

close https://gitee.com/openharmony/kernel_liteos_a/issues/I3QDB8

Close #I3OAFR

Change-Id: Icea238e20adf402d0ec1fc7e47ff4e58124a5e83

Change-Id: I626a96376fe6bee69b10ee9b56495d62849c19b7

Change-Id: I052d930d54e63179b17b77f02c107a015f3cfc3f

Change-Id: I8d2e9f96e86f4130474da9898791240b5d42328e

Description:Delete VM to support only kernel mode.
Sig:liteos_a
Feature or Bugfix:Feature
Binary Source:No

Change-Id: Ie1029c8fbc0c1b85c138663933118d2d148b7769

The macros assume that constants that are compared against
"addr" are either unsigned or less than INT_MAX.
In some cases it is not true so change costants to unsigned
using U32_C macros.
The correct solution would be to change teh MEM_ADDR, PMM_BASE, etc.
to be unsigned long but currently "U" suffix is appended in various
places so the assumption is that those macros use default definition
(which is int).

Put "addr" into brackets by the way since it could be an expression
rather than one variable.
Signed-off-by: NZbigniew Bodek <zbigniew.bodek@huawei.com>
Change-Id: Ife9bc5863b4934ecaab64b24faa084b87d7d7ea5

The macro to append "U" suffix should be named
according to what it actually does which is defining U32 constant.
Signed-off-by: NZbigniew Bodek <zbigniew.bodek@huawei.com>
Change-Id: I55701f0650c88bd083c062581af5c7a1b966bc0b

Reviewed-by: shenwei and zhangfanfan

Reviewed-by:liulei, lihao, likailong

Change-Id: Ibacdda2ccbbc991ac9732f2ad09bdb98195203b3

Change-Id: Ia6c1f6302407a707b3ec9b805f4c92d8a7970b86