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>,
"Roger Pau Monné" <roger@xenproject.org>,
"Teddy Astie" <teddy.astie@vates.tech>
Subject: Re: [PATCH v4 1/5] vpci: Export functions required for SR-IOV support
Date: Mon, 19 Oct 2026 15:09:02 -0400 [thread overview]
Message-ID: <62f101ef-7f47-4593-a79e-06abbc18f84c@amd.com> (raw)
In-Reply-To: <5b2721b7213d53232ce912e4f9ce0b4e7b1b39c7.1792072426.git.mykyta_poturai@epam.com>
On 2026-10-15 10:08, Mykyta Poturai wrote:
> From: Stewart Hildebrand <stewart.hildebrand@amd.com>
>
> Rename and export vpci_modify_bars, vpci_guest_mem_bar_{read,write}
>
> Signed-off-by: Stewart Hildebrand <stewart.hildebrand@amd.com>
> Signed-off-by: Mykyta Poturai <mykyta_poturai@epam.com>
> Reviewed-by: Teddy Astie <teddy.astie@vates.tech>
Reviewed-by: Jason Andryuk <jason.andryuk@amd.com>
next prev parent reply other threads:[~2026-10-19 19:17 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 1/5] vpci: Export functions required for SR-IOV support Mykyta Poturai
2026-10-19 19:09 ` Jason Andryuk [this message]
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 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
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
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=62f101ef-7f47-4593-a79e-06abbc18f84c@amd.com \
--to=jason.andryuk@amd.com \
--cc=Mykyta_Poturai@epam.com \
--cc=roger@xenproject.org \
--cc=stewart.hildebrand@amd.com \
--cc=teddy.astie@vates.tech \
--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.