All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Mykyta Poturai <Mykyta_Poturai@epam.com>,
	Stewart Hildebrand <stewart.hildebrand@amd.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v3 6/7] vpci: add SR-IOV support for DomUs
Date: Tue, 21 Apr 2026 16:55:25 +0200	[thread overview]
Message-ID: <c8e664fd-59f8-482d-ad48-99ff59842682@suse.com> (raw)
In-Reply-To: <1aaf1a087ca0003d943d43c55500b3ab84195cf5.1775742115.git.mykyta_poturai@epam.com>

On 09.04.2026 16:01, Mykyta Poturai wrote:
> From: Stewart Hildebrand <stewart.hildebrand@amd.com>
> 
> Emulate guest BAR register values based on PF BAR values for VFs.
> This allows creating a guest view of the normal BAR registers and emulates
> the size and properties as it is done during PCI device enumeration by
> the guest.
> 
> Expose VID/DID and class/revision to the guest.
> 
> Note, that VFs ROM BAR is read-only and is all zeros, but VF may provide
> access to the PFs ROM via emulation and is not implemented.
> 
> Signed-off-by: Stewart Hildebrand <stewart.hildebrand@amd.com>
> Signed-off-by: Mykyta Poturai <mykyta_poturai@epam.com>

So this change is merely to avoid having yet another gap on the road to
DomU support in vPCI? I.e. there's no claim or expectation that VFs
could now be used in DomU-s?

Jan


  reply	other threads:[~2026-04-21 14:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 14:01 [PATCH v3 0/7] Implement SR-IOV support for PVH Mykyta Poturai
2026-04-09 14:01 ` [PATCH v3 2/7] vpci: rename and export vpci_guest_mem_bar_{read,write} Mykyta Poturai
2026-04-22 10:27   ` Roger Pau Monné
2026-04-09 14:01 ` [PATCH v3 1/7] vpci: rename and export vpci_modify_bars Mykyta Poturai
2026-04-09 14:01 ` [PATCH v3 3/7] vpci: Use pervcpu ranges for BAR mapping Mykyta Poturai
2026-04-22 11:00   ` Roger Pau Monné
2026-04-22 12:04     ` Jan Beulich
2026-04-22 14:20       ` Roger Pau Monné
2026-04-09 14:01 ` [PATCH v3 4/7] vpci: allow queueing of mapping operations Mykyta Poturai
2026-04-22 11:38   ` Roger Pau Monné
2026-04-09 14:01 ` [PATCH v3 6/7] vpci: add SR-IOV support for DomUs Mykyta Poturai
2026-04-21 14:55   ` Jan Beulich [this message]
2026-04-24  6:34     ` Mykyta Poturai
2026-04-09 14:01 ` [PATCH v3 5/7] vpci: add SR-IOV support for PVH Dom0 Mykyta Poturai
2026-04-09 15:27   ` Daniel P. Smith
2026-04-21 14:43   ` Jan Beulich
2026-04-23 10:12     ` Mykyta Poturai
2026-05-04  5:37       ` Jan Beulich
2026-05-06  9:39         ` Mykyta Poturai
2026-05-06 11:54           ` Jan Beulich
2026-05-07 20:40             ` Volodymyr Babchuk
2026-05-08  5:52               ` Jan Beulich
2026-05-08  5:52               ` Jan Beulich
2026-05-11 14:10                 ` Volodymyr Babchuk
2026-05-12  6:20                   ` Jan Beulich
2026-05-12  7:32                     ` Mykyta Poturai
2026-05-12  8:58                       ` Roger Pau Monné
2026-05-12 10:28                         ` Volodymyr Babchuk
2026-05-12 13:22                           ` Roger Pau Monné
2026-05-12 10:44                         ` Jan Beulich
2026-05-12 11:11                           ` Roger Pau Monné
2026-04-22 14:19   ` Roger Pau Monné
2026-04-28 20:05   ` Stewart Hildebrand
2026-04-09 14:01 ` [PATCH v3 7/7] docs: Update SR-IOV support status Mykyta Poturai
2026-04-21 14:56   ` Jan Beulich

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=c8e664fd-59f8-482d-ad48-99ff59842682@suse.com \
    --to=jbeulich@suse.com \
    --cc=Mykyta_Poturai@epam.com \
    --cc=roger.pau@citrix.com \
    --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.