From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.7] monitor: eliminate monitor_event_state_lock
Date: Thu, 17 Oct 2013 08:45:42 -0400 [thread overview]
Message-ID: <20131017084542.148c5a80@redhat.com> (raw)
In-Reply-To: <1381943828-7948-1-git-send-email-pbonzini@redhat.com>
On Wed, 16 Oct 2013 19:17:08 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> This lock does not protect anything that the BQL does not already
> protect. Furthermore, with -nodefaults and no monitor, the mutex
> is not initialized but monitor_protocol_event_queue is called
> anyway, which causes a crash under mingw (and only works by luck.
> under Linux or other POSIX OSes).
>
> Reported-by: Orx Goshen <orx.goshen@intel.com>
> Cc: Daniel Berrange <berrange@redhat.com>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Applied to the qmp branch, thanks.
> ---
> Maybe I'm missing something?
I don't think so.
>
> monitor.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/monitor.c b/monitor.c
> index 74f3f1b..0ae99dc 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -511,7 +511,6 @@ static const char *monitor_event_names[] = {
> QEMU_BUILD_BUG_ON(ARRAY_SIZE(monitor_event_names) != QEVENT_MAX)
>
> MonitorEventState monitor_event_state[QEVENT_MAX];
> -QemuMutex monitor_event_state_lock;
>
> /*
> * Emits the event to every monitor instance
> @@ -543,7 +542,6 @@ monitor_protocol_event_queue(MonitorEvent event,
> int64_t now = qemu_clock_get_ns(QEMU_CLOCK_REALTIME);
> assert(event < QEVENT_MAX);
>
> - qemu_mutex_lock(&monitor_event_state_lock);
> evstate = &(monitor_event_state[event]);
> trace_monitor_protocol_event_queue(event,
> data,
> @@ -576,7 +574,6 @@ monitor_protocol_event_queue(MonitorEvent event,
> evstate->last = now;
> }
> }
> - qemu_mutex_unlock(&monitor_event_state_lock);
> }
>
>
> @@ -589,7 +586,6 @@ static void monitor_protocol_event_handler(void *opaque)
> MonitorEventState *evstate = opaque;
> int64_t now = qemu_clock_get_ns(QEMU_CLOCK_REALTIME);
>
> - qemu_mutex_lock(&monitor_event_state_lock);
>
> trace_monitor_protocol_event_handler(evstate->event,
> evstate->data,
> @@ -601,7 +597,6 @@ static void monitor_protocol_event_handler(void *opaque)
> evstate->data = NULL;
> }
> evstate->last = now;
> - qemu_mutex_unlock(&monitor_event_state_lock);
> }
>
>
> @@ -638,7 +633,6 @@ monitor_protocol_event_throttle(MonitorEvent event,
> * and initialize state */
> static void monitor_protocol_event_init(void)
> {
> - qemu_mutex_init(&monitor_event_state_lock);
> /* Limit RTC & BALLOON events to 1 per second */
> monitor_protocol_event_throttle(QEVENT_RTC_CHANGE, 1000);
> monitor_protocol_event_throttle(QEVENT_BALLOON_CHANGE, 1000);
prev parent reply other threads:[~2013-10-17 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 17:17 [Qemu-devel] [PATCH 1.7] monitor: eliminate monitor_event_state_lock Paolo Bonzini
2013-10-16 17:21 ` Daniel P. Berrange
2013-10-17 12:45 ` Luiz Capitulino [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=20131017084542.148c5a80@redhat.com \
--to=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).