From: Amit Shah <amit.shah@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv3] virtio-serial-bus: use bh for unthrottling
Date: Fri, 29 Apr 2011 17:05:48 +0530 [thread overview]
Message-ID: <20110429113548.GB15359@amit-x200.redhat.com> (raw)
In-Reply-To: <1304076306-15867-1-git-send-email-alevy@redhat.com>
On (Fri) 29 Apr 2011 [14:25:06], Alon Levy wrote:
> Instead of calling flush_queued_data when unthrottling, schedule
> a bh. That way we can return immediately to the caller, and the
> flush uses the same call path as a have_data for callbackee.
>
> No migration change is required because bh are called from vm_stop.
This one looks OK; I'll put it through some testing.
However, I'd like confirmation that accessing (and modifying) vq
elements is fine in bh context. Stefan / Michael?
> ---
> hw/virtio-serial-bus.c | 12 ++++++++++--
> hw/virtio-serial.h | 5 +++++
> 2 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/hw/virtio-serial-bus.c b/hw/virtio-serial-bus.c
> index f10d48f..ca0581b 100644
> --- a/hw/virtio-serial-bus.c
> +++ b/hw/virtio-serial-bus.c
> @@ -285,6 +285,13 @@ size_t virtio_serial_guest_ready(VirtIOSerialPort *port)
> return 0;
> }
>
> +static void flush_queued_data_bh(void *opaque)
> +{
> + VirtIOSerialPort *port = opaque;
> +
> + flush_queued_data(port);
> +}
> +
> void virtio_serial_throttle_port(VirtIOSerialPort *port, bool throttle)
> {
> if (!port) {
> @@ -295,8 +302,7 @@ void virtio_serial_throttle_port(VirtIOSerialPort *port, bool throttle)
> if (throttle) {
> return;
> }
> -
> - flush_queued_data(port);
> + qemu_bh_schedule(port->bh);
> }
>
> /* Guest wants to notify us of some event */
> @@ -726,6 +732,7 @@ static int virtser_port_qdev_init(DeviceState *qdev, DeviceInfo *base)
> bool plugging_port0;
>
> port->vser = bus->vser;
> + port->bh = qemu_bh_new(flush_queued_data_bh, port);
>
> /*
> * Is the first console port we're seeing? If so, put it up at
> @@ -792,6 +799,7 @@ static int virtser_port_qdev_exit(DeviceState *qdev)
> VirtIOSerialPort *port = DO_UPCAST(VirtIOSerialPort, dev, qdev);
> VirtIOSerial *vser = port->vser;
>
> + qemu_bh_delete(port->bh);
> remove_port(port->vser, port->id);
>
> QTAILQ_REMOVE(&vser->ports, port, next);
> diff --git a/hw/virtio-serial.h b/hw/virtio-serial.h
> index 5eb948e..0fa03d1 100644
> --- a/hw/virtio-serial.h
> +++ b/hw/virtio-serial.h
> @@ -119,6 +119,11 @@ struct VirtIOSerialPort {
> uint32_t iov_idx;
> uint64_t iov_offset;
>
> + /*
> + * When unthrottling we use a buttomhalf to call flush_queued_data.
> + */
> + QEMUBH *bh;
> +
> /* Identify if this is a port that binds with hvc in the guest */
> uint8_t is_console;
>
> --
> 1.7.5
>
Amit
next prev parent reply other threads:[~2011-04-29 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 11:25 [Qemu-devel] [PATCHv3] virtio-serial-bus: use bh for unthrottling Alon Levy
2011-04-29 11:35 ` Amit Shah [this message]
2011-04-29 12:56 ` Amit Shah
2011-04-30 8:23 ` Alon Levy
2011-05-02 7:21 ` Amit Shah
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=20110429113548.GB15359@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=alevy@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).