1. 04 Apr, 2019 1 commit
  2. 02 Mar, 2019 1 commit
  3. 21 Feb, 2019 3 commits
  4. 18 Feb, 2019 2 commits
    • Oded Gabbay's avatar
      habanalabs: add debugfs support · c2164773
      Oded Gabbay authored
      This patch adds debugfs support to the driver. It allows the user-space to
      display information that is contained in the internal structures of the
      driver, such as:
      - active command submissions
      - active user virtual memory mappings
      - number of allocated command buffers
      
      It also enables the user to perform reads and writes through Goya's PCI
      bars.
      Reviewed-by: default avatarMike Rapoport <rppt@linux.ibm.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c2164773
    • Oded Gabbay's avatar
      habanalabs: add sysfs and hwmon support · d91389bc
      Oded Gabbay authored
      This patch add the sysfs and hwmon entries that are exposed by the driver.
      
      Goya has several sensors, from various categories such as temperature,
      voltage, current, etc. The driver exposes those sensors in the standard
      hwmon mechanism.
      
      In addition, the driver exposes a couple of interfaces in sysfs, both for
      configuration and for providing status of the device or driver.
      
      The configuration attributes is for Power Management:
      - Automatic or manual
      - Frequency value when moving to high frequency mode
      - Maximum power the device is allowed to consume
      
      The rest of the attributes are read-only and provide the following
      information:
      - Versions of the various firmwares running on the device
      - Contents of the device's EEPROM
      - The device type (currently only Goya is supported)
      - PCI address of the device (to allow user-space to connect between
        /dev/hlX to PCI address)
      - Status of the device (operational, malfunction, in_reset)
      - How many processes are open on the device's file
      Reviewed-by: default avatarMike Rapoport <rppt@linux.ibm.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      d91389bc
  5. 15 Feb, 2019 1 commit
    • Kimberly Brown's avatar
      Drivers: hv: vmbus: Expose counters for interrupts and full conditions · 396ae57e
      Kimberly Brown authored
      Counter values for per-channel interrupts and ring buffer full
      conditions are useful for investigating performance.
      
      Expose counters in sysfs for 2 types of guest to host interrupts:
      1) Interrupts caused by the channel's outbound ring buffer transitioning
      from empty to not empty
      2) Interrupts caused by the channel's inbound ring buffer transitioning
      from full to not full while a packet is waiting for enough buffer space to
      become available
      
      Expose 2 counters in sysfs for the number of times that write operations
      encountered a full outbound ring buffer:
      1) The total number of write operations that encountered a full
      condition
      2) The number of write operations that were the first to encounter a
      full condition
      
      Increment the outbound full condition counters in the
      hv_ringbuffer_write() function because, for most drivers, a full
      outbound ring buffer is detected in that function. Also increment the
      outbound full condition counters in the set_channel_pending_send_size()
      function. In the hv_sock driver, a full outbound ring buffer is detected
      and set_channel_pending_send_size() is called before
      hv_ringbuffer_write() is called.
      
      I tested this patch by confirming that the sysfs files were created and
      observing the counter values. The values seemed to increase by a
      reasonable amount when the Hyper-v related drivers were in use.
      Signed-off-by: default avatarKimberly Brown <kimbrownkd@gmail.com>
      Reviewed-by: default avatarMichael Kelley <mikelley@microsoft.com>
      Signed-off-by: default avatarSasha Levin <sashal@kernel.org>
      396ae57e
  6. 04 Feb, 2019 2 commits
  7. 01 Feb, 2019 3 commits
  8. 26 Jan, 2019 3 commits
  9. 19 Jan, 2019 1 commit
  10. 16 Jan, 2019 2 commits
  11. 09 Jan, 2019 1 commit
    • Minchan Kim's avatar
      zram: idle writeback fixes and cleanup · 1d69a3f8
      Minchan Kim authored
      This patch includes some fixes and cleanup for idle-page writeback.
      
      1. writeback_limit interface
      
      Now writeback_limit interface is rather conusing.  For example, once
      writeback limit budget is exausted, admin can see 0 from
      /sys/block/zramX/writeback_limit which is same semantic with disable
      writeback_limit at this moment.  IOW, admin cannot tell that zero came
      from disable writeback limit or exausted writeback limit.
      
      To make the interface clear, let's sepatate enable of writeback limit to
      another knob - /sys/block/zram0/writeback_limit_enable
      
      * before:
        while true :
          # to re-enable writeback limit once previous one is used up
          echo 0 > /sys/block/zram0/writeback_limit
          echo $((200<<20)) > /sys/block/zram0/writeback_limit
          ..
          .. # used up the writeback limit budget
      
      * new
        # To enable writeback limit, from the beginning, admin should
        # enable it.
        echo $((200<<20)) > /sys/block/zram0/writeback_limit
        echo 1 > /sys/block/zram/0/writeback_limit_enable
        while true :
          echo $((200<<20)) > /sys/block/zram0/writeback_limit
          ..
          .. # used up the writeback limit budget
      
      It's much strightforward.
      
      2. fix condition check idle/huge writeback mode check
      
      The mode in writeback_store is not bit opeartion any more so no need to
      use bit operations.  Furthermore, current condition check is broken in
      that it does writeback every pages regardless of huge/idle.
      
      3. clean up idle_store
      
      No need to use goto.
      
      [minchan@kernel.org: missed spin_lock_init]
        Link: http://lkml.kernel.org/r/20190103001601.GA255139@google.com
      Link: http://lkml.kernel.org/r/20181224033529.19450-1-minchan@kernel.orgSigned-off-by: default avatarMinchan Kim <minchan@kernel.org>
      Suggested-by: default avatarJohn Dias <joaodias@google.com>
      Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
      Cc: John Dias <joaodias@google.com>
      Cc: Srinivas Paladugu <srnvs@google.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      1d69a3f8
  12. 07 Jan, 2019 1 commit
    • Dan Williams's avatar
      device-dax: Add /sys/class/dax backwards compatibility · 730926c3
      Dan Williams authored
      On the expectation that some environments may not upgrade libdaxctl
      (userspace component that depends on the /sys/class/dax hierarchy),
      provide a default / legacy dax_pmem_compat driver. The dax_pmem_compat
      driver implements the original /sys/class/dax sysfs layout rather than
      /sys/bus/dax. When userspace is upgraded it can blacklist this module
      and switch to the dax_pmem driver going forward.
      
      CONFIG_DEV_DAX_PMEM_COMPAT and supporting code will be deleted according
      to the dax_pmem entry in Documentation/ABI/obsolete/.
      Signed-off-by: default avatarDan Williams <dan.j.williams@intel.com>
      730926c3
  13. 05 Jan, 2019 2 commits
  14. 28 Dec, 2018 4 commits
  15. 17 Dec, 2018 1 commit
    • Damien Le Moal's avatar
      block: update sysfs documentation · f9824952
      Damien Le Moal authored
      Add the description of the zoned, nr_zones and chunk_sectors sysfs queue
      attributes to Documentation/block/queue-sysfs.txt. The description of
      the zoned and chunk_sector attributes are mostly copied from
      ABI/testing/sysfs-block (added a typo fix). While at it, also fix a
      typo in the description of the io_poll_delay attribute.
      
      nr_zones description is also added to ABI/testing/sysfs-block and
      contact email address updated for the zoned attribute.
      Signed-off-by: default avatarDamien Le Moal <damien.lemoal@wdc.com>
      Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
      f9824952
  16. 16 Dec, 2018 2 commits
  17. 12 Dec, 2018 1 commit
  18. 11 Dec, 2018 1 commit
  19. 05 Dec, 2018 1 commit
  20. 01 Dec, 2018 1 commit
  21. 26 Nov, 2018 2 commits
    • Chao Yu's avatar
      f2fs: export migration_granularity sysfs entry · 34655575
      Chao Yu authored
      Add one sysfs entry to control migration granularity of GC in large
      section f2fs, it can be tuned to mitigate heavy overhead of migrating
      huge number of blocks in large section.
      Signed-off-by: default avatarChao Yu <yuchao0@huawei.com>
      Signed-off-by: default avatarJaegeuk Kim <jaegeuk@kernel.org>
      34655575
    • Heikki Krogerus's avatar
      drivers: base: Introducing software nodes to the firmware node framework · 59abd836
      Heikki Krogerus authored
      Software node is a new struct fwnode_handle type that can be
      used to describe devices in kernel (software). It is meant
      to complement fwnodes representing real firmware nodes when
      they are incomplete (for example missing device properties)
      and to supply the primary fwnode when the firmware lacks
      hardware description for a device completely.
      
      The software node type is really meant to replace the
      currently used "property_set" struct fwnode_handle type. The
      handling of struct property_set is glued to the generic
      device property handling code, and it is not possible to
      create a struct property_set independently from the device
      that it is bind to. struct property_set is only created when
      device properties are added to already initialized struct
      device, and control of it is only possible from the generic
      property handling code.
      
      Software nodes are instead designed to be created
      independently from the device entries (struct device). It
      makes them much more flexible, as then the device meant to
      be bind to the node can be created at a later time, and from
      another location. It is also possible to bind multiple
      devices to a single software node if needed.
      
      The software node implementation also includes support for
      node hierarchy, which was the main motivation for this
      commit. The node hierarchy was something that was requested
      for the struct property_set, but it did not seem reasonable
      to try to extend the property_set support for that purpose.
      struct property_set was really meant only for device
      property handling like the name suggests.
      
      Support for struct property_set is not yet removed in this
      commit, but it will be in the following one.
      Signed-off-by: default avatarHeikki Krogerus <heikki.krogerus@linux.intel.com>
      Acked-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Reviewed-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      59abd836
  22. 12 Nov, 2018 1 commit
  23. 07 Nov, 2018 1 commit
  24. 19 Oct, 2018 1 commit
  25. 17 Oct, 2018 1 commit