1. 03 Mar, 2018 1 commit
  2. 28 Feb, 2018 1 commit
  3. 22 Feb, 2018 1 commit
  4. 21 Feb, 2018 1 commit
  5. 19 Feb, 2018 1 commit
  6. 13 Feb, 2018 1 commit
  7. 09 Feb, 2018 1 commit
  8. 08 Feb, 2018 1 commit
  9. 07 Feb, 2018 7 commits
  10. 06 Feb, 2018 1 commit
  11. 05 Feb, 2018 2 commits
    • Mathieu Desnoyers's avatar
      powerpc, membarrier: Skip memory barrier in switch_mm() · 3ccfebed
      Mathieu Desnoyers authored
      
      Allow PowerPC to skip the full memory barrier in switch_mm(), and
      only issue the barrier when scheduling into a task belonging to a
      process that has registered to use expedited private.
      
      Threads targeting the same VM but which belong to different thread
      groups is a tricky case. It has a few consequences:
      
      It turns out that we cannot rely on get_nr_threads(p) to count the
      number of threads using a VM. We can use
      (atomic_read(&mm->mm_users) == 1 && get_nr_threads(p) == 1)
      instead to skip the synchronize_sched() for cases where the VM only has
      a single user, and that user only has a single thread.
      
      It also turns out that we cannot use for_each_thread() to set
      thread flags in all threads using a VM, as it only iterates on the
      thread group.
      
      Therefore, test the membarrier state variable directly rather than
      relying on thread flags. This means
      membarrier_register_private_expedited() needs to set the
      MEMBARRIER_STATE_PRIVATE_EXPEDITED flag, issue synchronize_sched(), and
      only then set MEMBARRIER_STATE_PRIVATE_EXPEDITED_READY which allows
      private expedited membarrier commands to succeed.
      membarrier_arch_switch_mm() now tests for the
      MEMBARRIER_STATE_PRIVATE_EXPEDITED flag.
      Signed-off-by: default avatarMathieu Desnoyers <mathieu.desnoyers@efficios.com>
      Acked-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Acked-by: default avatarPeter Zijlstra (Intel) <peterz@infradead.org>
      Cc: Alan Stern <stern@rowland.harvard.edu>
      Cc: Alexander Viro <viro@zeniv.linux.org.uk>
      Cc: Andrea Parri <parri.andrea@gmail.com>
      Cc: Andrew Hunter <ahh@google.com>
      Cc: Andy Lutomirski <luto@kernel.org>
      Cc: Avi Kivity <avi@scylladb.com>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Boqun Feng <boqun.feng@gmail.com>
      Cc: Dave Watson <davejwatson@fb.com>
      Cc: David Sehr <sehr@google.com>
      Cc: Greg Hackmann <ghackmann@google.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Maged Michael <maged.michael@gmail.com>
      Cc: Michael Ellerman <mpe@ellerman.id.au>
      Cc: Nicholas Piggin <npiggin@gmail.com>
      Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Russell King <linux@armlinux.org.uk>
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: linux-api@vger.kernel.org
      Cc: linux-arch@vger.kernel.org
      Cc: linuxppc-dev@lists.ozlabs.org
      Link: http://lkml.kernel.org/r/20180129202020.8515-3-mathieu.desnoyers@efficios.com
      
      Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
      3ccfebed
    • Jie Deng's avatar
      dwc-xlgmac: remove Jie Deng as co-maintainer · 23ddd261
      Jie Deng authored
      
      Jose Abreu is working on this driver and I will leave Synopsys soon.
      Thus it does not seem appropriate for me to be a co-maintainer anymore.
      Signed-off-by: default avatarJie Deng <jiedeng@synopsys.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      23ddd261
  12. 04 Feb, 2018 1 commit
  13. 02 Feb, 2018 1 commit
  14. 31 Jan, 2018 6 commits
  15. 29 Jan, 2018 1 commit
  16. 27 Jan, 2018 2 commits
  17. 26 Jan, 2018 3 commits
  18. 25 Jan, 2018 4 commits
  19. 24 Jan, 2018 3 commits
  20. 22 Jan, 2018 1 commit
    • Miodrag Dinic's avatar
      MIPS: ranchu: Add Ranchu as a new generic-based board · f2d0b0d5
      Miodrag Dinic authored
      
      Provide amendments to the MIPS generic platform framework so that
      the new generic-based board Ranchu can be chosen to be built.
      
      The Ranchu board is intended to be used by Android emulator. The name
      "Ranchu" originates from Android development community. "Goldfish" and
      "Ranchu" are terms used for two generations of virtual boards used by
      Android emulator. The name "Ranchu" is a newer one among the two, and
      this patch deals with Ranchu. However, for historical reasons, some
      devices/drivers still contain the name "Goldfish".
      
      MIPS Ranchu machine includes a number of Goldfish devices. The support
      for Virtio devices is also included. Ranchu board supports up to 16
      Virtio devices which can be attached using Virtio MMIO Bus. This is
      summarized in the following picture:
      
             ABUS
              ||----MIPS CPU
              ||       |                    IRQs
              ||----Goldfish PIC------------(32)--------
              ||                     | | | | | | | | |
              ||----Goldfish TTY------ | | | | | | | |
              ||                       | | | | | | | |
              ||----Goldfish RTC-------- | | | | | | |
              ||                         | | | | | | |
              ||----Goldfish FB----------- | | | | | |
              ||                           | | | | | |
              ||----Goldfish Events--------- | | | | |
              ||                             | | | | |
              ||----Goldfish Audio------------ | | | |
              ||                               | | | |
              ||----Goldfish Battery------------ | | |
              ||                                 | | |
              ||----Android PIPE------------------ | |
              ||                                   | |
              ||----Virtio MMIO Bus                | |
              ||    |    |    |                    | |
              ||    |    |   (virtio-block)--------- |
              ||   (16)  |                           |
              ||    |   (virtio-net)------------------
      
      Device Tree is created on the QEMU side based on the information about
      devices IO map and IRQ numbers. Kernel will load this DTB using UHI
      boot protocol DTB handover mode.
      Signed-off-by: default avatarMiodrag Dinic <miodrag.dinic@mips.com>
      Signed-off-by: default avatarGoran Ferenc <goran.ferenc@mips.com>
      Signed-off-by: default avatarAleksandar Markovic <aleksandar.markovic@mips.com>
      Reviewed-by: default avatarJames Hogan <jhogan@kernel.org>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Paul Burton <paul.burton@mips.com>
      Cc: linux-mips@linux-mips.org
      Patchwork: https://patchwork.linux-mips.org/patch/18138/
      
      Signed-off-by: default avatarJames Hogan <jhogan@kernel.org>
      f2d0b0d5