From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/3] char: check for initial_reset_issued unnecessary
Date: Wed, 7 Oct 2009 17:45:54 +0530 [thread overview]
Message-ID: <20091007121554.GC22238@amit-x200.redhat.com> (raw)
In-Reply-To: <1254913840-10358-2-git-send-email-amit.shah@redhat.com>
On (Wed) Oct 07 2009 [16:40:38], Amit Shah wrote:
> At init, qemu_chr_reset is always called with initial_reset_issued set to 1.
> So checking for it to be set is not necessary.
>
> A later patch will make use of initial_reset_issued to send the reset event
> only if the char device is opened instead of each time when qemu resets it
>
> Signed-off-by: Amit Shah <amit.shah@redhat.com>
> ---
> qemu-char.c | 5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index 8084a67..99ab471 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -127,7 +127,7 @@ static void qemu_chr_reset_bh(void *opaque)
>
> void qemu_chr_reset(CharDriverState *s)
> {
> - if (s->bh == NULL && initial_reset_issued) {
> + if (s->bh == NULL) {
> s->bh = qemu_bh_new(qemu_chr_reset_bh, s);
> qemu_bh_schedule(s->bh);
> }
> @@ -137,11 +137,10 @@ void qemu_chr_initial_reset(void)
> {
> CharDriverState *chr;
>
> - initial_reset_issued = 1;
> -
> QTAILQ_FOREACH(chr, &chardevs, next) {
> qemu_chr_reset(chr);
> }
> + initial_reset_issued = 1;
> }
Actually this won't work since the actual reset is done in a
bh_schedule.
I'll have to find out another way of doing this.
Amit
prev parent reply other threads:[~2009-10-07 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 11:10 [Qemu-devel] char: Send out OPENED events only on char dev open; not on qemu initial reset Amit Shah
2009-10-07 11:10 ` [Qemu-devel] [PATCH 1/3] char: check for initial_reset_issued unnecessary Amit Shah
2009-10-07 11:10 ` [Qemu-devel] [PATCH 2/3] char: rename CHR_EVENT_RESET to CHR_EVENT_OPENED Amit Shah
2009-10-07 11:10 ` [Qemu-devel] [PATCH 3/3] char: emit the OPENED event only when a new char connection is opened Amit Shah
2009-10-07 12:15 ` Amit Shah [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=20091007121554.GC22238@amit-x200.redhat.com \
--to=amit.shah@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).