All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: skandasa@cisco.com, adnan@khaleel.us, wexu2@cisco.com,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, etmartin@cisco.com
Subject: [Qemu-devel] Re: [PATCH v8 07/11] pci: introduce a parser for pci device path
Date: Mon, 15 Nov 2010 11:03:48 +0200	[thread overview]
Message-ID: <20101115090348.GH7948@redhat.com> (raw)
In-Reply-To: <20101115085740.GH27722@valinux.co.jp>

On Mon, Nov 15, 2010 at 05:57:40PM +0900, Isaku Yamahata wrote:
> On Mon, Nov 15, 2010 at 10:06:13AM +0200, Michael S. Tsirkin wrote:
> > On Mon, Nov 15, 2010 at 04:30:43PM +0900, Isaku Yamahata wrote:
> > > introduce a function to parse pci device path of
> > > the format, [Domain:]Slot.Function:Slot.Function....:Slot.Function.
> > > 
> > > Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
> > 
> > Hmm.
> > How about we use openfirmware path like what Gleb's patch does,
> > with a fallback to bus:dev.fn for when it's unambiguous?
> 
> Okay, let me check my understanding of the format.
> 
> The openfirmware path in pci case looks like
> /pci@<ioport>/<device name>@<slot>,<func>/.../<device name>@<slot>,<func>
> 
> "pci@<ioport>" corresponds to pci domain. So <mmio address> should be
> also supported in addition to <ioport>.
> 
Correct.

> Maybe we'd like "<device name>@" to be optional.
> So the parser would accept something like
> /{<ioport>, <mmio addr>}/<slot>,<func>/.../<slot>,<func>
My patch series has pci_dev_fw_name() function that fills in <device name>
for you, so no reason to make it optional. If you still want to make it
optional @ should stay, so it should be /@ioport/@slot.func/

--
			Gleb.

  reply	other threads:[~2010-11-15  9:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  7:30 [Qemu-devel] [PATCH v8 00/11] pcie port switch emulators Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 01/11] pci: revise pci command register initialization Isaku Yamahata
2010-11-15  8:09   ` [Qemu-devel] " Michael S. Tsirkin
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 02/11] pci: clean up pci command register io/memory bit initialization Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 03/11] pci: fix accesses to pci status register Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 04/11] pci: clean up of " Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 05/11] pcie_regs.h: more constants Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 06/11] pcie/aer: helper functions for pcie aer capability Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 07/11] pci: introduce a parser for pci device path Isaku Yamahata
2010-11-15  8:06   ` [Qemu-devel] " Michael S. Tsirkin
2010-11-15  8:57     ` Isaku Yamahata
2010-11-15  9:03       ` Gleb Natapov [this message]
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 08/11] pcie/aer: glue aer error injection into qemu monitor Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 09/11] ioh3420: support aer Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 10/11] x3130/upstream: " Isaku Yamahata
2010-11-15  7:30 ` [Qemu-devel] [PATCH v8 11/11] x3130/downstream: " 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=20101115090348.GH7948@redhat.com \
    --to=gleb@redhat.com \
    --cc=adnan@khaleel.us \
    --cc=etmartin@cisco.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=skandasa@cisco.com \
    --cc=wexu2@cisco.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 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.