similar to: [PATCH 3/3] Update SFC net drivers

There would seem to be a potential deadlock in the netfront accelerator plugin support. When the configured accelerator changes in xenstore, netfront tries to load the new plugin using request_module(). It does this from a workqueue work item. request_module() will invoke modprobe which in some circumstances (I''m not sure exactly what - I''ve not managed to reproduce it myself)

Add two new functions: xenbus_for_each_backend and xenbus_for_each_frontend to iterate the backend and frontend buses respectively and apply the supplied test to each one. Signed-off-by: Kieran Mansley <kmansley@solarflare.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Signed-off-by: Kieran Mansley <kmansley@solarflare.com> Cleanup vif_state on device removal diff -r f992a517aba5 drivers/xen/netfront/accel.c --- a/drivers/xen/netfront/accel.c Wed Oct 03 13:41:33 2007 +0100 +++ b/drivers/xen/netfront/accel.c Wed Oct 03 13:45:55 2007 +0100 @@ -500,6 +500,30 @@ EXPORT_SYMBOL_GPL(netfront_accelerator_r /* + * Remove the hooks from a single vif state.

lejeczek via CentOS wrote: > hi guys > > I wonder if any of you might be using SFN6122F-R7 SFP+ (SFC9000, same > firmware everywhere, Centos 7.5 too. > > I'm trying poor man's setup to get the servers onto 10GbE network. > > > Setup is such that three Dell R815 are connected to each other, each has > one Solarflare(SFP ports) and each Solarflare is set as

hi guys I wonder if any of you might be using SFN6122F-R7 SFP+ (SFC9000, same firmware everywhere, Centos 7.5 too. I'm trying poor man's setup to get the servers onto 10GbE network. Setup is such that three Dell R815 are connected to each other, each has one Solarflare(SFP ports) and each Solarflare is set as net-team(both ports on a card are net-team device) with runner in broadcast

Signed-off-by: Kieran Mansley <kmansley@solarflare.com> Allow iomem permissions to be set up through grant table ops diff -r 749b60ccc177 xen/arch/x86/mm.c --- a/xen/arch/x86/mm.c Wed Jul 25 14:03:08 2007 +0100 +++ b/xen/arch/x86/mm.c Wed Jul 25 14:03:12 2007 +0100 @@ -594,6 +594,14 @@ get_##level##_linear_pagetable( return 1; \ } + +int iomem_page_test(unsigned long mfn,

cleanup accelerators list on netfront unload Signed-off-by <kmansley@solarflare.com> diff -r fdfd708d2ec4 drivers/xen/netfront/accel.c --- a/drivers/xen/netfront/accel.c Wed Oct 24 15:38:35 2007 +0100 +++ b/drivers/xen/netfront/accel.c Wed Oct 24 16:25:57 2007 +0100 @@ -75,6 +75,24 @@ void netif_init_accel(void) spin_lock_init(&accelerators_lock); } +void netif_exit_accel(void) +{

CentOS Errata and Enhancement Advisory 2014:1179 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-1179.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fc6171ee4cfab2807cd0cd54b684def6109fef8a2e5d516d0cfca38d47d64404 kmod-sfc-4.0-3.el6_5.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2016:1977 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1977.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8d00aea701167b41636c94c8dc6c6dc7658daa1f833d5c6dfbf2a02e179d26a6 kmod-sfc-4.0-1.el7_2.x86_64.rpm Source:

Can anyone work out why my callerid doesn't work on my isdn4Linux with asterisk (or without asterisk for that matter)... This used to work fine, and I am quite confident that the telco is sending callerid information (because they always do on all ISDN lines standard, only extra cost on POTS lines). This is the information from dmesg, whether asterisk is running or not: isdn_net: Incoming

I''m having problems starting more than three domains. It sometimes works fine, but more often than not the 4th domain''s root block device times out and so the domU kernel panics as there''s no /dev/root: XENBUS: Timeout connecting to device: device/vbd/2057 (state 6) XENBUS: Timeout connecting to device: device/vif/0 (state 6) XENBUS: Timeout connecting to device:

Hi, I have uploaded a new set of rebased openSUSE dom0 xen patches and Gentoo ebuild for 2.6.31 to http://code.google.com/p/gentoo-xen-kernel/downloads/list, Jan Beulich recently identified the cause of the null pointer crash and other stability problems that affected previous versions and with the necessary fixes applied the kernel has run for 2+ days with no issues at all, I think you will find

This set of patches adds the support for acceleration plugins to the netfront/netback drivers. These plugins are intended to support virtualisable network hardware that can be directly accessed from the guest, bypassing dom0. This is in response to the RFC we posted to xen-devel with an outline of our approach at the end of September. To follow will be another set of patches to provide our

While writing a driver for a device doing lots of DMA I''ve hit an "swiotlb_full()" problem. This surprised me somewhat as I wouldn''t have expected to need the use of the software TLB - it''s a 64 bit capable device on a server with only 2 GB of RAM, and so I''d have expected to be using a hardware TLB. Is this a peculiarity of Xen, or should I be right

This might be a silly question for most, but since Xen is ever so changing with regular changesets and updates, what is the "best practice" way to upgrade / update or even downgrade Xen? 1.) Is it by booting into regular Linux Kernel without Xen, do a complete uninstall of the old Xen, than install the newly compiled Xen? 2.) Is it by booting into regular Linux Kernel without Xen,

is anybody else having problems with the new java 1.6.0.22 ? i am tried both cortado-ovt-debug and cortado-ovtk-debug - neither seem to work anymore once i installed the new java. once i go back to the old java 21 everything works fine. my jar file downloads for console messages (below) came from: http://downloads.xiph.org/releases/cortado/cortado-ovtk-debug-0.6.0.jar i have included

Hi, Apologies in advance for the lengthy email. I'm new to asterisk and have trouble with isdn4linux. The setup is very basic like this: winxp ------- asterisk -------- winxp x-lite | x-lite | pstn The hardware involved is: Compaq EVO with RH9/kernel 2.4.20-30.9. Fritz!Card PCI v2 Asterisk CVS-04/17/04-21:36:18 Basically

2008/7/16 John Ferlito <johnf at inodes.org>: >> Now there's the minor problem of upgrading from an earlier version of >> oggz, and having both versions of the >> tools around (eg. having an old oggzdump lying around even as >> oggz-dump is upgraded). What are your thoughts about ways to deal with >> this? eg. >> >> * On 'make install',

This set of patches adds the support for acceleration plugins to the netfront/netback drivers. These plugins are intended to support virtualisable network hardware that can be directly accessed from the guest, bypassing dom0. This is in response to the RFC we posted to xen-devel with an outline of our approach at the end of September. To follow will be another set of patches to provide our

********************************************************************** CALL FOR PARTICIPATION ====================== The 8th IEEE International Conference on Autonomic Computing Karlsruhe, Germany June 14-18, 2011 http://icac2011.cis.fiu.edu