search for: devlinks

On Mon, Nov 02, 2020 at 05:07:59AM +0000, Parav Pandit wrote: > > > > From: Leon Romanovsky <leon at kernel.org> > > Sent: Monday, November 2, 2020 1:46 AM > > > > From: Leon Romanovsky <leonro at nvidia.com> > > > > Remove exposed driver version as it was done in other drivers, so module > > version will work correctly by displaying the

On 2020/8/11 ??7:58, Eli Cohen wrote: > On Tue, Aug 11, 2020 at 11:26:20AM +0000, Eli Cohen wrote: >> Hi All >> >> Currently, the only statistics we get for a VDPA instance comes from the virtio_net device instance. Since VDPA involves hardware acceleration, there can be quite a lot of information that can be fetched from the underlying device. Currently there is no generic

On Fri, 27 Jan 2023 07:26:13 +0200 Leon Romanovsky wrote: > > That'd be my preference too, FWIW. It's only the offload cases which > > need this sort of fallback. > > Of course not, almost any error unwind path which sets extack will need it. I guess we can come up with scenarios where the new behavior would be useful. But the fact is - your patch changes 4 places...

I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty). With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk (not cdrom) and only administrators can mount it. I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing. Is possible use cdrom on linux domU pv full working where also normal user can mount it without

...MINOR=64 E: DEVNAME=/dev/input/event0 E: SUBSYSTEM=input E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_SERIAL=noserial E: ID_PATH=platform-i8042-serio-0 E: XKBMODEL=pc105 E: XKBLAYOUT=fr E: XKBVARIANT=latin9 E: XKBOPTIONS=lv3:ralt_switch E: x11_driver=evdev E: DMI_VENDOR=Dell Inc. E: DEVLINKS=/dev/char/13:64 /dev/input/by-path/platform-i8042-serio-0-event-kbd P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1/event1 N: input/event1 S: char/13:65 E: UDEV_LOG=3 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1/event1 E: MAJOR=13 E: MINOR=65 E: DEVNAME=/dev/inpu...

On Tue, Aug 11, 2020 at 11:58:23AM +0000, Eli Cohen wrote: > On Tue, Aug 11, 2020 at 11:26:20AM +0000, Eli Cohen wrote: > > Hi All > > > > Currently, the only statistics we get for a VDPA instance comes from the virtio_net device instance. Since VDPA involves hardware acceleration, there can be quite a lot of information that can be fetched from the underlying device.

From: Leon Romanovsky <leonro at nvidia.com> Changelog: v1: * Renamed _mlx5_rescan_driver to be mlx5_rescan_driver_locked like in other parts of the mlx5 driver. * Renamed MLX5_INTERFACE_PROTOCOL_VDPA to tbe MLX5_INTERFACE_PROTOCOL_VNET as a preparation to coming series from Eli C. * Some small naming renames in mlx5_vdpa. * Refactored adev index code to make Parav's SF series

When I attach an external monitor to my new Dell Precision I always get this and the monitor refuses to recognize video input. If I persist it reaches a point where the machine will boot but won't bring up a login prompt. I have to ssh to get in. And worst of all, it persisted after I remove the external monitor and am forced to re-install CentOS (7.6.1810). Aug 02 14:19:42

Thu, Apr 05, 2018 at 11:08:21PM CEST, sridhar.samudrala at intel.com wrote: >This provides a generic interface for paravirtual drivers to listen >for netdev register/unregister/link change events from pci ethernet >devices with the same MAC and takeover their datapath. The notifier and >event handling code is based on the existing netvsc implementation. A >paravirtual driver can use

This provides a generic interface for paravirtual drivers to listen for netdev register/unregister/link change events from pci ethernet devices with the same MAC and takeover their datapath. The notifier and event handling code is based on the existing netvsc implementation. A paravirtual driver can use this module by registering a set of ops and each instance of the device when it is probed.

Hi! I've installed NUT 2.0.2 to work with my MGE Protection Center and it works but for one thing. When I reboot the computer, at startup upsdrvctl/newhidups can't find the UPS so I have to manually unplug, replug and start upsdrvctl/upsd every time. I've installed from sourcecode onto a Gentoo machine. Where should I look for the problem (USB/hotplug/newhidups/somewhere else)?

From: David Ahern <dsahern at gmail.com> Date: Wed, 4 Apr 2018 11:37:52 -0600 > Networking vendors have out of tree kernel modules. Those modules use a > netdev (call it a master netdev, a control netdev, cpu port, whatever) > to pull packets from the ASIC and deliver to virtual netdevices > representing physical ports. The master netdev should not be mucked with > by a user.

On 2020/1/17 ??10:10, Jason Gunthorpe wrote: >>>> Netlink based lifecycle management could be implemented for vDPA >>>> simulator as well. >>> This is just begging for a netlink based approach. >>> >>> Certainly netlink driven removal should be an agreeable standard for >>> all devices, I think. >> Well, I think Parav had some

On 2020/7/20 ??3:14, Eli Cohen wrote: > Add a front end VDPA driver that registers in the VDPA bus and provides > networking to a guest. The VDPA driver creates the necessary resources > on the VF it is driving such that data path will be offloaded. > > Notifications are being communicated through the driver. > > Currently, only VFs are supported. In subsequent patches we will

On 2020/8/5 ??12:20, Eli Cohen wrote: > Add a front end VDPA driver that registers in the VDPA bus and provides > networking to a guest. The VDPA driver creates the necessary resources > on the VF it is driving such that data path will be offloaded. > > Notifications are being communicated through the driver. > > Currently, only VFs are supported. In subsequent patches we will

On Tue, Aug 11, 2020 at 11:26:20AM +0000, Eli Cohen wrote: > Hi All > > Currently, the only statistics we get for a VDPA instance comes from the virtio_net device instance. Since VDPA involves hardware acceleration, there can be quite a lot of information that can be fetched from the underlying device. Currently there is no generic method to fetch this information. > > One way of

Hello, I just learned this morning about a new patch from Sun for Solaris 8 that adds /dev/random. The patch is based on the device in Solaris 9. I have not tried it yet, but I though some might be interested. The patch is: (this is available for free from sunsolve) Patch-ID# 112438-01 Keywords: secuity random number generator PRNG Synopsis: SunOS 5.8: /kernel/drv/random patch Date: Mar/28/2002

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris

On Fri, 27 Jan 2023 00:32:13 +0200 Vladimir Oltean wrote: > On Thu, Jan 26, 2023 at 09:15:03PM +0200, Leon Romanovsky wrote: > > From: Leon Romanovsky <leonro at nvidia.com> > > > > In netdev common pattern, xxtack pointer is forwarded to the drivers > ~~~~~~ > extack > > > to be filled with error

Greetings! I am trying to do a hot driver swap between the vfio-pci and nouveau drivers for my secondary Nvidia graphics card. I boot up with vfio-pci enabled. With this script I give control over the GPU to nouveau: echo "0000:01:00.0" > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind echo 0x10de 0x11c6 > /sys/bus/pci/drivers/nouveau/new_id echo 1 > /sys/bus/pci/rescan