From: Gerd Hoffmann <kraxel@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: mst@redhat.com, sfd@endace.com, seabios@seabios.org,
qemu-devel@nongnu.org, avi@redhat.com,
Alexey Korolev <alexey.korolev@endace.com>
Subject: Re: [Qemu-devel] [SeaBIOS] [Seabios] [PATCH 0/6] 64bit PCI BARs allocations (take 2)
Date: Mon, 05 Mar 2012 10:53:25 +0100 [thread overview]
Message-ID: <4F548D15.5000609@redhat.com> (raw)
In-Reply-To: <20120304194030.GJ29291@morn.localdomain>
Hi,
> Hrmm. By my count, this would be the third "rewrite" of the PCI bar
> initialization in the last 14 months.
Indeed.
> Given the churn in this area, I don't want to commit patches that do
> wholesale code replacement. I'd prefer to see each patch
> independently add some functionality and perform its related cleanup.
Hardly doable, the algorithms are very different.
> Also, since Gerd has some patches pending in this area, we should
> figure out which direction makes sense. Can you explain on how this
> 64bit support is different from the support proposed by Gerd?
My code keeps all state needed to do the pci bar allocation in the
pci_bus struct. It counts how many bars of each type+size it has, then
uses this for the allocation. It doesn't need per-device state. The
logic is a bit twisted because of that. Main reason for this is that I
wrote it before "struct pci_device" showed up in seabios (although the
merge was afterwards).
Alexey's code takes a very different route: It uses pci_device data
structure instead and organizes the pci bars in per-region lists. It
makes sense to do that, I think that version is easier to understand
when you look at it the first time.
Both approaches will work fine in the end. I don't care much, I just
want something that works. It's probably a bit risky to merge Alexey's
version before the planned mid-march release.
cheers,
Gerd
next prev parent reply other threads:[~2012-03-05 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 5:50 [Qemu-devel] [Seabios] [PATCH 0/6] 64bit PCI BARs allocations (take 2) Alexey Korolev
2012-03-01 6:05 ` [Qemu-devel] [Seabios] [PATCH 1/6] Adding new structures Alexey Korolev
2012-03-01 6:15 ` [Qemu-devel] [PATCH 2/6] New service functions and ported old functions to 64bit Alexey Korolev
2012-03-01 6:40 ` [Qemu-devel] [PATCH 3/6] Fill PCI regions with etnries Alexey Korolev
2012-03-01 6:57 ` [Qemu-devel] [PATCH 4/6] Mapping of BARs and Bridge regions Alexey Korolev
2012-03-01 9:22 ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2012-03-01 22:01 ` Alexey Korolev
2012-03-02 7:21 ` Gerd Hoffmann
2012-03-05 5:31 ` Alexey Korolev
2012-03-01 7:02 ` [Qemu-devel] [PATCH 5/6] Delete old code Alexey Korolev
2012-03-01 7:11 ` [Qemu-devel] [PATCH 6/6] 64bit PCI range in _CRS table Alexey Korolev
2012-03-01 9:05 ` [Qemu-devel] [SeaBIOS] [Seabios] [PATCH 0/6] 64bit PCI BARs allocations (take 2) Gerd Hoffmann
2012-03-01 21:48 ` Alexey Korolev
2012-03-02 7:08 ` Gerd Hoffmann
2012-03-05 5:34 ` Alexey Korolev
2012-03-05 10:12 ` Gerd Hoffmann
2012-03-06 4:28 ` Alexey Korolev
2012-03-04 19:40 ` [Qemu-devel] " Kevin O'Connor
2012-03-05 6:03 ` Alexey Korolev
2012-03-05 13:16 ` Kevin O'Connor
2012-03-05 9:53 ` Gerd Hoffmann [this message]
2012-03-05 13:49 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2012-03-06 4:44 ` Alexey Korolev
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=4F548D15.5000609@redhat.com \
--to=kraxel@redhat.com \
--cc=alexey.korolev@endace.com \
--cc=avi@redhat.com \
--cc=kevin@koconnor.net \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=sfd@endace.com \
/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).