summaryrefslogtreecommitdiff
path: root/drivers/net/ethernet/realtek
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2023-10-14 03:26:39 +0300
committerJakub Kicinski <kuba@kernel.org>2023-10-14 03:26:40 +0300
commit1efddc064e1802ceb995c8f51b3a9135af79f7cd (patch)
treec2c49583d1ec5a2dc331b5238f0756d3e15a4555 /drivers/net/ethernet/realtek
parent220dd227ca3aec6ab65fcdfd4549ce12fe326249 (diff)
parent7eeb84d89f2e561ac5b97e0142c029908ddf00d5 (diff)
downloadlinux-1efddc064e1802ceb995c8f51b3a9135af79f7cd.tar.xz
Merge branch 'net-netconsole-configfs-entries-for-boot-target'
Breno Leitao says: ==================== net: netconsole: configfs entries for boot target There is a limitation in netconsole, where it is impossible to disable or modify the target created from the command line parameter. (netconsole=...). "netconsole" cmdline parameter sets the remote IP, and if the remote IP changes, the machine needs to be rebooted (with the new remote IP set in the command line parameter). This allows the user to modify a target without the need to restart the machine. This functionality sits on top of the dynamic target reconfiguration that is already implemented in netconsole. The way to modify a boot time target is creating special named configfs directories, that will be associated with the targets coming from `netconsole=...`. Example: Let's suppose you have two netconsole targets defined at boot time:: netconsole=4444@10.0.0.1/eth1,9353@10.0.0.2/12:34:56:78:9a:bc;4444@10.0.0.1/eth1,9353@10.0.0.3/12:34:56:78:9a:bc You can modify these targets in runtime by creating the following targets:: $ mkdir cmdline1 $ cat cmdline1/remote_ip 10.0.0.3 $ echo 0 > cmdline1/enabled $ echo 10.0.0.4 > cmdline1/remote_ip $ echo 1 > cmdline1/enabled ==================== Link: https://lore.kernel.org/r/20231012111401.333798-1-leitao@debian.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/ethernet/realtek')
0 files changed, 0 insertions, 0 deletions