From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabien Hermenier Subject: Re: xenbus api Date: Tue, 20 Jun 2006 14:22:58 +0200 Message-ID: <1150806178.3408.5.camel@localhost.localdomain> References: <1150360202.21177.7.camel@localhost.localdomain> <4491CABF.60709@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4491CABF.60709@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hello I think your right. I've got the same problem if I write the same code in the netfront. But this time I can show you the call trace The call trace: scheduling while atomic: swapper/0x00000100/1 [] show_trace+0x13/0x20 [] dump_stack+0x1e/0x20 [] schedule+0x766/0x860 [] read_reply+0xe5/0x120 [] xs_talkv+0xab/0x1a0 [] xs_single+0x40/0x50 [] xenbus_read+0x33/0x50 [] xenbus_update_statistics+0x37/0x70 <--- my function [] network_start_xmit+0x214/0x3f0 [] qdisc_restart+0x6f/0x280 [] dev_queue_xmit+0x14f/0x3a0 [] send_fake_arp+0x80/0x90 [] inetdev_notify+0x26/0x30 [] notifier_call_chain+0x2d/0x50 [] inet_insert_ifa+0xe3/0x170 [] devinet_ioctl+0x37f/0x6a9 [] ic_dev_ioctl+0x29/0x40 [] ip_auto_config+0x3a8/0x84f [] init+0x116/0x3e0 [] kernel_thread_helper+0x5/0x10 Thanks for helping Fabien. Le jeudi 15 juin 2006 =C3=A0 16:01 -0500, Anthony Liguori a =C3=A9crit : > You have to provide more context than that. If you're domain boots at=20 > all, XenBus is working. >=20 > It's likely that you're using the XenBus API (which may block) while=20 > holding a lock in the network driver and causing a nasty dead lock of=20 > some sort. >=20 > Regards, >=20 > Anthony Liguori >=20 > Fabien Hermenier wrote: > > Hello > > I have a lot of problem using the xenbus api (in xen-3.0-testing). > > > > I had to modify the network backend driver (file netback.c), and each > > call to a xenbus function in a virtual machine make my machine reboot > > (not the virtual, the real machine). > > > > for example, I 've add this line of code (wich is useless): > > printk("%d",xenbus_exists(XBT_NULL,"/local/domain/0/","domid")); > > after a network packet reception. > > > > When I launch my virtual machine, the station reboot after the virtua= l > > machine console log is stopped after this block: > > > > TCP: Hash tables configured (established 8192 bind 8192) > > NET: Registered protocol family 1 > > NET: Registered protocol family 17 > > > > What do I wrong ? Could I use the xenbus API in the backend (I have s= ame > > problem in the frontend) ? Any tips/advice would be appreciate > > > > Regards. > > Fabien > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > =20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel