From: Gal Hammer <ghammer@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, peter.maydell@linaro.org, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PATCH 2/2] qtest: fix a "!chr->fd_in_tag" assertion error in qtest.
Date: Mon, 24 Feb 2014 13:44:31 +0200 [thread overview]
Message-ID: <530B309F.8050906@redhat.com> (raw)
In-Reply-To: <530B1FC9.3080507@redhat.com>
On 24/02/2014 12:32, Paolo Bonzini wrote:
> Il 24/02/2014 11:16, Gal Hammer ha scritto:
>> Replacement of the default chardev handlers now requires a call to
>> release the current handlers.
>>
>> Signed-off-by: Gal Hammer <ghammer@redhat.com>
>> ---
>> monitor.c | 1 +
>> qtest.c | 2 ++
>> 2 files changed, 3 insertions(+)
>>
>> diff --git a/monitor.c b/monitor.c
>> index de90fba..db52e7f 100644
>> --- a/monitor.c
>> +++ b/monitor.c
>> @@ -5024,6 +5024,7 @@ void monitor_init(CharDriverState *chr, int flags)
>> if (monitor_ctrl_mode(mon)) {
>> mon->mc = g_malloc0(sizeof(MonitorControl));
>> /* Control mode requires special handlers */
>> + qemu_chr_add_handlers(chr, NULL, NULL, NULL, NULL);
>> qemu_chr_add_handlers(chr, monitor_can_read,
>> monitor_control_read,
>> monitor_control_event, mon);
>> qemu_chr_fe_set_echo(chr, true);
>> diff --git a/qtest.c b/qtest.c
>> index ae941d6..a5682ee 100644
>> --- a/qtest.c
>> +++ b/qtest.c
>> @@ -519,6 +519,8 @@ void qtest_init(const char *qtest_chrdev, const
>> char *qtest_log, Error **errp)
>> return;
>> }
>>
>> + /* Replace the default tcp's handlers with qtest's handlers. */
>> + qemu_chr_add_handlers(chr, NULL, NULL, NULL, NULL);
>> qemu_chr_add_handlers(chr, qtest_can_read, qtest_read,
>> qtest_event, chr);
>> qemu_chr_fe_set_echo(chr, true);
>>
>>
>
> Why can't qemu_chr_add_handlers call remove_fd_in_watch when handlers
> are replaced, before setting the new ones?
>
> Paolo
It used to be like that (see patch 1/2 for the change). However, I
removed it after I saw that the function remove_fd_in_watch() is always
called when setting all the handlers to NULL (qemu-char.c +3872) so a
second call in every chr_update_read_handler callback seems redundant.
As far as I can tell only the qtest change the read handlers and not
using the default ones.
Gal.
next prev parent reply other threads:[~2014-02-24 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 10:16 [Qemu-devel] [PATCH 0/2] char: restore read callback on a reattached (hotplug) chardev Gal Hammer
2014-02-24 10:16 ` [Qemu-devel] [PATCH 1/2] " Gal Hammer
2014-02-24 10:16 ` [Qemu-devel] [PATCH 2/2] qtest: fix a "!chr->fd_in_tag" assertion error in qtest Gal Hammer
2014-02-24 10:32 ` Paolo Bonzini
2014-02-24 11:44 ` Gal Hammer [this message]
2014-02-25 10:18 ` Gal Hammer
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=530B309F.8050906@redhat.com \
--to=ghammer@redhat.com \
--cc=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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.