Remove propmt for selecting MLX5_VDPA by the user and modify
MLX5_VDPA_NET to select MLX5_VDPA. Also modify MLX5_VDPA_NET to depend
on mlx5_core.
This fixes an issue where configuration sets 'y' for MLX5_VDPA_NET while
MLX5_CORE is compiled as a module causing link errors.
Reported-by: kernel tes
On Tue, 2020-10-06 at 10:10 +0300, Kalle Valo wrote:
> Lee Jones writes:
>
> > On Tue, 06 Oct 2020, Kalle Valo wrote:
> >
> > > Lee Jones writes:
> > >
> > > > On Thu, 10 Sep 2020, Lee Jones wrote:
> > > >
> > > > > This is a rebased/re-worked set of patches which have been
> > > > > previous
When CONFIG_NET is not defined, I hit the following build error:
kernel/trace/bpf_trace.o:(.rodata+0x110): undefined reference to
`bpf_prog_test_run_raw_tp'
Commit 1b4d60ec162f ("bpf: Enable BPF_PROG_TEST_RUN for raw_tracepoint")
added test_run support for raw_tracepoint in /kernel/trace/bpf_
On Tue, Oct 06, 2020 at 06:26:18AM -0700, David Miller wrote:
> From: Johannes Berg
> Date: Tue, 06 Oct 2020 08:43:17 +0200
>
> > On Mon, 2020-10-05 at 15:07 -0700, Jakub Kicinski wrote:
> >> Hi!
> >>
> >> This series wires up ethtool policies to ops, so they can be
> >> dumped to user space for f
Firmware live patch event notifies the driver that the firmware was just
updated using live patch. In such case the driver should not reload or
re-initiate entities, part to updating the firmware version and
re-initiate the firmware tracer which can be updated by live patch with
new strings databas
Add devlink reload rst documentation file.
Update index file to include it.
Signed-off-by: Moshe Shemesh
---
v1 -> v2:
- Split first paragraph of devlink reload description to 2 sentences
RFCv5 -> v1:
- Rename reload_action_limit_level to reload_limit
RFCv4 -> RFCv5:
- Rephrase namespace change s
Add support for devlink reload action fw_activate with reload limit
no_reset which does firmware live patching, updating the firmware image
without reset, no downtime and no configuration lose. The driver checks
if the firmware is capable of handling the pending firmware changes as a
live patch. If
On 10/6/20 7:16 PM, Randy Dunlap wrote:
Fix build errors in kernel/bpf/verifier.c when CONFIG_NET is
not enabled.
../kernel/bpf/verifier.c:3995:13: error: ‘btf_sock_ids’ undeclared here (not in
a function); did you mean ‘bpf_sock_ops’?
.btf_id = &btf_sock_ids[BTF_SOCK_TYPE_SOCK_COMMON],
On 10/2/20 6:22 AM, Antony Antony wrote:
> The XFRMA_SET_MARK_MASK attribute can be set in states (4.19+)
> It is optional and the kernel default is 0x
> It is the mask of XFRMA_SET_MARK(a.k.a. XFRMA_OUTPUT_MARK in 4.18)
>
> e.g.
> ./ip/ip xfrm state add output-mark 0x6 mask 0xab proto esp
On 10/1/20 12:21 AM, Jiri Pirko wrote:
> From: Jiri Pirko
>
> Add health reporter test command and allow user to trigger a test event.
>
> Signed-off-by: Jiri Pirko
> ---
> bash-completion/devlink | 2 +-
> devlink/devlink.c | 11 +++
> man/man8/devlink-health.8 | 16 +++
On 9/30/20 2:05 PM, Jacob Keller wrote:
> The recently added DEVLINK_ATTR_FLASH_UPDATE_OVERWRITE_MASK allows
> userspace to indicate how a device should handle subsections of a flash
> component when updating. For example, a flash component might contain
> vital data such as PCIe serial number or c
Add devlink reload action to allow the user to request a specific reload
action. The action parameter is optional, if not specified then devlink
driver re-init action is used (backward compatible).
Note that when required to do firmware activation some drivers may need
to reload the driver. On the
Set capability to notify the firmware that this host driver is capable
of handling pci sync for firmware update events.
Signed-off-by: Moshe Shemesh
Reviewed-by: Saeed Mahameed
---
drivers/net/ethernet/mellanox/mlx5/core/main.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/
On sync_reset_now event the driver does reload and PCI link toggle to
activate firmware upgrade reset. When the firmware sends this event it
syncs the event on all PFs, so all PFs will do PCI link toggle at once.
To do PCI link toggle, the driver ensures that no other device ID under
the same bridg
Add reload limit to demand restrictions on reload actions.
Reload limits supported:
no_reset: No reset allowed, no down time allowed, no link flap and no
configuration is lost.
By default reload limit is unspecified and so no constraints on reload
actions are required.
Some combinations
If firmware sends sync_reset_abort to driver the driver should clear the
reset requested mode as reset is not expected any more.
Signed-off-by: Moshe Shemesh
Reviewed-by: Saeed Mahameed
---
.../net/ethernet/mellanox/mlx5/core/fw_reset.c| 15 +++
1 file changed, 15 insertions(+)
Change devlink_reload_supported() function to get devlink_ops pointer
param instead of devlink pointer param.
This change will be used in the next patch to check if devlink reload is
supported before devlink instance is allocated.
Signed-off-by: Moshe Shemesh
Reviewed-by: Jakub Kicinski
Reviewed
Add reload stats to hold the history per reload action type and limit.
For example, the number of times fw_activate has been performed on this
device since the driver module was added or if the firmware activation
was performed with or without reset.
Add devlink notification on stats update.
Exp
Add functions to query and set the MFRL reset options supported by
firmware.
Signed-off-by: Moshe Shemesh
Reviewed-by: Saeed Mahameed
---
RFCv5 -> v1:
- Renamed non-static functions to have module prefix
---
.../net/ethernet/mellanox/mlx5/core/Makefile | 2 +-
.../ethernet/mellanox/mlx5/core/
Add remote reload stats to hold the history of actions performed due
devlink reload commands initiated by remote host. For example, in case
firmware activation with reset finished successfully but was initiated
by remote host.
The function devlink_remote_reload_actions_performed() is exported to
e
The enable_remote_dev_reset devlink param flags that the host admin
allows device resets that can be initiated by other hosts. This
parameter is useful for setups where a device is shared by different
hosts, such as multi-host setup. Once the user set this parameter to
false, the driver should NACK
Once the driver gets sync_reset_request from firmware it prepares for the
coming reset and sends acknowledge.
After getting this event the driver expects device reset, either it will
trigger PCI reset on sync_reset_now event or such PCI reset will be
triggered by another PF of the same device. So i
Add support for devlink reload action fw_activate. To activate firmware
image the mlx5 driver resets the firmware and reloads it from flash. If
a new image was stored on flash it will be loaded. Once this reload
command is executed the driver initiates fw sync reset flow, where the
firmware synchro
Introduce new options on devlink reload API to enable the user to select
the reload action required and constrains limits on these actions that he
may want to ensure. Complete support for reload actions in mlx5.
The following reload actions are supported:
driver_reinit: driver entities re-initial
The enable_remote_dev_reset devlink param flags that the host admin
allows resets by other hosts. In case it is cleared mlx5 host PF driver
will send NACK on pci sync for firmware update reset request and the
command will fail.
By default enable_remote_dev_reset parameter is true, so pci sync for
f
On 9/30/20 4:40 PM, Jacob Keller wrote:
> @@ -3124,12 +3140,19 @@ static int cmd_dev_flash_status_cb(const struct
> nlmsghdr *nlh, void *data)
> done =
> mnl_attr_get_u64(tb[DEVLINK_ATTR_FLASH_UPDATE_STATUS_DONE]);
> if (tb[DEVLINK_ATTR_FLASH_UPDATE_STATUS_TOTAL])
>
On 10/5/2020 10:12 PM, Jacob Keller wrote:
On 10/4/2020 12:09 AM, Moshe Shemesh wrote:
On 10/3/2020 12:05 PM, Jiri Pirko wrote:
Thu, Oct 01, 2020 at 03:59:08PM CEST, mo...@mellanox.com wrote:
Add remote reload stats to hold the history of actions performed due
devlink reload commands initia
On Tue, Oct 06, 2020 at 09:42:18PM -0700, Andrii Nakryiko wrote:
> > I see it differently.
> > I don't like moving if (reg->id) into find_equal_scalars(). Otherwise it
> > would
> > have to be named something like try_find_equal_scalars(). And even with such
> > "try_" prefix it's still not clean.
On Tue, Oct 6, 2020 at 9:15 PM Alexei Starovoitov
wrote:
>
> On Tue, Oct 06, 2020 at 08:31:23PM -0700, Andrii Nakryiko wrote:
> >
> > > 'linked' is also wrong. The regs are exactly equal.
> > > In case of pkt and other pointers two regs will have the same id
> > > as well, but they will not be equ
Hi,
This patch is to fix the kernel error
[ 46.271811] debugfs: File 'force_bredr_smp' in directory 'hci0'
already present!
When powering off and on the bluetooth, the smp_register will try to create the
force_bredr_smp entry again.
Move the creation to hci_debugfs_create_bredr so the force_bre
On Tue, Oct 06, 2020 at 08:31:23PM -0700, Andrii Nakryiko wrote:
>
> > 'linked' is also wrong. The regs are exactly equal.
> > In case of pkt and other pointers two regs will have the same id
> > as well, but they will not be equal. Here these two scalars are equal
> > otherwise doing *reg = *know
Based on RFC 8200, Section 4.5 Fragment Header:
- If the first fragment does not include all headers through an
Upper-Layer header, then that fragment should be discarded and
an ICMP Parameter Problem, Code 3, message should be sent to
the source of the fragment, with the Pointer
When our Engineer run latest IPv6 Core Conformance test, test v6LC.1.3.6:
First Fragment Doesn’t Contain All Headers[1] failed. The test purpose is to
verify that the node(Linux for example) should properly process IPv6 packets
that don’t include all the headers through the Upper-Layer header.
B
Based on RFC7112, Section 6:
IANA has added the following "Type 4 - Parameter Problem" message to
the "Internet Control Message Protocol version 6 (ICMPv6) Parameters"
registry:
CODE NAME/DESCRIPTION
3 IPv6 First Fragment has incomplete IPv6 Header Chain
Signed-of
In nl80211_parse_key(), key.idx is first initialized as -1.
If this value of key.idx remains unmodified and gets returned, and
nl80211_key_allowed() also returns 0, then rdev_del_key() gets called
with key.idx = -1.
This causes an out-of-bounds array access.
Handle this issue by checking if the
On Tue, Oct 6, 2020 at 1:10 PM Alexei Starovoitov
wrote:
>
> From: Yonghong Song
>
> Under register pressure the llvm may spill registers with bounds into the
> stack.
> The verifier has to track them through spill/fill otherwise many kinds of
> bound
> errors will be seen. The spill/fill of in
On Tue, Oct 6, 2020 at 7:18 PM Alexei Starovoitov
wrote:
>
> On Tue, Oct 06, 2020 at 06:56:14PM -0700, Andrii Nakryiko wrote:
> > On Tue, Oct 6, 2020 at 1:14 PM Alexei Starovoitov
> > wrote:
> > >
> > > From: Alexei Starovoitov
> > >
> > > The llvm register allocator may use two different regist
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 6 Oct 2020 19:28:57 -0700 you wrote:
> Commit 4976b718c355 ("bpf: Introduce pseudo_btf_id") switched
> the order of check_subprogs() and resolve_pseudo_ldimm() in
> the verifier. Now an empty prog expects to see the e
On Tue, Oct 6, 2020 at 12:21 PM Leon Romanovsky wrote:
>
> On Tue, Oct 06, 2020 at 05:41:00PM +, Saleem, Shiraz wrote:
> > > Subject: Re: [PATCH v2 1/6] Add ancillary bus support
> > >
> > > On Tue, Oct 06, 2020 at 05:09:09PM +, Parav Pandit wrote:
> > > >
> > > > > From: Leon Romanovsky
On Tue, Oct 06, 2020 at 06:56:14PM -0700, Andrii Nakryiko wrote:
> On Tue, Oct 6, 2020 at 1:14 PM Alexei Starovoitov
> wrote:
> >
> > From: Alexei Starovoitov
> >
> > The llvm register allocator may use two different registers representing the
> > same virtual register. In such case the following
Fix build errors in kernel/bpf/verifier.c when CONFIG_NET is
not enabled.
../kernel/bpf/verifier.c:3995:13: error: ‘btf_sock_ids’ undeclared here (not in
a function); did you mean ‘bpf_sock_ops’?
.btf_id = &btf_sock_ids[BTF_SOCK_TYPE_SOCK_COMMON],
../kernel/bpf/verifier.c:3995:26: error: ‘BTF_
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/rxrpc/conn_event.c
between commit:
fa1d113a0f96 ("rxrpc: Fix some missing _bh annotations on locking
conn->state_lock")
from the net tree and commit:
245500d853e9 ("rxrpc: Rewrite the client connection manager
On Tue, Oct 06, 2020 at 06:23:13PM -0700, Hao Luo wrote:
> Commit 4976b718c355 ("bpf: Introduce pseudo_btf_id") switched
> the order of check_subprogs() and resolve_pseudo_ldimm() in
> the verifier. Now an empty prog expects to see the error "last
> insn is not an the prog of a single invalid ldimm
On Tue, Oct 6, 2020 at 1:14 PM Alexei Starovoitov
wrote:
>
> From: Alexei Starovoitov
>
> The llvm register allocator may use two different registers representing the
> same virtual register. In such case the following pattern can be observed:
> 1047: (bf) r9 = r6
> 1048: (a5) if r6 < 0x1000 goto
On Tue, Oct 6, 2020 at 6:22 PM Jakub Kicinski wrote:
>
> On Tue, 6 Oct 2020 13:09:55 -0700 Alexei Starovoitov wrote:
> > +static ino_t get_inode_from_kernfs(struct kernfs_node* node)
>
> nit: my bot suggests this may be missing an "INLINE" since it's a
> static function in a header
false po
On Tue, 6 Oct 2020 13:09:55 -0700 Alexei Starovoitov wrote:
> +static ino_t get_inode_from_kernfs(struct kernfs_node* node)
nit: my bot suggests this may be missing an "INLINE" since it's a
static function in a header
> +{
> + struct kernfs_node___52* node52 = (void*)node;
> +
> + i
On Tue, 6 Oct 2020 18:33:02 +0200 Jesper Dangaard Brouer wrote:
> > +static const struct bpf_func_proto bpf_xdp_mtu_lookup_proto = {
> > + .func = bpf_xdp_mtu_lookup,
> > + .gpl_only = true,
> > + .ret_type = RET_INTEGER,
> > + .arg1_type = ARG_PTR_TO_CTX,
> > +
On Tue, Oct 6, 2020 at 5:51 PM Hao Luo wrote:
>
> On Tue, Oct 6, 2020 at 5:43 PM Andrii Nakryiko
> wrote:
> >
> > On Tue, Oct 6, 2020 at 4:45 PM Hao Luo wrote:
> > >
> > > Commit 4976b718c355 ("bpf: Introduce pseudo_btf_id") switched
> > > the order of check_subprogs() and resolve_pseudo_ldimm()
On Tue, Oct 6, 2020 at 4:45 PM Hao Luo wrote:
>
> Commit 4976b718c355 ("bpf: Introduce pseudo_btf_id") switched
> the order of check_subprogs() and resolve_pseudo_ldimm() in
> the verifier. Now an empty prog and the prog of a single
> invalid ldimm expect to see the error "last insn is not an
> ex
Hi Jesper,
I love your patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url:
https://github.com/0day-ci/linux/commits/Jesper-Dangaard-Brouer/bpf-New-approach-for-BPF-MTU-handling-and-enforcement/20201007-000903
base: https://git.kernel.org/pub/scm/linux/ker
From: Fabian Frederick
When some test directly done with check_one_counter() fails,
counter variable is undefined. This patch calls ip with cname
which avoids errors like:
FAIL: oskuidcounter, want "packets 2", got
Error: syntax error, unexpected newline, expecting string
list counter inet filter
Hi,
The following patchset contains Netfilter selftests fixes from
Fabian Frederick:
1) Extend selftest nft_meta.sh to check for meta cpu.
2) Fix selftest nft_meta.sh error reporting.
3) Fix shellcheck warnings in selftest nft_meta.sh.
4) Extend selftest nft_meta.sh to check for meta time.
Pl
From: Fabian Frederick
cnt was not used in nft_meta.sh
This patch also fixes 2 shellcheck SC2181 warnings:
"check exit code directly with e.g. 'if mycmd;', not indirectly with
$?."
Signed-off-by: Fabian Frederick
Signed-off-by: Pablo Neira Ayuso
---
tools/testing/selftests/netfilter/nft_meta.
From: Fabian Frederick
Check packets are correctly placed in current year.
Also do a NULL check for another one.
Signed-off-by: Fabian Frederick
Signed-off-by: Pablo Neira Ayuso
---
tools/testing/selftests/netfilter/nft_meta.sh | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
From: Fabian Frederick
run task on first CPU with netfilter counters reset and check
cpu meta after another ping
Signed-off-by: Fabian Frederick
Acked-by: Florian Westphal
Signed-off-by: Pablo Neira Ayuso
---
tools/testing/selftests/netfilter/nft_meta.sh | 14 ++
1 file changed,
On Tue, 6 Oct 2020, Davide Caratti wrote:
using packetdrill it's possible to observe the same MPTCP DSN being acked
by different subflows with DACK4 and DACK8. This is in contrast with what
specified in RFC8684 §3.3.2: if an MPTCP endpoint transmits a 64-bit wide
DSN, it MUST be acknowledged wit
On Sat, 2020-10-03 at 12:10 +0100, Alex Dewar wrote:
> Commit ff7ea04ad579 ("net/mlx5e: Fix potential null pointer
> dereference")
> added some missing null checks but the error handling in
> mlx5e_alloc_flow() was left broken: the variable attr is passed to
> kfree
> although it is never assigned
On Tue, 2020-10-06 at 19:12 +0100, Colin King wrote:
> From: Colin Ian King
>
> Currently the error exit path err_free kfree's attr. In the case
> where
> flow and parse_attr failed to be allocated this return path will free
> the uninitialized pointer attr, which is not correct. In the other
>
On Tue, 6 Oct 2020, Paolo Abeni wrote:
If recvmsg() and the workqueue race to dequeue the data
pending on some subflow, the current mapping for such
subflow covers several skbs and some of them have not
reached yet the received, either the worker or recvmsg()
can find a subflow with the data_ava
On 10/6/20 11:11 PM, Florian Fainelli wrote:
>
>
> On 10/6/2020 1:24 PM, Marek Vasut wrote:
>> On 10/6/20 9:36 PM, Florian Fainelli wrote:
>> [...]
- Use compatible ("compatible = "ethernet-phy-id0022.1560") in the
devicetree,
so that reading the PHYID is not needed
-
Hi Linus,
I love your patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Linus-Walleij/net-dsa-rtl8366rb-Roof-MTU-for-switch/20201007-033703
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
9fae
On Sat, 3 Oct 2020 16:10:05 +0200
Adel Belhouane wrote:
> These were reported as IPv6-only and ignored:
>
> # ip address add 192.0.2.2/24 dev dummy5 noprefixroute
> Warning: noprefixroute option can be set only for IPv6 addresses
> # ip address add 224.1.1.10/24 dev dummy5 autojoi
On Fri, 2 Oct 2020 12:34:28 +0300
Eyal Birger wrote:
> Used for tracking neighbour table overflows.
>
> Signed-off-by: Eyal Birger
Looks good, wonder why it wasn't there already.
Applied.
On 10/6/20 11:09 PM, Florian Fainelli wrote:
>
>
> On 10/6/2020 1:20 PM, Marek Vasut wrote:
>> The phy_reset_after_clk_enable() is always called with ndev->phydev,
>> however that pointer may be NULL even though the PHY device instance
>> already exists and is sufficient to perform the PHY reset.
On Sun, 4 Oct 2020 11:42:59 +
Samanta Navarro wrote:
Looks good overall.
Take the "a" off in the gso_max_segs part.
Please resubmit this patch with proper Developer's Certificate of Origin
(a.k.a. Signed-off-by).
On Sun, Oct 04, 2020 at 03:22:09PM +, Alex Belits wrote:
>
> On Thu, 2020-10-01 at 16:44 +0200, Frederic Weisbecker wrote:
> > > @@ -268,7 +269,8 @@ static void tick_nohz_full_kick(void)
> > > */
> > > void tick_nohz_full_kick_cpu(int cpu)
> > > {
> > > - if (!tick_nohz_full_cpu(cpu))
> >
available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git
tags/linux-can-fixes-for-5.9-20201006
for you to fetch changes up to 81f1f5ae8b3cbd54fdd994c9e9aacdb7b414a802:
can: m_can_platform: don't call m_can_class_suspend in runtime suspend
(
From: Lucas Stach
0704c5743694 can: m_can_platform: remove unnecessary m_can_class_resume()
call
removed the m_can_class_resume() call in the runtime resume path to get
rid of a infinite recursion, so the runtime resume now only handles the device
clocks.
Unfortunately it did not remove th
RDS/IB tries to refill the recv buffer in softirq context using
GFP_NOWAIT flag. However alloc failure is handled by queueing a work to
refill the recv buffer with GFP_KERNEL flag. This means failure to
allocate with GFP_NOWAIT isn't fatal. Do not print the PAF warnings if
softirq context fails to
When processing a system suspend request we suspend modem endpoints
if they are enabled, and call ipa_cmd_tag_process() (which issues
IPA commands) to ensure the IPA pipeline is cleared. It is an error
to attempt to issue an IPA command before setup is complete, so this
is clearly a bug. But we a
In the setup phase of initialization, GSI firmware gets loaded
and initialized, and the AP command TX and default RX endpoints
get set up. Until that happens, IPA commands must not be issued
to the hardware.
If the modem crashes, we stop endpoint channels and perform a
number of other activities
This series fixes two bugs that occur if the IPA driver has not
completed its setup phase of initialization when an event occurs.
One event is the crash of the modem. If the modem crashes,
ipa_modem_crashed() is called, and it performs various activities
intended to put the IPA hardware into a go
On 10/6/2020 1:24 PM, Marek Vasut wrote:
On 10/6/20 9:36 PM, Florian Fainelli wrote:
[...]
- Use compatible ("compatible = "ethernet-phy-id0022.1560") in the
devicetree,
so that reading the PHYID is not needed
- easy to solve.
Disadvantage:
- losing PHY auto-detection capabili
On 10/6/2020 1:20 PM, Marek Vasut wrote:
The phy_reset_after_clk_enable() is always called with ndev->phydev,
however that pointer may be NULL even though the PHY device instance
already exists and is sufficient to perform the PHY reset.
If the PHY still is not bound to the MAC, but there is
On Sat, Oct 03, 2020 at 12:07:28AM +0300, Ioana Ciornei wrote:
> Add a documentation entry for the DTS bindings needed and supported by
> the dpaa2-mac driver.
>
> Signed-off-by: Ioana Ciornei
> ---
> Changes in v2:
> - new patch
>
> .../devicetree/bindings/net/dpaa2-mac.yaml| 55 +
From: Marek Vasut
Sent: Tuesday, October 6, 2020 10:20 PM
> The phy_reset_after_clk_enable() is always called with ndev->phydev,
> however that pointer may be NULL even though the PHY device instance
> already exists and is sufficient to perform the PHY reset.
>
> If the PHY still is not bound t
On Tue, 6 Oct 2020 17:56:51 +0200 Christian Eggers wrote:
> Fixes: 7c6ff470aa ("net: dsa: microchip: add MIB counter reading support")
Fixes tag: Fixes: 7c6ff470aa ("net: dsa: microchip: add MIB counter reading
support")
Has these problem(s):
- SHA1 should be at least 12 digits long
On 9/28/20 10:04 PM, Oliver Hartkopp wrote:
> 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
On 10/6/20 9:36 PM, Florian Fainelli wrote:
[...]
>> - Use compatible ("compatible = "ethernet-phy-id0022.1560") in the
>> devicetree,
>> so that reading the PHYID is not needed
>> - easy to solve.
>> Disadvantage:
>> - losing PHY auto-detection capability
>> - need a new devicetree
The phy_reset_after_clk_enable() is always called with ndev->phydev,
however that pointer may be NULL even though the PHY device instance
already exists and is sufficient to perform the PHY reset.
If the PHY still is not bound to the MAC, but there is OF PHY node
and a matching PHY device instance
/kernel/git/bpf/bpf-next.git master
config: s390-randconfig-r026-20201006 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
1127662c6dc2a276839c75a42238b11a3ad00f32)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp
In all cases I've seen eth_type_trans() is used as in the new helper.
Biggest benefit is improved readability when replacing statements like
the following:
desc->skb->protocol = eth_type_trans(desc->skb, priv->dev);
Coccinelle tells me that using the new helper tree-wide would touch
313 files. The
From: Alexei Starovoitov
Make two verifier improvements:
- The llvm register allocator may use two different registers representing the
same virtual register. Teach the verifier to recognize that.
- Track bounded scalar spill/fill.
The 'profiler' test in patch 3 will fail to load without patches
From: Alexei Starovoitov
The main purpose of the profiler test to check different llvm generation
patterns to make sure the verifier can load these large programs.
Note that profiler.inc.h test doesn't follow strict kernel coding style.
The code was formatted in kernel style, but variable declar
From: Alexei Starovoitov
The llvm register allocator may use two different registers representing the
same virtual register. In such case the following pattern can be observed:
1047: (bf) r9 = r6
1048: (a5) if r6 < 0x1000 goto pc+1
1050: ...
1051: (a5) if r9 < 0x2 goto pc+66
1052: ...
1053: (bf)
From: Yonghong Song
Under register pressure the llvm may spill registers with bounds into the stack.
The verifier has to track them through spill/fill otherwise many kinds of bound
errors will be seen. The spill/fill of induction variables was already
happening. This patch extends this logic from
On 2020-08-21 16:13, Paul Moore wrote:
> On Fri, Aug 7, 2020 at 1:10 PM Richard Guy Briggs wrote:
> > On 2020-07-05 11:11, Paul Moore wrote:
> > > On Sat, Jun 27, 2020 at 9:23 AM Richard Guy Briggs
> > > wrote:
> > > > Require the target task to be a descendant of the container
> > > > orchestra
On Wed, Oct 7, 2020 at 12:22 AM Florian Westphal wrote:
>
> Numan Siddique wrote:
> > On Tue, Oct 6, 2020 at 4:46 PM Florian Westphal wrote:
> > >
> > > nusid...@redhat.com wrote:
> > > > From: Numan Siddique
> > > >
> > > > For a tcp packet which is part of an existing committed connection,
>
On Tue, Oct 06, 2020 at 10:39:13PM +0300, Ido Schimmel wrote:
> On Tue, Oct 06, 2020 at 08:04:24AM -0700, Jakub Kicinski wrote:
> > Older kernels don't support statistics, to avoid retries
> > make use of netlink policy dumps to figure out which
> > flags kernel actually supports.
>
> Thanks for w
On Tue, Oct 06, 2020 at 08:04:24AM -0700, Jakub Kicinski wrote:
> Older kernels don't support statistics, to avoid retries
> make use of netlink policy dumps to figure out which
> flags kernel actually supports.
Thanks for working on this, Jakub.
Michal, should I try something similar for the leg
On 10/6/2020 1:04 AM, Oleksij Rempel wrote:
Hello PHY experts,
Short version:
what is the proper way to handle the PHY reset before identifying PHY?
Long version:
I stumbled over following issue:
If PHY reset is registered within PHY node. Then, sometimes, we will not be
able to identify it
On 9/14/20 10:49 AM, Michal Simek wrote:
> Hi,
>
> recently some small patches come to our internal tree. We started to use
> coverity which found 2 issues (last two patches) which is simply to fix.
>
> Thanks,
> Michal
>
>
> Srinivas Neeli (3):
> can: xilinx_can: Limit CANFD brp to 2
> can
The MTU setting for this DSA switch is global so we need
to keep track of the MTU set for each port, then as soon
as any MTU changes, roof the MTU to the biggest common
denominator and poke that into the switch MTU setting.
To achieve this we need a per-chip-variant state container
for the RTL8366
On 10/5/20 10:13 AM, Lad Prabhakar wrote:
> Hi All,
>
> I am re-sending this patch set as this has been missed previously.
> It is exactly same as [1].
>
> DT maintainers have already acked the patches.
>
> [1] https://www.spinics.net/lists/netdev/msg679244.html
>
> Cheers,
> Prabhakar
>
> Cha
On Tue, Oct 06, 2020 at 05:41:00PM +, Saleem, Shiraz wrote:
> > Subject: Re: [PATCH v2 1/6] Add ancillary bus support
> >
> > On Tue, Oct 06, 2020 at 05:09:09PM +, Parav Pandit wrote:
> > >
> > > > From: Leon Romanovsky
> > > > Sent: Tuesday, October 6, 2020 10:33 PM
> > > >
> > > > On Tue
On 10/6/20 9:36 AM, Lad, Prabhakar wrote:
> On Tue, Aug 25, 2020 at 3:21 AM Rob Herring wrote:
>>
>> On Sun, 16 Aug 2020 20:07:31 +0100, Lad Prabhakar wrote:
>>> Document RZ/G1H (r8a7742) SoC specific bindings. The R8A7742 CAN module
>>> is identical to R-Car Gen2 family.
>>>
>>> No driver change
From: Marek Vasut
Sent: Tuesday, October 6, 2020 3:53 PM
> The phy_reset_after_clk_enable() does a PHY reset, which means the PHY
> loses its register settings. The fec_enet_mii_probe() starts the PHY
> and does the necessary calls to configure the PHY via PHY framework,
> and loads the correct r
On Tue, Sep 29, 2020 at 4:50 PM Hao Luo wrote:
>
> - ret = replace_map_fd_with_map_ptr(env);
> - if (ret < 0)
> - goto skip_full_check;
> -
> if (bpf_prog_is_dev_bound(env->prog->aux)) {
> ret = bpf_prog_offload_verifier_prep(env->prog);
>
This is the implementation of CFM netlink configuration
and status information interface.
Add new nested netlink attributes. These attributes are used by the
user space to create/delete/configure CFM instances and get status.
Also they are used by the kernel to notify the user space when changes
i
This is the implementation of Netlink notifications out of CFM.
Notifications are initiated whenever a state change happens in CFM.
IFLA_BRIDGE_CFM:
Points to the CFM information.
IFLA_BRIDGE_CFM_MEP_STATUS_INFO:
This indicate that the MEP instance status are following.
IFLA_BRIDGE_CFM_C
1 - 100 of 259 matches
Mail list logo
