qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] spapr_llan: fix device reenabling
Date: Mon, 06 May 2013 17:16:24 +0200	[thread overview]
Message-ID: <5187C948.30607@suse.de> (raw)
In-Reply-To: <1367562123-1686-1-git-send-email-aik@ozlabs.ru>

On 05/03/2013 08:22 AM, Alexey Kardashevskiy wrote:
> Normally, the "tap" device is polled by QEMU if a guest NIC can
> receive packets. If a guest NIC is stopped during transfer (rmmod or
> ifdown), it may still have packets in a queue which have to be send
> to the guest before QEMU enables polling of a "tap" interface via
> tap_update_fd_handler().
>
> However the spapr_llan device was missing the qemu_flush_queued_packets()
> call so the tap_send_completed() callback was never called and therefore
> "tap" interface polling was not enabled ever.
>
> The patch fixes this problem.
>
> Signed-off-by: Alexey Kardashevskiy<aik@ozlabs.ru>

Thanks, applied to ppc-next.

Alex

> ---
>   hw/net/spapr_llan.c |    2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/hw/net/spapr_llan.c b/hw/net/spapr_llan.c
> index cca3d1a..46f7d5f 100644
> --- a/hw/net/spapr_llan.c
> +++ b/hw/net/spapr_llan.c
> @@ -336,6 +336,8 @@ static target_ulong h_register_logical_lan(PowerPCCPU *cpu,
>       spapr_vio_dma_set(sdev, VLAN_BD_ADDR(rec_queue), 0, VLAN_BD_LEN(rec_queue));
>
>       dev->isopen = 1;
> +    qemu_flush_queued_packets(qemu_get_queue(dev->nic));
> +
>       return H_SUCCESS;
>   }
>

      reply	other threads:[~2013-05-06 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  6:22 [Qemu-devel] [PATCH] spapr_llan: fix device reenabling Alexey Kardashevskiy
2013-05-06 15:16 ` Alexander Graf [this message]

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=5187C948.30607@suse.de \
    --to=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).