1. 08 Jan, 2021 1 commit
  2. 11 Dec, 2020 1 commit
  3. 04 Nov, 2020 3 commits
    • Jan Kiszka's avatar
      ipipe-core-4.19.152-cip37-x86-15 · c659a644
      Jan Kiszka authored
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      c659a644
    • Jan Kiszka's avatar
      Merge tag 'v4.19.152-cip37' into ipipe-x86-4.19.y-cip · a4fb1672
      Jan Kiszka authored
      This is the v4.19.152-cip37 CIP release
      a4fb1672
    • Jan Kiszka's avatar
      ipipe: mm: Drop un-COW from copy_pte_range · 0f0b6099
      Jan Kiszka authored
      This is not needed, in fact, and it is in conflict with upcoming stable
      changes. Philippe writes:
      
      "IIRC, the reason was to ensure that any mapping duplicated from a
      parent process which has pinned its memory via an earlier call to
      __ipipe_disable_ondemand_mappings() would be immediately un-COWed upon
      fork() in the child process. On second thoughts, this is useless since
      the child process either:
      
      - if it has to, explicitly attaches to the real-time core, which ends up
        calling mlock(), therefore causing these mappings to be un-COWed if
        need be. IOW, there is no inheritance of the Cobalt context at
        fork. Maybe at some point in time there was the assumption that such
        context might be shared between both processes somehow, which has been
        ruled out later on.
      
      - the child process does not attach to the real-time core, in which case
        COW is a non-issue."
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      0f0b6099
  4. 25 Oct, 2020 1 commit
  5. 23 Oct, 2020 7 commits
  6. 22 Oct, 2020 13 commits
  7. 20 Oct, 2020 14 commits