From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: cam@cs.ualberta.ca, seabios@seabios.org, adnan@khaleel.us,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/2] pciinit: fix overflow when bar allocation
Date: Mon, 18 Oct 2010 11:47:42 +0200 [thread overview]
Message-ID: <20101018094742.GA21892@redhat.com> (raw)
In-Reply-To: <cover.1287394119.git.yamahata@valinux.co.jp>
On Mon, Oct 18, 2010 at 06:34:21PM +0900, Isaku Yamahata wrote:
> 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 | 70 +++++++++++++++++++++++++++++++
> src/pciinit.c | 122 ++++++++++++++++++++++++++---------------------------
> src/util.h | 15 +++++++
> 4 files changed, 147 insertions(+), 63 deletions(-)
> create mode 100644 src/pci_region.c
Could you clarify what do you mean by bar overflow please?
next prev parent reply other threads:[~2010-10-18 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 9:34 [Qemu-devel] [PATCH 0/2] pciinit: fix overflow when bar allocation Isaku Yamahata
2010-10-18 9:34 ` [Qemu-devel] [PATCH 1/2] pci: introduce pci_region to manage pci io/memory/prefmemory regions Isaku Yamahata
2010-10-18 9:55 ` [Qemu-devel] " Michael S. Tsirkin
2010-10-19 1:43 ` [Qemu-devel] Re: [SeaBIOS] " Isaku Yamahata
2010-10-18 9:34 ` [Qemu-devel] [PATCH 2/2] pciinit: use pci_region functions Isaku Yamahata
2010-10-18 9:47 ` Michael S. Tsirkin [this message]
2010-10-19 1:56 ` [Qemu-devel] Re: [SeaBIOS] [PATCH 0/2] pciinit: fix overflow when bar allocation 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=20101018094742.GA21892@redhat.com \
--to=mst@redhat.com \
--cc=adnan@khaleel.us \
--cc=cam@cs.ualberta.ca \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--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.