From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH] stop cpus before forking.
Date: Mon, 14 Jun 2010 14:33:00 -0500 [thread overview]
Message-ID: <4C1683EC.3010609@codemonkey.ws> (raw)
In-Reply-To: <1276543644-32689-1-git-send-email-glommer@redhat.com>
On 06/14/2010 02:27 PM, Glauber Costa wrote:
> This patch fixes a bug that happens with kvm, irqchip-in-kernel,
> while adding a netdev. Despite the situations of reproduction being
> specific to kvm, I believe this fix is pretty generic, and fits here.
> Specially if we ever want to have our own irqchip in kernel too.
>
> The problem happens after the fork system call, and although it is not
> 100 % reproduceable, happens pretty often. After fork, the memory where
> the apic is mapped is present in both processes. It ends up confusing
> the vcpus somewhere in the irq<-> ack path, and qemu hangs, with no
> irqs being delivered at all from that point on.
>
> Making sure the vcpus are stopped before forking makes the problem go
> away. Besides, this is a pretty unfrequent operation, which already hangs
> the io-thread for a while. So it should not hurt performance.
>
> Signed-off-by: Glauber Costa<glommer@redhat.com>
>
This doesn't make very much sense to me but smells like a kernel bug to me.
Even if it isn't, I can't rationalize why stopping the vm like this is
enough to fix such a problem. Is the problem that the KVM VCPU threads
get duplicated while potentially running or something like that?
Regards,
Anthony Liguori
> ---
> net/tap.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/net/tap.c b/net/tap.c
> index 0147dab..f34dd9c 100644
> --- a/net/tap.c
> +++ b/net/tap.c
> @@ -330,6 +330,9 @@ static int launch_script(const char *setup_script, const char *ifname, int fd)
> sigaddset(&mask, SIGCHLD);
> sigprocmask(SIG_BLOCK,&mask,&oldmask);
>
> + /* make sure no cpus are running, so the apic does not
> + * get confused */
> + vm_stop(0);
> /* try to launch network script */
> pid = fork();
> if (pid == 0) {
> @@ -350,6 +353,7 @@ static int launch_script(const char *setup_script, const char *ifname, int fd)
> execv(setup_script, args);
> _exit(1);
> } else if (pid> 0) {
> + vm_start();
> while (waitpid(pid,&status, 0) != pid) {
> /* loop */
> }
>
next prev parent reply other threads:[~2010-06-14 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 19:27 [Qemu-devel] [PATCH] stop cpus before forking Glauber Costa
2010-06-14 19:33 ` Anthony Liguori [this message]
2010-06-14 19:42 ` Glauber Costa
2010-06-14 19:58 ` Anthony Liguori
2010-06-14 20:05 ` Glauber Costa
2010-06-16 16:57 ` Glauber Costa
2010-06-15 6:14 ` Daniel P. Berrange
2010-06-15 7:36 ` Avi Kivity
2010-06-15 7:35 ` Avi Kivity
2010-06-15 7:33 ` Avi Kivity
2010-06-16 16:58 ` Glauber Costa
2010-06-22 12:18 ` Avi Kivity
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=4C1683EC.3010609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.