From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Chen, Jiqian" <Jiqian.Chen@amd.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Huang, Ray" <Ray.Huang@amd.com>
Subject: Re: [PATCH v2 2/8] vpci/header: Emulate legacy capability list for host
Date: Wed, 16 Apr 2025 09:32:11 +0200 [thread overview]
Message-ID: <Z_9c-8V1OwhnWVSW@macbook.lan> (raw)
In-Reply-To: <BL1PR12MB58493D18F9F533FE3D928607E7BD2@BL1PR12MB5849.namprd12.prod.outlook.com>
On Wed, Apr 16, 2025 at 02:51:18AM +0000, Chen, Jiqian wrote:
> On 2025/4/15 18:10, Roger Pau Monné wrote:
> > On Wed, Apr 09, 2025 at 02:45:22PM +0800, Jiqian Chen wrote:
> >> + while ( next && ttl )
> >> + {
> >> + unsigned int pos = next;
> >> +
> >> + next = pci_find_next_cap_ttl(pdev->sbdf, pos + PCI_CAP_LIST_NEXT,
> >> + caps, n, &ttl);
> >> +
> >> + rc = vpci_add_register(pdev->vpci, vpci_hw_read8, NULL,
> >> + pos + PCI_CAP_LIST_ID, 1, NULL);
> >> + if ( rc )
> >> + return rc;
> >> +
> >> + rc = vpci_add_register(pdev->vpci, vpci_read_val, NULL,
> >> + pos + PCI_CAP_LIST_NEXT, 1,
> >> + (void *)(uintptr_t)next);
> >> + if ( rc )
> >> + return rc;
> >> +
> >> + next &= ~3;
> >> + }
> >> + }
> >> +
> >> + /* Utilize rsvdp_mask to hide PCI_STATUS_CAP_LIST from the guest. */
> >> + rc = vpci_add_register_mask(pdev->vpci, vpci_hw_read16, vpci_hw_write16,
> >> + PCI_STATUS, 2, NULL,
> >> + PCI_STATUS_RO_MASK &
> >> + ~(mask_cap_list ? PCI_STATUS_CAP_LIST : 0),
> >> + PCI_STATUS_RW1C_MASK,
> >> + mask_cap_list ? PCI_STATUS_CAP_LIST : 0,
> >> + PCI_STATUS_RSVDZ_MASK);
> >
> > One further remark I've forgot to make on the previous reply: I'm
> > unsure we want to do this for dom0, as we in general allow dom0
> > unfiltered write access (unless it's for accesses mediated by Xen).
> This part is the original implementation before my patches.
> If you want to restrict this only for domUs, not for dom0.
Oh, indeed. I was confused thinking it was inside the
!is_hardware_domain() conditional. Leave it like that, your series is
already long enough.
Thanks, Roger.
next prev parent reply other threads:[~2025-04-16 7:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 6:45 [PATCH v2 0/8] Support hiding capability when its initialization fails Jiqian Chen
2025-04-09 6:45 ` [PATCH v2 1/8] driver/pci: Get next capability without passing caps Jiqian Chen
2025-04-10 12:34 ` Jan Beulich
2025-04-11 2:51 ` Chen, Jiqian
2025-04-11 8:00 ` Jan Beulich
2025-04-11 8:08 ` Chen, Jiqian
2025-04-09 6:45 ` [PATCH v2 2/8] vpci/header: Emulate legacy capability list for host Jiqian Chen
2025-04-10 12:40 ` Jan Beulich
2025-04-11 2:54 ` Chen, Jiqian
2025-04-11 8:01 ` Jan Beulich
2025-04-15 9:25 ` Roger Pau Monné
2025-04-15 10:07 ` Chen, Jiqian
2025-04-15 10:08 ` Jan Beulich
2025-04-15 10:23 ` Chen, Jiqian
2025-04-15 10:50 ` Roger Pau Monné
2025-04-15 10:10 ` Roger Pau Monné
2025-04-16 2:51 ` Chen, Jiqian
2025-04-16 7:32 ` Roger Pau Monné [this message]
2025-04-09 6:45 ` [PATCH v2 3/8] vpci/header: Emulate extended " Jiqian Chen
2025-04-15 9:42 ` Roger Pau Monné
2025-04-15 10:11 ` Chen, Jiqian
2025-04-15 9:49 ` Jan Beulich
2025-04-15 10:18 ` Chen, Jiqian
2025-04-15 10:20 ` Jan Beulich
2025-04-09 6:45 ` [PATCH v2 4/8] vpci: Hide capability when it fails to initialize Jiqian Chen
2025-04-15 10:47 ` Roger Pau Monné
2025-04-16 6:07 ` Chen, Jiqian
2025-04-09 6:45 ` [PATCH v2 5/8] vpci: Refactor vpci_remove_register to remove matched registers Jiqian Chen
2025-04-15 11:06 ` Roger Pau Monné
2025-04-09 6:45 ` [PATCH v2 6/8] vpci/rebar: Remove registers when init_rebar() fails Jiqian Chen
2025-04-15 12:59 ` Roger Pau Monné
2025-04-09 6:45 ` [PATCH v2 7/8] vpci/msi: Free MSI resources when init_msi() fails Jiqian Chen
2025-04-15 13:29 ` Roger Pau Monné
2025-04-16 6:16 ` Chen, Jiqian
2025-04-16 7:47 ` Roger Pau Monné
2025-04-09 6:45 ` [PATCH v2 8/8] vpci/msix: Add function to clean MSIX resources Jiqian Chen
2025-04-15 13:45 ` Roger Pau Monné
2025-04-16 6:20 ` Chen, Jiqian
2025-04-16 7:54 ` Roger Pau Monné
2025-04-17 7:34 ` Jan Beulich
2025-04-17 7:38 ` Chen, Jiqian
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=Z_9c-8V1OwhnWVSW@macbook.lan \
--to=roger.pau@citrix.com \
--cc=Jiqian.Chen@amd.com \
--cc=Ray.Huang@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.