From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Szymon Durawa <szymon.durawa@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Dan Williams <dan.j.williams@intel.com>,
Lukas Wunner <lukas@wunner.de>,
linux-pci@vger.kernel.org,
Nirmal Patel <nirmal.patel@linux.intel.com>
Subject: Re: [PATCH v2 0/8] VMD add second rootbus support
Date: Wed, 20 Nov 2024 10:10:21 +0100 [thread overview]
Message-ID: <20241120101021.00007003@linux.intel.com> (raw)
In-Reply-To: <20241115174855.GA2045200@bhelgaas>
On Fri, 15 Nov 2024 11:48:55 -0600
Bjorn Helgaas <helgaas@kernel.org> wrote:
> The "BUS0" nomenclature seems heavily embedded in the vmd driver but
> is really a misnomer. Maybe that reflects similar terminology in an
> internal spec? Any hard-wiring of bus numbers reflects a property of
> the way a *Root Port* works, so using the right name will make this
> easier to understand, especially since there are other Root Ports with
> the same hard wiring.
Hi Bjorn,
It is named as BUS_0 and BUS_1 because it refers to kernel's
pci_create_root_bus()`, we simplified it for better code wrapping.
Looks like it confuses you, do you like ROOT_BUS0 and ROOT_BUS1 better?
I don't see better fit than "root bus" because we are creating new root buses
accordingly.
Internally, it is called as "VMD domain" and each VMD Domain is presented as
separate pci root bus.
The original naming is presented in the sysfs links:
- "domain" -> root bus 0
= "domain1" -> root bus 1
i.e:
domain -> pci10000:e0/pci_bus/10000:e0
domain1 -> pci10000:e1/pci_bus/10000:e1
Thanks,
Mariusz
next prev parent reply other threads:[~2024-11-20 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 9:22 [PATCH v2 0/8] VMD add second rootbus support Szymon Durawa
2024-11-15 17:48 ` Bjorn Helgaas
2024-11-20 9:10 ` Mariusz Tkaczyk [this message]
2024-11-20 21:07 ` Bjorn Helgaas
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=20241120101021.00007003@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=nirmal.patel@linux.intel.com \
--cc=szymon.durawa@linux.intel.com \
/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.