All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v2 2/6] qdev: reset qdev along with qdev tree
Date: Mon, 20 Dec 2010 22:01:36 +0100	[thread overview]
Message-ID: <m31v5cw43z.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <4D0FB11D.4030607@mail.berlios.de> (Stefan Weil's message of "Mon, 20 Dec 2010 20:40:13 +0100")

Stefan Weil <weil@mail.berlios.de> writes:

> Am 20.12.2010 13:58, schrieb Markus Armbruster:
>> Anthony Liguori <aliguori@linux.vnet.ibm.com> writes:
>>
>>> On 12/17/2010 08:45 AM, Peter Maydell wrote:
>>>> On 17 December 2010 00:24, Anthony
>>>> Liguori<aliguori@linux.vnet.ibm.com> wrote:
>>>>
>>>>> On 12/16/2010 05:48 PM, Michael S. Tsirkin wrote:
>>>>>
>>>>>> Ugh, I keep forgetting about the non-qdev systems.
>>>>>> Maybe it's a good way to finally make everyone to convert? If a system
>>>>>> maintainer can't be bothered to convert to qdev we can declare the
>>>>>> system unsupported :)
>>>>>>
>>>>
>>>>> Honestly, I think that's a fair thing to do.
>>>>>
>>>> I'm guessing that would be a transition/conversion to make for the
>>>> 0.15 release, right?
>>>>
>>>
>>> Yes.
>>
>> Let's do it.
>
>
> I already tried to convert malta / gt64xxx to qdev. While simple
> devices are easily converted, I'm still struggling with gt64xxx.

Specific problems?

> There is some qdev documentation for end users (command line
> parameters), but is there qdev documentation for developers, too?
> If not, adding a qdev chapter to qemu-tech.texi (preferred), writing a
> qdev wiki page, code templates (for systems / buses / bus controllers /
> bus devices) or some other form of documentation would be a good start
> for release 0.15 (imho).

It's not what you ask for, but perhaps it helps a bit anyway:
http://www.linux-kvm.org/wiki/images/f/fe/2010-forum-armbru-qdev.pdf

  reply	other threads:[~2010-12-20 21:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19  9:55 [Qemu-devel] [PATCH v2 0/6] qdev reset refactoring and pci bus reset Isaku Yamahata
2010-11-19  9:55 ` [Qemu-devel] [PATCH v2 1/6] qbus: add functions to walk both devices and busses Isaku Yamahata
2010-11-19  9:55 ` [Qemu-devel] [PATCH v2 2/6] qdev: reset qdev along with qdev tree Isaku Yamahata
2010-12-16 19:31   ` Stefan Weil
2010-12-16 23:48     ` Michael S. Tsirkin
2010-12-17  0:24       ` Anthony Liguori
2010-12-17 14:45         ` Peter Maydell
2010-12-17 14:56           ` Anthony Liguori
2010-12-20 12:58             ` Markus Armbruster
2010-12-20 19:40               ` Stefan Weil
2010-12-20 21:01                 ` Markus Armbruster [this message]
2010-12-17  4:29     ` Isaku Yamahata
2010-12-17  4:47       ` Isaku Yamahata
2010-12-18 18:11         ` Stefan Weil
2010-12-19 13:25           ` Michael S. Tsirkin
2010-11-19  9:56 ` [Qemu-devel] [PATCH v2 3/6] qdev: introduce reset call back for qbus level Isaku Yamahata
2010-11-19  9:56 ` [Qemu-devel] [PATCH v2 4/6] qdev: introduce a helper function which triggers reset from a given device Isaku Yamahata
2010-11-19  9:56 ` [Qemu-devel] [PATCH v2 5/6] pci: make use of qdev reset frame work to pci bus reset Isaku Yamahata
2010-11-19  9:56 ` [Qemu-devel] [PATCH v2 6/6] pci bridge: implement secondary " Isaku Yamahata
2010-11-19 12:00   ` [Qemu-devel] " Michael S. Tsirkin
2010-11-22  7:54 ` [Qemu-devel] Re: [PATCH v2 0/6] qdev reset refactoring and pci " Michael S. Tsirkin
2010-11-22 10:43   ` Isaku Yamahata
2010-11-22 10:54     ` Michael S. Tsirkin
2010-11-22 22:53     ` Michael S. Tsirkin
2010-11-23 18:10       ` Michael S. Tsirkin
2010-11-24  2:37         ` Isaku Yamahata
2010-11-24  5:27           ` Michael S. Tsirkin
2010-11-24  7:15             ` Isaku Yamahata
2010-11-24 10:59               ` Michael S. Tsirkin
2010-11-24 11:09                 ` Isaku Yamahata

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=m31v5cw43z.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    --cc=yamahata@valinux.co.jp \
    /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.