From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Hu Tao <hutao@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH RFC qom-next 0/4] QOM'ification of pci-bridge types
Date: Tue, 23 Jul 2013 00:05:52 +0200 [thread overview]
Message-ID: <51EDACC0.1060208@suse.de> (raw)
In-Reply-To: <51ED6A41.6000108@suse.de>
Am 22.07.2013 19:22, schrieb Andreas Färber:
> Am 21.07.2013 22:26, schrieb Michael S. Tsirkin:
>> On Sun, Jul 21, 2013 at 04:09:00PM +0200, Andreas Färber wrote:
>>> Hello Michael et al.,
>>>
>>> This series turns PCIBridge, PCIEPort and PCIESlot into abstract QOM types,
>>> so that we can use QOM casts to obtain a pointer.
>>>
>>> Possibly this was prompted by q35's PCIe?
>>
>> What was prompted?
>
> This refactoring series.
>
>> What's the question exactly?
>
> Why I prepared this series on an offline train ride on Wednesday. ;) Not
> for you to answer - something PCIe must've gotten in the way of some QOM
> realize conversion but the branch is missing the final patch showing
> what these types and casts are good for.
Doh, stumbled over it again: pci_bridge_initfn() should become
PCIBridge's realizefn, and walking down the type hierarchy
pcie_port_init_reg() should become PCIEPort's (which needs
TYPE_PCIE_PORT), etc. That's a bigger refactoring though, so v2 will
come without it.
Andreas
> Since we're in Soft Freeze I
> rather wanted to flush my queues for review though rather than spend
> more time puzzling why I did this. :)
>
> Andreas
>
>>
>>> Don't remember ATM...
>>>
>>> Regards,
>>> Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-07-22 22:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 14:09 [Qemu-devel] [PATCH RFC qom-next 0/4] QOM'ification of pci-bridge types Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 1/4] pci-bridge: Turn into abstract QOM type Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 2/4] pci-bridge-dev: QOM parent field cleanup Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 3/4] pci-bridge/i82801b11: Rename parent field Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 4/4] pcie_port: Turn PCIEPort and PCIESlot into abstract QOM types Andreas Färber
2013-07-21 20:26 ` Michael S. Tsirkin
2013-07-22 17:42 ` Andreas Färber
2013-07-22 19:34 ` Michael S. Tsirkin
2013-07-22 20:29 ` Anthony Liguori
2013-07-22 21:04 ` Andreas Färber
2013-07-23 7:07 ` Michael S. Tsirkin
2013-07-23 9:10 ` Andreas Färber
2013-07-23 9:59 ` Michael S. Tsirkin
2013-07-23 10:21 ` Andreas Färber
2013-07-23 11:21 ` Gerd Hoffmann
2013-07-23 12:35 ` Michael S. Tsirkin
2013-07-23 7:04 ` Michael S. Tsirkin
2013-07-28 12:36 ` Andreas Färber
2013-07-28 12:58 ` Michael S. Tsirkin
2013-07-21 20:26 ` [Qemu-devel] [PATCH RFC qom-next 0/4] QOM'ification of pci-bridge types Michael S. Tsirkin
2013-07-22 17:22 ` Andreas Färber
2013-07-22 22:05 ` Andreas Färber [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=51EDACC0.1060208@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=hutao@cn.fujitsu.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.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).