1. 15 5月, 2018 2 次提交
    • S
      bpf: add selftest for stackmap with build_id in NMI context · 13790d1c
      Song Liu 提交于
      This new test captures stackmap with build_id with hardware event
      PERF_COUNT_HW_CPU_CYCLES.
      
      Because we only support one ips-to-build_id lookup per cpu in NMI
      context, stack_amap will not be able to do the lookup in this test.
      Therefore, we didn't do compare_stack_ips(), as it will alwasy fail.
      
      urandom_read.c is extended to run configurable cycles so that it can be
      caught by the perf event.
      Signed-off-by: NSong Liu <songliubraving@fb.com>
      Signed-off-by: NDaniel Borkmann <daniel@iogearbox.net>
      13790d1c
    • S
      bpf: enable stackmap with build_id in nmi context · bae77c5e
      Song Liu 提交于
      Currently, we cannot parse build_id in nmi context because of
      up_read(&current->mm->mmap_sem), this makes stackmap with build_id
      less useful. This patch enables parsing build_id in nmi by putting
      the up_read() call in irq_work. To avoid memory allocation in nmi
      context, we use per cpu variable for the irq_work. As a result, only
      one irq_work per cpu is allowed. If the irq_work is in-use, we
      fallback to only report ips.
      
      Cc: Alexei Starovoitov <ast@kernel.org>
      Cc: Daniel Borkmann <daniel@iogearbox.net>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Signed-off-by: NSong Liu <songliubraving@fb.com>
      Signed-off-by: NDaniel Borkmann <daniel@iogearbox.net>
      bae77c5e
  2. 11 5月, 2018 21 次提交
  3. 10 5月, 2018 6 次提交
  4. 09 5月, 2018 9 次提交
  5. 08 5月, 2018 2 次提交
    • D
      Merge branch 'bnxt_en-Fixes-for-net-next' · 8d42eada
      David S. Miller 提交于
      Michael Chan says:
      
      ====================
      bnxt_en: Fixes for net-next.
      
      This series includes a bug fix for a regression in firmware message polling
      introduced recently on net-next.  There are 3 additional minor fixes for
      unsupported link speed checking, VF MAC address handling, and setting
      PHY eeprom length.
      ====================
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8d42eada
    • M
      bnxt_en: Always forward VF MAC address to the PF. · 707e7e96
      Michael Chan 提交于
      The current code already forwards the VF MAC address to the PF, except
      in one case.  If the VF driver gets a valid MAC address from the firmware
      during probe time, it will not forward the MAC address to the PF,
      incorrectly assuming that the PF already knows the MAC address.  This
      causes "ip link show" to show zero VF MAC addresses for this case.
      
      This assumption is not correct.  Newer firmware remembers the VF MAC
      address last used by the VF and provides it to the VF driver during
      probe.  So we need to always forward the VF MAC address to the PF.
      
      The forwarded MAC address may now be the PF assigned MAC address and so we
      need to make sure we approve it for this case.
      Signed-off-by: NMichael Chan <michael.chan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      707e7e96