qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: stefano.stabellini@eu.citrix.com, jan.kiszka@siemens.com,
	seabios@seabios.org, allen.m.kay@intel.com,
	qemu-devel@nongnu.org, jean.guyader@gmail.com
Subject: [Qemu-devel] Re: [PATCH 0/8] seabios: pci: multi pci bus support
Date: Thu, 17 Jun 2010 14:17:20 +0300	[thread overview]
Message-ID: <20100617111720.GA10616@redhat.com> (raw)
In-Reply-To: <cover.1276771355.git.yamahata@valinux.co.jp>

On Thu, Jun 17, 2010 at 08:03:08PM +0900, Isaku Yamahata wrote:
> This patch set allows seabios to initialize multi pci bus and 64bit BAR.
> 
> Currently seabios is able to initialize only pci root bus.
> However multi pci bus support is wanted because
>   - more pci bus is wanted in qemu for many slots
>   - pci express support is commin in qemu which requires multi pci bus.
> those patches on Qemu part are under way, though.

Not that I object, but - does it really require multi bus? Why?

> Isaku Yamahata (8):
>   seabios: pci: introduce foreachpci_in_bus() helper macro.
>   seabios: pciinit: factor out pci bar region allocation logic.
>   seabios: pciinit: make pci memory space assignment 64bit aware.
>   seabios: pciinit: make pci bar assigner preferchable memory aware.
>   seabios: pciinit: factor out bar offset calculation.
>   seabios: pciinit: make bar offset calculation pci bridge aware.
>   seabios: pciinit: pci bridge bus initialization.
>   seabios: pciinit: initialize pci bridge filtering registers.
> 
>  src/pci.c     |   30 ++++++
>  src/pci.h     |   11 ++
>  src/pciinit.c |  310 ++++++++++++++++++++++++++++++++++++++++++++++++--------
>  3 files changed, 306 insertions(+), 45 deletions(-)

  parent reply	other threads:[~2010-06-17 11:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 11:03 [Qemu-devel] [PATCH 0/8] seabios: pci: multi pci bus support Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 1/8] seabios: pci: introduce foreachpci_in_bus() helper macro Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 2/8] seabios: pciinit: factor out pci bar region allocation logic Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 3/8] seabios: pciinit: make pci memory space assignment 64bit aware Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 4/8] seabios: pciinit: make pci bar assigner preferchable memory aware Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 5/8] seabios: pciinit: factor out bar offset calculation Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 6/8] seabios: pciinit: make bar offset calculation pci bridge aware Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 7/8] seabios: pciinit: pci bridge bus initialization Isaku Yamahata
2010-06-17 11:03 ` [Qemu-devel] [PATCH 8/8] seabios: pciinit: initialize pci bridge filtering registers Isaku Yamahata
2010-06-17 11:17 ` Michael S. Tsirkin [this message]
2010-06-18  2:02   ` [Qemu-devel] Re: [PATCH 0/8] seabios: pci: multi pci bus support 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=20100617111720.GA10616@redhat.com \
    --to=mst@redhat.com \
    --cc=allen.m.kay@intel.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jean.guyader@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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).