From: Tal Shnaiderman <talshn@nvidia.com>
To: "Menon, Ranjit" <ranjit.menon@intel.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
"dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>,
"harini.ramakrishnan@microsoft.com"
<harini.ramakrishnan@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] bus/pci: support segment value as address domain on Windows
Date: Sun, 13 Sep 2020 14:50:45 +0000 [thread overview]
Message-ID: <BY5PR12MB432308491F9EE8F852058BACA4220@BY5PR12MB4323.namprd12.prod.outlook.com> (raw)
In-Reply-To: <0897c65e-a90c-e02e-e1f4-44a28993615f@intel.com>
> Subject: Re: [PATCH] bus/pci: support segment value as address domain on
> Windows
>
> Thanks for the explanation, Tal.
>
> I had always been curious how Windows stores the PCIe segment (domain)
> number.
>
> On VMs hosted on Hyper-V, the VF segment numbers are always in the high
> 16-bit values.
>
> Is this documented somewhere, or did you find this by experimentation?
>
Hi Ranjit,
I didn’t find documentation on it.
I found it by experimentation on a Windows VM with several VFs using the same virtual switch, Linux VFs showed the same behavior but they are being detected using the domain value which is different.
>
> ranjit m.
next prev parent reply other threads:[~2020-09-13 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 11:43 Tal Shnaiderman
2020-09-09 23:21 ` Narcisa Ana Maria Vasile
2020-09-10 7:30 ` Tal Shnaiderman
2020-09-10 17:21 ` Menon, Ranjit
2020-09-13 14:50 ` Tal Shnaiderman [this message]
2020-09-10 17:57 ` Dmitry Kozlyuk
2020-09-13 14:54 ` Tal Shnaiderman
2020-09-16 18:32 ` Ranjit Menon
2020-10-14 9:01 ` Thomas Monjalon
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=BY5PR12MB432308491F9EE8F852058BACA4220@BY5PR12MB4323.namprd12.prod.outlook.com \
--to=talshn@nvidia.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=thomas@monjalon.net \
/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).