From: Isaku Yamahata <yamahata@valinux.co.jp>
To: seabios@seabios.org
Cc: yamahata@valinux.co.jp, cam@cs.ualberta.ca, adnan@khaleel.us,
qemu-devel@nongnu.org, mst@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] pciinit: fix overflow when bar allocation
Date: Thu, 28 Oct 2010 14:04:04 +0900 [thread overview]
Message-ID: <cover.1288242111.git.yamahata@valinux.co.jp> (raw)
Okay, now added comments to members and functions as requested.
No essential code change.
Changes v1 -> v2:
- add comment.
Patch description:
This patch set fixes PCI bar allocation when bar overflow occured.
I checked if pmm_alloc facility can be used, but it doesn't suit for
pci bar allocation. So I resulted in new API, pci_region which
encapsulates region allocation and overflow checks.
The first patch introduces pci_region, and the second patch fixes
the overflow case with pci_region.
Isaku Yamahata (2):
pci: introduce pci_region to manage pci io/memory/prefmemory regions.
pciinit: use pci_region functions.
Makefile | 3 +-
src/pci_region.c | 77 ++++++++++++++++++++++++++++++++++
src/pciinit.c | 122 ++++++++++++++++++++++++++---------------------------
src/util.h | 28 ++++++++++++
4 files changed, 167 insertions(+), 63 deletions(-)
create mode 100644 src/pci_region.c
next reply other threads:[~2010-10-28 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 5:04 Isaku Yamahata [this message]
2010-10-28 5:04 ` [Qemu-devel] [PATCH v2 1/2] pci: introduce pci_region to manage pci io/memory/prefmemory regions Isaku Yamahata
2010-10-28 5:56 ` [Qemu-devel] " Michael S. Tsirkin
2010-10-28 6:23 ` Isaku Yamahata
2010-10-28 5:04 ` [Qemu-devel] [PATCH v2 2/2] pciinit: use pci_region functions Isaku Yamahata
2010-10-28 6:33 ` [Qemu-devel] " Michael S. Tsirkin
2010-10-28 7:26 ` 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=cover.1288242111.git.yamahata@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=adnan@khaleel.us \
--cc=cam@cs.ualberta.ca \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).