1. 28 Apr, 2012 11 commits
  2. 26 Apr, 2012 8 commits
  3. 25 Apr, 2012 7 commits
  4. 24 Apr, 2012 1 commit
  5. 23 Apr, 2012 7 commits
  6. 19 Apr, 2012 4 commits
  7. 18 Apr, 2012 2 commits
    • Pavel Emelyanov's avatar
      dump: Init mmap's file pos · fd85b194
      Pavel Emelyanov authored
      It's unused, but makes show command show 0, not trash.
      Signed-off-by: 's avatarPavel Emelyanov <xemul@parallels.com>
      fd85b194
    • Cyrill Gorcunov's avatar
      syscalls: Complete redesign v9 · 2ea781a9
      Cyrill Gorcunov authored
      At early days we've been using only a few syscalls
      which together with debug compiler options always
      produce relative addresses for memory variables used
      in parasite and restorer blobs. Thus it came in unnoticed
      that there is something worng with syscalls declarations
      we use.
      
      Basically all our syscalls are just a wrappers over inline
      assembly code in form of
      
      static long syscall2(int nr, long arg0, long arg1)
      {
      	long ret;
      	asm volatile(
      		"movl %1, %%eax		\t\n"
      		"movq %2, %%rdi		\t\n"
      		"movq %3, %%rsi		\t\n"
      		"syscall		\t\n"
      		"movq %%rax, %0		\t\n"
      		: "=r"(ret)
      		: "g" ((int)nr), "g" (arg0), "g" (arg1)
      		: "rax", "rdi", "rsi", "memory");
      	return ret;
      }
      
      so every argument treated to be plain long (even if the call
      sematics implies it's a memory address passed but not some
      integer direct value) and transferred via general purpose
      register.
      
      As being mentioned it caused no problems when debug options
      specified at compile time, the compiler do not tries to optimize
      addressing but generates code which always compute them.
      
      The situation is changed if one is building crtools with
      optimization enabled -- the compiler finds that arguments
      are rather plain long numbers and might pass direct addresses
      of variables, instead of generating relative addresses
      (because function declarations have no pointers and 'g' in cope
       with 'mov' is used, which is of course wrong).
      
      To fix all this -- now syscalls declarations are generated from
      syscall.def file and function arguments are passed in conform
      with x86-64 ABI.
      
      This shrinks amount of source code needed to declare syscalls
      and opens a way to use optimization.
      Signed-off-by: 's avatarCyrill Gorcunov <gorcunov@openvz.org>
      Signed-off-by: 's avatarPavel Emelyanov <xemul@parallels.com>
      2ea781a9