From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Patchset to implement PTRACE_SYSEMU_SINGLESTEP
Date: Thu, 18 Nov 2004 17:01:38 +0100 [thread overview]
Message-ID: <419CC762.8070602@fujitsu-siemens.com> (raw)
In-Reply-To: <200411181541.13171.blaisorblade_spam@yahoo.it>
Blaisorblade wrote:
> On Thursday 18 November 2004 15:19, Bodo Stroesser wrote:
>
>>Jeff Dike wrote:
>>
>>>bstroesser@fujitsu-siemens.com said:
>>>
>>>>What happens on my system shows some other symptoms. After "Restarting
>>>>system." UML exits without further message. I could track this down to
>>>>a SIGIO being unblocked immediately before the execvp(). It is handled
>>>>by sig_handler() that calls sig_handler_common_skas(). Why this exits,
>>>>I don't know.
>
>
>>>Try this patch. It adds the missing closes that you found today, plus it
>>>makes sure that netdevices get closed down correctly.
>
>
>>> Jeff
>
>
>>Yes. I've tested and mostly it works fine. Only one litte change is needed
>>to have the daemon-network working after "network stop" and "network
>>start". I commented it in the patch.
>
> You mean restarting network support in the guest, right?
Yes. There were some problems in reboot related to the way, daemon network
was closed on "network stop" while UML shutdown.
>
>
>> Bodo
>
>
>>>Index: 2.6.9/arch/um/drivers/net_kern.c
>>>===================================================================
>>>--- 2.6.9.orig/arch/um/drivers/net_kern.c 2004-11-17 22:25:19.000000000
>>>-0500 +++ 2.6.9/arch/um/drivers/net_kern.c 2004-11-17 23:18:21.000000000
>>>-0500 @@ -126,10 +126,6 @@
>>> lp->tl.data = (unsigned long) &lp->user;
>>> netif_start_queue(dev);
>>>
>>>- spin_lock(&opened_lock);
>>>- list_add(&lp->list, &opened);
>>>- spin_unlock(&opened_lock);
>>>-
>>> /* clear buffer - it can happen that the host side of the interface
>>> * is full when we get here. In this case, new data is never queued,
>>> * SIGIOs never arrive, and the net never works.
>>>@@ -150,11 +146,10 @@
>>>
>>> free_irq_by_irq_and_dev(dev->irq, dev);
>
>
>>A little question: what about the "free_irq_by_irq_and_dev"? In my sources
>>they are missing, and I couldn't find a patch relating this. My daemon
>>works without it.
>
>
> Use the 2.6.10-rc2 tree and you should find that - it's an update for IRQ
> handling changes in 2.6.10, i.e. the creation of generic IRQ support, in
> kernel/irq/*, merged by Ingo Molnar.
Aha! I'm still using 2.6.9-bb2 plus some of my patches.
>
> From arch/i386/kernel/irq.c:
>
> /*
> * (mostly architecture independent, will move to kernel/irq.c in 2.5.)
> */
> Well, Ingo Molnar did this. Other archs are not forced to upgrade to the new
> code, but UML was borrowing the i386 headers, which got converted, so we had
> no choice.
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-11-18 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 20:05 [uml-devel] Patchset to implement PTRACE_SYSEMU_SINGLESTEP Bodo Stroesser
2004-11-12 23:43 ` Blaisorblade
2004-11-15 17:11 ` Bodo Stroesser
2004-11-18 6:47 ` Jeff Dike
2004-11-18 14:19 ` Bodo Stroesser
2004-11-18 14:41 ` Blaisorblade
2004-11-18 16:01 ` Bodo Stroesser [this message]
2004-12-06 20:33 ` Blaisorblade
2004-12-07 14:21 ` Bodo Stroesser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=419CC762.8070602@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox