1. 31 8月, 2017 1 次提交
  2. 30 8月, 2017 1 次提交
  3. 29 8月, 2017 1 次提交
    • D
      hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK) · ae0078fc
      Dexuan Cui 提交于
      Hyper-V Sockets (hv_sock) supplies a byte-stream based communication
      mechanism between the host and the guest. It uses VMBus ringbuffer as the
      transportation layer.
      
      With hv_sock, applications between the host (Windows 10, Windows Server
      2016 or newer) and the guest can talk with each other using the traditional
      socket APIs.
      
      More info about Hyper-V Sockets is available here:
      
      "Make your own integration services":
      https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service
      
      The patch implements the necessary support in Linux guest by introducing a new
      vsock transport for AF_VSOCK.
      Signed-off-by: NDexuan Cui <decui@microsoft.com>
      Cc: K. Y. Srinivasan <kys@microsoft.com>
      Cc: Haiyang Zhang <haiyangz@microsoft.com>
      Cc: Stephen Hemminger <sthemmin@microsoft.com>
      Cc: Andy King <acking@vmware.com>
      Cc: Dmitry Torokhov <dtor@vmware.com>
      Cc: George Zhang <georgezhang@vmware.com>
      Cc: Jorgen Hansen <jhansen@vmware.com>
      Cc: Reilly Grant <grantr@vmware.com>
      Cc: Asias He <asias@redhat.com>
      Cc: Stefan Hajnoczi <stefanha@redhat.com>
      Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
      Cc: Cathy Avery <cavery@redhat.com>
      Cc: Rolf Neugebauer <rolf.neugebauer@docker.com>
      Cc: Marcelo Cerri <marcelo.cerri@canonical.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ae0078fc
  4. 28 8月, 2017 1 次提交
  5. 24 8月, 2017 1 次提交
  6. 23 8月, 2017 2 次提交
  7. 22 8月, 2017 2 次提交
  8. 20 8月, 2017 1 次提交
  9. 18 8月, 2017 3 次提交
  10. 17 8月, 2017 2 次提交
    • M
      membarrier: Provide expedited private command · 22e4ebb9
      Mathieu Desnoyers 提交于
      Implement MEMBARRIER_CMD_PRIVATE_EXPEDITED with IPIs using cpumask built
      from all runqueues for which current thread's mm is the same as the
      thread calling sys_membarrier. It executes faster than the non-expedited
      variant (no blocking). It also works on NOHZ_FULL configurations.
      
      Scheduler-wise, it requires a memory barrier before and after context
      switching between processes (which have different mm). The memory
      barrier before context switch is already present. For the barrier after
      context switch:
      
      * Our TSO archs can do RELEASE without being a full barrier. Look at
        x86 spin_unlock() being a regular STORE for example.  But for those
        archs, all atomics imply smp_mb and all of them have atomic ops in
        switch_mm() for mm_cpumask(), and on x86 the CR3 load acts as a full
        barrier.
      
      * From all weakly ordered machines, only ARM64 and PPC can do RELEASE,
        the rest does indeed do smp_mb(), so there the spin_unlock() is a full
        barrier and we're good.
      
      * ARM64 has a very heavy barrier in switch_to(), which suffices.
      
      * PPC just removed its barrier from switch_to(), but appears to be
        talking about adding something to switch_mm(). So add a
        smp_mb__after_unlock_lock() for now, until this is settled on the PPC
        side.
      
      Changes since v3:
      - Properly document the memory barriers provided by each architecture.
      
      Changes since v2:
      - Address comments from Peter Zijlstra,
      - Add smp_mb__after_unlock_lock() after finish_lock_switch() in
        finish_task_switch() to add the memory barrier we need after storing
        to rq->curr. This is much simpler than the previous approach relying
        on atomic_dec_and_test() in mmdrop(), which actually added a memory
        barrier in the common case of switching between userspace processes.
      - Return -EINVAL when MEMBARRIER_CMD_SHARED is used on a nohz_full
        kernel, rather than having the whole membarrier system call returning
        -ENOSYS. Indeed, CMD_PRIVATE_EXPEDITED is compatible with nohz_full.
        Adapt the CMD_QUERY mask accordingly.
      
      Changes since v1:
      - move membarrier code under kernel/sched/ because it uses the
        scheduler runqueue,
      - only add the barrier when we switch from a kernel thread. The case
        where we switch from a user-space thread is already handled by
        the atomic_dec_and_test() in mmdrop().
      - add a comment to mmdrop() documenting the requirement on the implicit
        memory barrier.
      
      CC: Peter Zijlstra <peterz@infradead.org>
      CC: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
      CC: Boqun Feng <boqun.feng@gmail.com>
      CC: Andrew Hunter <ahh@google.com>
      CC: Maged Michael <maged.michael@gmail.com>
      CC: gromer@google.com
      CC: Avi Kivity <avi@scylladb.com>
      CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      CC: Paul Mackerras <paulus@samba.org>
      CC: Michael Ellerman <mpe@ellerman.id.au>
      Signed-off-by: NMathieu Desnoyers <mathieu.desnoyers@efficios.com>
      Signed-off-by: NPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      Tested-by: NDave Watson <davejwatson@fb.com>
      22e4ebb9
    • N
  11. 14 8月, 2017 1 次提交
  12. 12 8月, 2017 1 次提交
  13. 11 8月, 2017 3 次提交
  14. 09 8月, 2017 3 次提交
  15. 07 8月, 2017 1 次提交
  16. 04 8月, 2017 1 次提交
  17. 03 8月, 2017 1 次提交
  18. 02 8月, 2017 2 次提交
  19. 01 8月, 2017 2 次提交
  20. 31 7月, 2017 1 次提交
  21. 30 7月, 2017 1 次提交
  22. 29 7月, 2017 1 次提交
  23. 25 7月, 2017 1 次提交
  24. 24 7月, 2017 2 次提交
    • L
      Properly alphabetize MAINTAINERS file · 7683e9e5
      Linus Torvalds 提交于
      This adds a perl script to actually parse the MAINTAINERS file, clean up
      some whitespace in it, warn about errors in it, and then properly sort
      the end result.
      
      My perl-fu is atrocious, so the script has basically been created by
      randomly putting various characters in a pile, mixing them around, and
      then looking it the end result does anything interesting when used as a
      perl script.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7683e9e5
    • L
      Fix up MAINTAINERS file problems · f47e07bc
      Linus Torvalds 提交于
      Prepping for scripting the MAINTAINERS file cleanup (and possible split)
      showed a couple of cases where the headers for a couple of entries were
      bogus.
      
      There's a few different kinds of bogosities:
      
       - the X-GENE SOC EDAC case was confused and split over two lines
      
       - there were four entries for "GREYBUS PROTOCOLS DRIVERS" that were all
         different things.
      
       - the NOKIA N900 CAMERA SUPPORT" was duplicated
      
      all of which were more obvious when you started doing associative arrays
      in perl to track these things by the header (so that we can alphabetize
      this thing properly, and so that we might split it up by the data too).
      
      Cc: Joe Perches <joe@perches.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      f47e07bc
  25. 22 7月, 2017 1 次提交
  26. 18 7月, 2017 2 次提交
  27. 17 7月, 2017 1 次提交