1. 21 5月, 2018 1 次提交
  2. 06 11月, 2017 1 次提交
    • S
      powernv/opal-sensor: remove not needed lock · 95e1bc1d
      Stewart Smith 提交于
      Parallel sensor reads could run out of async tokens due to
      opal_get_sensor_data grabbing tokens but then doing the sensor
      read behind a mutex, essentially serializing the (possibly
      asynchronous and relatively slow) sensor read.
      
      It turns out that the mutex isn't needed at all, not only
      should the OPAL interface allow concurrent reads, the implementation
      is certainly safe for that, and if any sensor we were reading
      from somewhere isn't, doing the mutual exclusion in the kernel
      is the wrong place to do it, OPAL should be doing it for the kernel.
      
      So, remove the mutex.
      
      Additionally, we shouldn't be printing out an error when we don't
      get a token as the only way this should happen is if we've been
      interrupted in down_interruptible() on the semaphore.
      Reported-by: NRobert Lippert <rlippert@google.com>
      Signed-off-by: NStewart Smith <stewart@linux.vnet.ibm.com>
      Signed-off-by: NCyril Bur <cyrilbur@gmail.com>
      Signed-off-by: NMichael Ellerman <mpe@ellerman.id.au>
      95e1bc1d
  3. 31 3月, 2017 1 次提交
  4. 29 6月, 2016 1 次提交
  5. 22 5月, 2015 1 次提交
  6. 31 3月, 2015 2 次提交
  7. 01 12月, 2014 1 次提交
  8. 09 4月, 2014 1 次提交
  9. 07 4月, 2014 1 次提交
  10. 24 3月, 2014 1 次提交