search for: unreg

The virtio_net driver doesn't dynamically change the RX-ring queue layout and backing pages, but instead reject XDP setup if all the conditions for XDP is not meet. Thus, the xdp_rxq_info also remains fairly static. This allow us to simply add the reg/unreg to net_device open/close functions. Driver hook points for xdp_rxq_info: * reg : virtnet_open * unreg: virtnet_close Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: virtualization at lists.linux-foundation.org Signed-off-by: Jesper...

The virtio_net driver doesn't dynamically change the RX-ring queue layout and backing pages, but instead reject XDP setup if all the conditions for XDP is not meet. Thus, the xdp_rxq_info also remains fairly static. This allow us to simply add the reg/unreg to net_device open/close functions. Driver hook points for xdp_rxq_info: * reg : virtnet_open * unreg: virtnet_close V3: - bugfix, also setup xdp.rxq in receive_mergeable() - Tested bpf-sample prog inside guest on a virtio_net device Cc: "Michael S. Tsirkin" <mst at redhat.com&...

The virtio_net driver doesn't dynamically change the RX-ring queue layout and backing pages, but instead reject XDP setup if all the conditions for XDP is not meet. Thus, the xdp_rxq_info also remains fairly static. This allow us to simply add the init+reg/unreg to net_device open/close functions. Driver hook points for xdp_rxq_info: * init+reg: virtnet_open * unreg : virtnet_close Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: virtualization at lists.linux-foundation.org Signed-off-by:...

The virtio_net driver doesn't dynamically change the RX-ring queue layout and backing pages, but instead reject XDP setup if all the conditions for XDP is not meet. Thus, the xdp_rxq_info also remains fairly static. This allow us to simply add the init+reg/unreg to net_device open/close functions. Driver hook points for xdp_rxq_info: * init+reg: virtnet_open * unreg : virtnet_close Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: virtualization at lists.linux-foundation.org Signed-off-by:...

The virtio_net driver doesn't dynamically change the RX-ring queue layout and backing pages, but instead reject XDP setup if all the conditions for XDP is not meet. Thus, the xdp_rxq_info also remains fairly static. This allow us to simply add the reg/unreg to net_device open/close functions. Driver hook points for xdp_rxq_info: * reg : virtnet_open * unreg: virtnet_close V3: - bugfix, also setup xdp.rxq in receive_mergeable() - Tested bpf-sample prog inside guest on a virtio_net device Cc: "Michael S. Tsirkin" <mst at redhat.com&...

...cation as well. Now the 3rd feature ... in iax.conf or sip.conf for each user define the keyword 'onregister-context' syntax: [user] type=friend onregister-context=regcontext etc then upon registry, (context,exten) = (<onregister-context>,<user>,1) will be invoked and on unregister the (unreg-<onregister-context>,<user>,1) is invoked So on unregister 'unreg-' is prefixed to the onregister_context The variable ${DEVICETECH} contains the technology of the device registering. To rebuild the unique channel id from this, you would use ${DEVICETECH}/$...

...c void virtnet_disable_qp(struct virtnet_info *vi, int qp_index) >>>>>> +{ >>>>>> + virtnet_napi_tx_disable(&vi->sq[qp_index].napi); >>>>>> + napi_disable(&vi->rq[qp_index].napi); >>>>>> + xdp_rxq_info_unreg(&vi->rq[qp_index].xdp_rxq); >>>>>> +} >>>>>> + >>>>>> static int virtnet_open(struct net_device *dev) >>>>>> { >>>>>> struct virtnet_info *vi = netdev_priv(dev); >>>>>&gt...

...> > > > > The fbdev notifier strikes again! > > > > > > Last time I looked into this I think the proper solution would be to split > > > the backlight part from the other fbdev notifier (which is used by fbcon > > > for reacting to fbdev device reg/unreg events). > > > > > > I think that would fix this too, with the added bonus of slightly > > > untangling the fbcon locking mess. And it's also the one part of > > > untangling this mess which should be possible without any trouble - I've > > > sim...

...HREED.OCX' or one of its dependancies not correctly registered: a file is missing or invalid. * THREED.OCX is present in the Wine windows\system32 folder. It is identical with the THREED.OCX file on my windows computer. * I have manually registered the file using regsvr32. Also tried to first unreg it and the reg it again. * I have checked with RegEdit that THREED.OCX is in the Registry (under Shared DLLs) * I have used Winetricks to install Vb6run What am I missing? Please help

...;> +static void virtnet_disable_qp(struct virtnet_info *vi, int qp_index) > >>>> +{ > >>>> + virtnet_napi_tx_disable(&vi->sq[qp_index].napi); > >>>> + napi_disable(&vi->rq[qp_index].napi); > >>>> + xdp_rxq_info_unreg(&vi->rq[qp_index].xdp_rxq); > >>>> +} > >>>> + > >>>> static int virtnet_open(struct net_device *dev) > >>>> { > >>>> struct virtnet_info *vi = netdev_priv(dev); > >>>> @@ -1883,20 +1890,2...

...> The fbdev notifier strikes again! > > > > > > > > Last time I looked into this I think the proper solution would be to split > > > > the backlight part from the other fbdev notifier (which is used by fbcon > > > > for reacting to fbdev device reg/unreg events). > > > > > > > > I think that would fix this too, with the added bonus of slightly > > > > untangling the fbcon locking mess. And it's also the one part of > > > > untangling this mess which should be possible without any trouble - I'v...

Hi people, Does anybody know some Density-Based Method for clustering implemented in R? Thanks, Fernando Prass _______________________________________________________

...inor shutdown reasons. Aric Stewart (2): ws2_32: async_send with no buffers does not need to do any work. user32: Remove SetWindowText export. Austin English (3): ntdll: Bump win2k3 version information to sp2. urlmon: Add stubs for ordinals 410 and 423. msiexec: Add /unreg as an alias for /z. Charles Davis (2): ntdll: Fix IOCTL_CDROM_RAW_READ on Mac OS. ntdll: Implement CDROM_GetInterfaceInfo() on Mac OS. Cheer Xiao (1): view: Update simplified Chinese translation. Damian Dixon (1): advapi32: Added check for NULL pointer being passed to Que...

...1) != 0 ) ret = -EIO; break; + + case CALLBACKTYPE_sysenter: + if ( ! cpu_has_sep ) + ret = -EINVAL; + else + do_update_sysenter(&reg->address); + break; #endif case CALLBACKTYPE_nmi: @@ -358,6 +365,7 @@ static long unregister_guest_callback(st case CALLBACKTYPE_event: case CALLBACKTYPE_failsafe: #ifdef CONFIG_X86_SUPERVISOR_MODE_KERNEL + case CALLBACKTYPE_sysenter_deprecated: case CALLBACKTYPE_sysenter: #endif ret = -EINVAL; Index: 2007-08-08/xen/arch/x86/x86_64/asm-offsets.c ==========...

.... ole32/tests: Make sure to use return values (LLVM/Clang). urlmon/tests: Make sure to use a return value (LLVM/Clang). ntdll/tests: Make sure return values are used (LLVM/Clang). wine.inf: Add HKLM\\Software\\Microsoft\\Windows\\Current Version\\Run key. msiexec: Add /unreg as an alias for /z. oleaut32/tests: Don't check return values inside of if(0) (LLVM/Clang). oleaut32/tests: Make sure a return value is used (LLVM/Clang). oleaut32/tests: Make sure return values are used (LLVM/Clang). oleaut32/tests: Make sure return values are used (LLV...

...bout a dependency cycle: > > > > The fbdev notifier strikes again! > > > > Last time I looked into this I think the proper solution would be to split > > the backlight part from the other fbdev notifier (which is used by fbcon > > for reacting to fbdev device reg/unreg events). > > > > I think that would fix this too, with the added bonus of slightly > > untangling the fbcon locking mess. And it's also the one part of > > untangling this mess which should be possible without any trouble - I've > > simply never done it since e...

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

...ses lockdep to warn >> about a dependency cycle: > > The fbdev notifier strikes again! > > Last time I looked into this I think the proper solution would be to split > the backlight part from the other fbdev notifier (which is used by fbcon > for reacting to fbdev device reg/unreg events). > > I think that would fix this too, with the added bonus of slightly > untangling the fbcon locking mess. And it's also the one part of > untangling this mess which should be possible without any trouble - I've > simply never done it since entirely getting rid of th...

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

...r with the fbdev as a client causes lockdep to warn > about a dependency cycle: The fbdev notifier strikes again! Last time I looked into this I think the proper solution would be to split the backlight part from the other fbdev notifier (which is used by fbcon for reacting to fbdev device reg/unreg events). I think that would fix this too, with the added bonus of slightly untangling the fbcon locking mess. And it's also the one part of untangling this mess which should be possible without any trouble - I've simply never done it since entirely getting rid of the fbdev notifier for fbc...