From: Jason Andryuk <jason.andryuk@amd.com>
To: Mykyta Poturai <Mykyta_Poturai@epam.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Stewart Hildebrand" <stewart.hildebrand@amd.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Community Manager" <community.manager@xenproject.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger@xenproject.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Roger Pau Monné" <roger@xenproject.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH v4 4/5] vpci: add SR-IOV support for PVH Dom0
Date: Mon, 19 Oct 2026 20:29:21 -0400 [thread overview]
Message-ID: <9c6c4c93-9782-4192-8528-fb05ec1ebce4@amd.com> (raw)
In-Reply-To: <25df5d8d-7cd3-4344-86e1-8af883fa9a65@amd.com>
On 2026-10-19 17:47, Jason Andryuk wrote:
> On 2026-10-15 10:08, Mykyta Poturai wrote:
>> From: Stewart Hildebrand <stewart.hildebrand@amd.com>
>> + struct vpci_bar *bar = &bars[i];
>> +
>> + /*
>> + * The upper half of a 64-bit BAR holds no address or size of
>> its own;
>> + * the handlers reach the lower half through its type alone.
>> + */
>> + if ( pf_bar->type == VPCI_BAR_MEM64_HI )
>> + {
>> + bar->type = VPCI_BAR_MEM64_HI;
>> + continue;
>> + }
>> +
>> + if ( pf_bar->type != VPCI_BAR_MEM32 &&
>> + pf_bar->type != VPCI_BAR_MEM64_LO )
>> + continue;
>> +
>> + bar->addr = pf_bar->addr + vf_idx * pf_bar->size;
> AIUI, the PF has the SR-IOV BARs, which are sized like normal. But I
> thought the pf_bar->size needs to be reduced by some factor to get the
> per-VF size. I can't find where that is done. Or am I wrong about this?
Ok, I looked around and I think I was wrong. The SR-IOV bar returns the
single VF size, and it is up to the OS to multiply by the number of VFs.
Thanks,
Jason
next prev parent reply other threads:[~2026-10-20 0:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:08 [PATCH v4 0/5] Implement SR-IOV support for PVH Mykyta Poturai
2026-10-15 14:08 ` [PATCH v4 2/5] vpci: use a local variable for the BAR rangeset Mykyta Poturai
2026-10-19 19:09 ` Jason Andryuk
2026-10-15 14:08 ` [PATCH v4 1/5] vpci: Export functions required for SR-IOV support Mykyta Poturai
2026-10-19 19:09 ` Jason Andryuk
2026-10-15 14:08 ` [PATCH v4 4/5] vpci: add SR-IOV support for PVH Dom0 Mykyta Poturai
2026-10-19 21:47 ` Jason Andryuk
2026-10-20 0:29 ` Jason Andryuk [this message]
2026-10-15 14:08 ` [PATCH v4 3/5] vpci: allow queueing of mapping operations Mykyta Poturai
2026-10-19 19:46 ` Jason Andryuk
2026-10-15 14:08 ` [PATCH v4 5/5] vpci: add SR-IOV support for DomUs Mykyta Poturai
2026-10-20 0:19 ` Jason Andryuk
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=9c6c4c93-9782-4192-8528-fb05ec1ebce4@amd.com \
--to=jason.andryuk@amd.com \
--cc=Mykyta_Poturai@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=community.manager@xenproject.org \
--cc=dpsmith@apertussolutions.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=roger@xenproject.com \
--cc=roger@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=stewart.hildebrand@amd.com \
--cc=xen-devel@lists.xenproject.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 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.