From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>,
markmc@redhat.com, Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Avi Kivity <avi@redhat.com>, Juan Quintela <quintela@trasno.org>
Subject: [Qemu-devel] Re: [PATCH 1/2] qemu/qdev: type safety in reset handler
Date: Wed, 16 Sep 2009 12:05:41 +0200 [thread overview]
Message-ID: <4AB0B875.2060507@redhat.com> (raw)
In-Reply-To: <20090916093445.GA1404@redhat.com>
Hi,
>> Otherwise, I prefer the old version. We test if there exist
>> dev->info->reset
>> and just after that, we use
>> dev->info->reset()
>
> Good point. I think I'll just move the if (dev->info->reset)
> into qdev_reset.
How about going one step further? Register *one* qdev_reset instance
which then walks the qdev tree and calls ->reset() for every device?
cheers,
Gerd
next prev parent reply other threads:[~2009-09-16 10:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1253025151.git.mst@redhat.com>
2009-09-15 14:33 ` [Qemu-devel] [PATCH 1/2] qemu/qdev: type safety in reset handler Michael S. Tsirkin
2009-09-15 14:55 ` [Qemu-devel] " Gerd Hoffmann
2009-09-15 20:20 ` [Qemu-devel] " Blue Swirl
2009-09-15 20:42 ` Michael S. Tsirkin
2009-09-15 21:16 ` [Qemu-devel] " Paolo Bonzini
2009-09-15 21:37 ` Michael S. Tsirkin
2009-09-16 10:13 ` Gerd Hoffmann
2009-09-16 10:14 ` Michael S. Tsirkin
[not found] ` <m3vdjjutwa.fsf@neno.mitica>
2009-09-16 9:34 ` Michael S. Tsirkin
2009-09-16 10:05 ` Gerd Hoffmann [this message]
2009-09-16 10:06 ` Michael S. Tsirkin
2009-09-16 10:22 ` Gerd Hoffmann
2009-09-16 10:30 ` Michael S. Tsirkin
2009-09-16 10:47 ` Michael S. Tsirkin
2009-09-16 12:08 ` Michael S. Tsirkin
2009-09-15 14:33 ` [Qemu-devel] [PATCH 2/2] qemu/virtio: fix reset with device removal Michael S. Tsirkin
2009-09-15 15:30 ` [Qemu-devel] " Gerd Hoffmann
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=4AB0B875.2060507@redhat.com \
--to=kraxel@redhat.com \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).