From: Blue Swirl <blauwirbel@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, mst@redhat.com,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/5]: Convert pci_info() to QObject
Date: Wed, 20 Jan 2010 19:22:48 +0000 [thread overview]
Message-ID: <f43fc5581001201122w7e16bf48m221949909d658711@mail.gmail.com> (raw)
In-Reply-To: <20100120161114.3bfdebca@doriath>
On Wed, Jan 20, 2010 at 6:11 PM, Luiz Capitulino <lcapitulino@redhat.com> wrote:
> On Wed, 20 Jan 2010 18:57:56 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
>
>> Luiz Capitulino <lcapitulino@redhat.com> writes:
>>
>> > Hi,
>> >
>> > This new version addresses Markus's comments.
>> >
>> > changelog
>> > ---------
>> >
>> > V1 -> V2
>> >
>> > - Make class_info's key 'desc' optional
>> > - Better indentation
>> > - Doc fixes
>> >
>> > V0 -> V1
>> >
>> > - Coding style fixes
>> > - Make 'BAR' and 'IRQ' keys lowercase
>> > - Add 'irq' key to the documentation
>> >
>> > Thanks.
>>
>> Looks good, although one comment still applies: PATCH 3/5 regresses info
>> pci, 4/5 and 5/5 fix it. Do we care? They're separate because they're
>> untested.
>
> There are two problems here, which apply for those whom emulate
> the hardware:
>
> 1. 'info pci' output will brake with git bisect
>
> 2. As the code is untested, it might be broken
>
> Only two 2 seems serious.
>
> Michael, does the sparc image on qemu.org have the hardware
> in question (pci bridge)?
Sparc64 has two Simba bridges, but currently they are broken so there
are no devices behind them. In addition there should be a DEC 21154
bridge.
There is no Sparc64 test image yet (very few Sparc32 machines did have
any PCI and we don't emulate them), but you can test the output
without any images:
qemu-system-sparc64 -L pc-bios -S -monitor stdio
QEMU 0.12.50 monitor - type 'help' for more information
(qemu) info pci
Bus 0, device 0, function 0:
Host bridge: PCI device 108e:a000
id ""
Bus 0, device 1, function 0:
PCI bridge: PCI device 108e:5000
BUS 0.
secondary bus 0.
subordinate bus 0.
IO range [0x0000, 0x0fff]
memory range [0x00000000, 0x000fffff]
prefetchable memory range [0x00000000, 0x000fffff]
id ""
Bus 0, device 1, function 1:
PCI bridge: PCI device 108e:5000
BUS 0.
secondary bus 0.
subordinate bus 0.
IO range [0x0000, 0x0fff]
memory range [0x00000000, 0x000fffff]
prefetchable memory range [0x00000000, 0x000fffff]
id ""
Bus 0, device 2, function 0:
VGA controller: PCI device 1234:1111
BAR0: 32 bit prefetchable memory at 0xffffffffffffffff [0x007ffffe].
id ""
Bus 0, device 3, function 0:
Bridge: PCI device 108e:1000
BAR0: 32 bit memory at 0xffffffffffffffff [0x00fffffe].
BAR1: 32 bit memory at 0xffffffffffffffff [0x007ffffe].
id ""
Bus 0, device 4, function 0:
Ethernet controller: PCI device 10ec:8029
IRQ 0.
BAR0: I/O at 0xffffffffffffffff [0x00fe].
id ""
Bus 0, device 5, function 0:
IDE controller: PCI device 1095:0646
IRQ 0.
BAR0: I/O at 0xffffffffffffffff [0x0006].
BAR1: I/O at 0xffffffffffffffff [0x0002].
BAR2: I/O at 0xffffffffffffffff [0x0006].
BAR3: I/O at 0xffffffffffffffff [0x0002].
BAR4: I/O at 0xffffffffffffffff [0x000e].
id ""
(qemu) c
(qemu) info pci
Bus 0, device 0, function 0:
Host bridge: PCI device 108e:a000
id ""
Bus 0, device 1, function 0:
PCI bridge: PCI device 108e:5000
BUS 0.
secondary bus 0.
subordinate bus 0.
IO range [0x0000, 0x0fff]
memory range [0x00000000, 0x000fffff]
prefetchable memory range [0x00000000, 0x000fffff]
id ""
Bus 0, device 1, function 1:
PCI bridge: PCI device 108e:5000
BUS 0.
secondary bus 0.
subordinate bus 0.
IO range [0x0000, 0x0fff]
memory range [0x00000000, 0x000fffff]
prefetchable memory range [0x00000000, 0x000fffff]
id ""
Bus 0, device 2, function 0:
VGA controller: PCI device 1234:1111
BAR0: 32 bit prefetchable memory at 0x00800000 [0x00ffffff].
id ""
Bus 0, device 3, function 0:
Bridge: PCI device 108e:1000
BAR0: 32 bit memory at 0x01000000 [0x01ffffff].
BAR1: 32 bit memory at 0x02000000 [0x027fffff].
id ""
Bus 0, device 4, function 0:
Ethernet controller: PCI device 10ec:8029
IRQ 0.
BAR0: I/O at 0x0400 [0x04ff].
id ""
Bus 0, device 5, function 0:
IDE controller: PCI device 1095:0646
IRQ 1.
BAR0: I/O at 0x0500 [0x0507].
BAR1: I/O at 0x0580 [0x0583].
BAR2: I/O at 0x0600 [0x0607].
BAR3: I/O at 0x0680 [0x0683].
BAR4: I/O at 0x0700 [0x070f].
id ""
next prev parent reply other threads:[~2010-01-20 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 16:39 [Qemu-devel] [PATCH v2 0/5]: Convert pci_info() to QObject Luiz Capitulino
2010-01-20 16:39 ` [Qemu-devel] [PATCH 1/5] QList: Introduce QLIST_FOREACH_ENTRY() Luiz Capitulino
2010-01-20 16:39 ` [Qemu-devel] [PATCH 2/5] QDict: Introduce qdict_get_qdict() Luiz Capitulino
2010-01-20 16:39 ` [Qemu-devel] [PATCH 3/5] PCI: Convert pci_info() to QObject Luiz Capitulino
2010-01-20 16:39 ` [Qemu-devel] [PATCH 4/5] PCI: do_pci_info(): PCI bridge support Luiz Capitulino
2010-01-20 16:39 ` [Qemu-devel] [PATCH 5/5] PCI: do_pci_info(): PCI bridge devices support Luiz Capitulino
2010-01-20 17:57 ` [Qemu-devel] [PATCH v2 0/5]: Convert pci_info() to QObject Markus Armbruster
2010-01-20 18:11 ` Luiz Capitulino
2010-01-20 19:22 ` Blue Swirl [this message]
2010-01-21 13:52 ` Luiz Capitulino
2010-01-21 17:04 ` Blue Swirl
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=f43fc5581001201122w7e16bf48m221949909d658711@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@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).