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: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v2 0/5] pci/pcie: implement ARI enable bit correctly
Date: Thu, 27 Jan 2011 10:42:53 +0200	[thread overview]
Message-ID: <20110127084253.GD28784@redhat.com> (raw)
In-Reply-To: <cover.1296111201.git.yamahata@valinux.co.jp>

On Thu, Jan 27, 2011 at 03:56:34PM +0900, Isaku Yamahata wrote:
> Changes v1 -> v2:
> - dropped PCI_DEVFN_MAX
> - use uint8_t for devfn instead of int
> - move pcie_check_slot into pci.h and made it static inline
> - minor clean ups

So I put this on the pci branch but
we need to at least consider the following:
- command line/monitor/qmp: do we need to tweak it to force slot 0?
  Or just declare that slot >= 1 should be used to support
  insane # of functions?
- management needs to learn about ARI anyway, so
  maybe a clean change is better?
- multifunction: need to detect and support ARI:
  see pci_init_multifunction.
- And, we still did not implement the idea
  where parent id for the device is specified.

So while I don't think these patches make anything
worse, I think I'll give these a bit of time to stew
on my branch so we can hopefully see a bit more of the
full picture.

> Isaku Yamahata (5):
>   pci: replace the magic, 256, for the maximum of devfn
>   pci: use devfn for pci_find_device() instead of (slot, fn) pair
>   pci/pcie: make pci_find_device() ARI aware.
>   pci: use PCI_SLOT in pci_get_bus_devfn()
>   pci: use uint8_t for devfn_min
> 
>  hw/pci-hotplug.c   |    5 +++--
>  hw/pci.c           |   18 ++++++++++++------
>  hw/pci.h           |   51 +++++++++++++++++++++++++++++++++++++++++++++++----
>  hw/pci_host.c      |    2 +-
>  hw/pci_internals.h |    4 ++--
>  hw/pcie.c          |   13 -------------
>  hw/pcie.h          |    1 -
>  hw/pcie_host.c     |    3 +--
>  8 files changed, 66 insertions(+), 31 deletions(-)

  parent reply	other threads:[~2011-01-27  8:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27  6:56 [Qemu-devel] [PATCH v2 0/5] pci/pcie: implement ARI enable bit correctly Isaku Yamahata
2011-01-27  6:56 ` [Qemu-devel] [PATCH v2 1/5] pci: replace the magic, 256, for the maximum of devfn Isaku Yamahata
2011-01-27  7:09   ` [Qemu-devel] " Michael S. Tsirkin
2011-01-27  6:56 ` [Qemu-devel] [PATCH v2 2/5] pci: use devfn for pci_find_device() instead of (slot, fn) pair Isaku Yamahata
2011-01-27  7:11   ` [Qemu-devel] " Michael S. Tsirkin
2011-01-27  6:56 ` [Qemu-devel] [PATCH v2 3/5] pci/pcie: make pci_find_device() ARI aware Isaku Yamahata
2011-01-27  7:30   ` [Qemu-devel] " Michael S. Tsirkin
2011-01-27  6:56 ` [Qemu-devel] [PATCH v2 4/5] pci: use PCI_SLOT in pci_get_bus_devfn() Isaku Yamahata
2011-01-27  7:31   ` [Qemu-devel] " Michael S. Tsirkin
2011-01-27  6:56 ` [Qemu-devel] [PATCH v2 5/5] pci: use uint8_t for devfn_min Isaku Yamahata
2011-01-27  7:32   ` [Qemu-devel] " Michael S. Tsirkin
2011-01-27  8:42 ` Michael S. Tsirkin [this message]
2011-01-27 10:22   ` [Qemu-devel] Re: [PATCH v2 0/5] pci/pcie: implement ARI enable bit correctly 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=20110127084253.GD28784@redhat.com \
    --to=mst@redhat.com \
    --cc=qemu-devel@nongnu.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 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).