1. 21 10月, 2020 1 次提交
  2. 17 10月, 2020 1 次提交
  3. 15 10月, 2020 1 次提交
  4. 14 10月, 2020 1 次提交
    • liulangrenaaa's avatar
      mm,kmemleak-test.c: move kmemleak-test.c to samples dir · 1abbef4f
      liulangrenaaa 提交于
      kmemleak-test.c is just a kmemleak test module, which also can not be used
      as a built-in kernel module.  Thus, i think it may should not be in mm
      dir, and move the kmemleak-test.c to samples/kmemleak/kmemleak-test.c.
      Fix the spelling of built-in by the way.
      Signed-off-by: liulangrenaaa's avatarHui Su <sh_def@163.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Jonathan Corbet <corbet@lwn.net>
      Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
      Cc: David S. Miller <davem@davemloft.net>
      Cc: Rob Herring <robh@kernel.org>
      Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Josh Poimboeuf <jpoimboe@redhat.com>
      Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
      Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
      Cc: Divya Indi <divya.indi@oracle.com>
      Cc: Tomas Winkler <tomas.winkler@intel.com>
      Cc: David Howells <dhowells@redhat.com>
      Link: https://lkml.kernel.org/r/20200925183729.GA172837@rlkSigned-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      1abbef4f
  5. 13 10月, 2020 1 次提交
  6. 12 10月, 2020 2 次提交
  7. 11 10月, 2020 1 次提交
  8. 10 10月, 2020 1 次提交
  9. 09 10月, 2020 6 次提交
  10. 08 10月, 2020 3 次提交
    • O
      can: add ISO 15765-2:2016 transport protocol · e057dd3f
      Oliver Hartkopp 提交于
      CAN Transport Protocols offer support for segmented Point-to-Point
      communication between CAN nodes via two defined CAN Identifiers.
      As CAN frames can only transport a small amount of data bytes
      (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
      segmentation is needed to transport longer PDUs as needed e.g. for
      vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
      This protocol driver implements data transfers according to
      ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
      Signed-off-by: NOliver Hartkopp <socketcan@hartkopp.net>
      Link: https://lore.kernel.org/r/20200928200404.82229-1-socketcan@hartkopp.net
      [mkl: Removed "WITH Linux-syscall-note" from isotp.c.
            Fixed indention, a checkpatch warning and typos.
            Replaced __u{8,32} by u{8,32}.
            Removed always false (optlen < 0) check in isotp_setsockopt().]
      Signed-off-by: NMarc Kleine-Budde <mkl@pengutronix.de>
      e057dd3f
    • G
      MAINTAINERS: Update maintainers for pmc_core driver · d0e21c24
      Gayatri Kammela 提交于
      Update MAINTAINERS file for pmc_core driver to reflect the current
      maintainers.
      
      Cc: Vishwanath Somayaji <vishwanath.somayaji@intel.com>
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Srinivas Pandruvada <srinivas.pandruvada@intel.com>
      Cc: David E. Box <david.e.box@linux.intel.com>
      Acked-by: NDavid E. Box <david.e.box@linux.intel.com>
      Acked-by: NVishwanath Somayaji <vishwanath.somayaji@intel.com>
      Signed-off-by: NGayatri Kammela <gayatri.kammela@intel.com>
      Signed-off-by: NDavid E. Box <david.e.box@linux.intel.com>
      Reviewed-by: NAndy Shevchenko <andy.shevchenko@gmail.com>
      Reviewed-by: NRajneesh Bhardwaj <irenic.rajneesh@gmail.com>
      Link: https://lore.kernel.org/r/20201007035108.31078-5-david.e.box@linux.intel.comSigned-off-by: NHans de Goede <hdegoede@redhat.com>
      d0e21c24
    • B
      vfio/fsl-mc: Add VFIO framework skeleton for fsl-mc devices · fb1ff4c1
      Bharat Bhushan 提交于
      DPAA2 (Data Path Acceleration Architecture) consists in
      mechanisms for processing Ethernet packets, queue management,
      accelerators, etc.
      
      The Management Complex (mc) is a hardware entity that manages the DPAA2
      hardware resources. It provides an object-based abstraction for software
      drivers to use the DPAA2 hardware. The MC mediates operations such as
      create, discover, destroy of DPAA2 objects.
      The MC provides memory-mapped I/O command interfaces (MC portals) which
      DPAA2 software drivers use to operate on DPAA2 objects.
      
      A DPRC is a container object that holds other types of DPAA2 objects.
      Each object in the DPRC is a Linux device and bound to a driver.
      The MC-bus driver is a platform driver (different from PCI or platform
      bus). The DPRC driver does runtime management of a bus instance. It
      performs the initial scan of the DPRC and handles changes in the DPRC
      configuration (adding/removing objects).
      
      All objects inside a container share the same hardware isolation
      context, meaning that only an entire DPRC can be assigned to
      a virtual machine.
      When a container is assigned to a virtual machine, all the objects
      within that container are assigned to that virtual machine.
      The DPRC container assigned to the virtual machine is not allowed
      to change contents (add/remove objects) by the guest. The restriction
      is set by the host and enforced by the mc hardware.
      
      The DPAA2 objects can be directly assigned to the guest. However
      the MC portals (the memory mapped command interface to the MC) need
      to be emulated because there are commands that configure the
      interrupts and the isolation IDs which are virtual in the guest.
      
      Example:
      echo vfio-fsl-mc > /sys/bus/fsl-mc/devices/dprc.2/driver_override
      echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind
      
      The dprc.2 is bound to the VFIO driver and all the objects within
      dprc.2 are going to be bound to the VFIO driver.
      
      This patch adds the infrastructure for VFIO support for fsl-mc
      devices. Subsequent patches will add support for binding and secure
      assigning these devices using VFIO.
      
      More details about the DPAA2 objects can be found here:
      Documentation/networking/device_drivers/freescale/dpaa2/overview.rst
      Signed-off-by: NBharat Bhushan <Bharat.Bhushan@nxp.com>
      Signed-off-by: NDiana Craciun <diana.craciun@oss.nxp.com>
      Reviewed-by: NEric Auger <eric.auger@redhat.com>
      Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      fb1ff4c1
  11. 07 10月, 2020 2 次提交
  12. 06 10月, 2020 4 次提交
  13. 05 10月, 2020 2 次提交
  14. 04 10月, 2020 1 次提交
  15. 03 10月, 2020 1 次提交
    • V
      selftests: ocelot: add some example VCAP IS1, IS2 and ES0 tc offloads · 8cd6b020
      Vladimir Oltean 提交于
      Provide an example script which can be used as a skeleton for offloading
      TCAM rules in the Ocelot switches.
      
      Not all actions are demoed, mostly because of difficulty to automate
      this from a single board.
      
      For example, policing. We can set up an iperf3 UDP server and client and
      measure throughput at destination. But at least with DSA setups, network
      namespacing the individual ports is not possible because all switch
      ports are handled by the same DSA master. And we cannot assume that the
      target platform (an embedded board) has 2 other non-switch generator
      ports, we need to work with the generator ports as switch ports (this is
      the reason why mausezahn is used, and not IP traffic like ping). When
      somebody has an idea how to test policing, that can be added to this
      test.
      Signed-off-by: NVladimir Oltean <vladimir.oltean@nxp.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8cd6b020
  16. 02 10月, 2020 4 次提交
  17. 01 10月, 2020 5 次提交
  18. 30 9月, 2020 3 次提交