qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Isaku Yamahata <yamahata@valinux.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/2] pci: don't overwrite pci header type.
Date: Wed, 16 Jun 2010 20:38:18 +0900	[thread overview]
Message-ID: <20100616113818.GA25458@valinux.co.jp> (raw)
In-Reply-To: <20100616111944.GA5661@redhat.com>

On Wed, Jun 16, 2010 at 02:19:44PM +0300, Michael S. Tsirkin wrote:
> > > > Apb host bridge specifies PCI_HEADER_TYPE_BRIDGE in PCIDeviceInfo,
> > > > on the other hand pbc_pci_host_init() sets the register
> > > > to PCI_HEADER_TYPE_NORMAL.
> > > > To be honest I don't know why it does so, but that is what Blue wants.
> > > 
> > > BTW I think it would be prettier to have is_bridge instead of header_type
> > > as a qdev property. Agree?
> > 
> > The spec version 3.0 defines three header types.
> > 0:normal device, 1:pci-to-pci bridge, 2:card bus bridge
> > So I'd like the name a bit more generic than is_bridge.
> > Any suggestion?
> 
> Could we just have functions that set up header for
> each type, such as
> pci_init_normal_header()
> pci_init_p2p_bridge_header()
> pci_init_cardbus_header()

I see. You mean device specific initialization function should
call one of them. Then header_type property will be dropped.

I'll split pci p2p bridge related functions into a file
at first. Then introduce helper functions.
-- 
yamahata

  reply	other threads:[~2010-06-16 11:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15  5:06 [Qemu-devel] [PATCH 0/2] pci: multi-function bit fixes Isaku Yamahata
2010-06-15  5:06 ` [Qemu-devel] [PATCH 1/2] pci: set PCI multi-function bit appropriately Isaku Yamahata
2010-06-15  5:06 ` [Qemu-devel] [PATCH 2/2] pci: don't overwrite pci header type Isaku Yamahata
2010-06-15  9:12   ` [Qemu-devel] " Michael S. Tsirkin
2010-06-16  2:20     ` Isaku Yamahata
2010-06-16  8:54       ` Michael S. Tsirkin
2010-06-16  9:43         ` Isaku Yamahata
2010-06-16 11:19           ` Michael S. Tsirkin
2010-06-16 11:38             ` Isaku Yamahata [this message]
2010-06-16 12:43               ` Michael S. Tsirkin
2010-06-16 18:41         ` Blue Swirl
2010-06-16 18:51           ` Michael S. Tsirkin
2010-06-16 19:02             ` Blue Swirl
2010-06-16 19:22               ` Michael S. Tsirkin
2010-06-16 19:59                 ` Blue Swirl
2010-06-16 20:12                 ` Anthony Liguori
2010-06-15  9:42   ` [Qemu-devel] " malc

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=20100616113818.GA25458@valinux.co.jp \
    --to=yamahata@valinux.co.jp \
    --cc=blauwirbel@gmail.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).