qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: lersek@redhat.com, QEMU <qemu-devel@nongnu.org>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] monitor: throttle VSERPORT_CHANGED by "id"
Date: Thu, 10 Sep 2015 09:52:19 +0530	[thread overview]
Message-ID: <20150910042219.GA10281@grmbl.mre> (raw)
In-Reply-To: <CAJ+F1CLrSDtJjZ9U_7+a0_u4PiM_S819zDMPe=+4V+pyxvFUSQ@mail.gmail.com>

On (Tue) 08 Sep 2015 [12:18:53], Marc-André Lureau wrote:
> ping

I'd rather the qmp / qapi maintainers chimed in - the changes touch
that part of code rather than the virtio-serial related code.

> 
> On Wed, Sep 2, 2015 at 1:09 PM,  <marcandre.lureau@redhat.com> wrote:
> > From: Marc-André Lureau <marcandre.lureau@redhat.com>
> >
> > QAPI_EVENT_VSERPORT_CHANGE reports changes of a virtio serial port
> > state. However, the events may be for different ports, but the throttle
> > mechanism may replace the event for a different port, since it only
> > checks the event type.
> >
> > The following series implements throttling of events based on the "id"
> > field. Hopefully this hash table approach can be later extended if
> > other fields or combination of fields have to be used.
> >
> > rfc->v1:
> > - fix uppercase FALSE/TRUE and gpointer (glib-ism)
> > - spelling fix
> >
> > Marc-André Lureau (3):
> >   monitor: split MonitorQAPIEventState
> >   monitor: throttle QAPI_EVENT_VSERPORT_CHANGE by "id"
> >   monitor: remove old entries from event hash table
> >
> >  monitor.c    | 245 +++++++++++++++++++++++++++++++++++++++++++++--------------
> >  trace-events |   2 +-
> >  2 files changed, 188 insertions(+), 59 deletions(-)
> >
> > --
> > 2.4.3
> >
> 
> 
> 
> -- 
> Marc-André Lureau

		Amit

  reply	other threads:[~2015-09-10  4:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 11:09 [Qemu-devel] [PATCH 0/3] monitor: throttle VSERPORT_CHANGED by "id" marcandre.lureau
2015-09-02 11:09 ` [Qemu-devel] [PATCH 1/3] monitor: split MonitorQAPIEventState marcandre.lureau
2015-09-10  8:34   ` Daniel P. Berrange
2015-09-16 13:57   ` Markus Armbruster
2015-09-17 13:17     ` Marc-André Lureau
2015-09-02 11:09 ` [Qemu-devel] [PATCH 2/3] monitor: throttle QAPI_EVENT_VSERPORT_CHANGE by "id" marcandre.lureau
2015-09-10  8:35   ` Daniel P. Berrange
2015-09-16 16:40   ` Markus Armbruster
2015-09-17 11:28     ` Marc-André Lureau
2015-09-17 14:06     ` Marc-André Lureau
2015-09-02 11:09 ` [Qemu-devel] [PATCH 3/3] monitor: remove old entries from event hash table marcandre.lureau
2015-09-10  8:35   ` Daniel P. Berrange
2015-09-16 16:50   ` Markus Armbruster
2015-09-17 14:43     ` Marc-André Lureau
2015-09-08 10:18 ` [Qemu-devel] [PATCH 0/3] monitor: throttle VSERPORT_CHANGED by "id" Marc-André Lureau
2015-09-10  4:22   ` Amit Shah [this message]
2015-09-10  6:46     ` Markus Armbruster

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=20150910042219.GA10281@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=marcandre.lureau@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 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).