From: Nirmal Patel <nirmal.patel@linux.intel.com>
To: Nirmal Patel <nirmal.patel@intel.com>
Cc: <linux-pci@vger.kernel.org>,
bhelgaas@google.com, kwilczynski@kernel.org, mani@kernel.org,
robh@kernel.org, lpieralisi@kernel.org,
Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: Re: [PATCH v3] PCI: vmd: Only assign OSC features in bare metal OS
Date: Mon, 20 Jul 2026 14:22:00 -0700 [thread overview]
Message-ID: <20260720142200.00004842@linux.intel.com> (raw)
In-Reply-To: <20260713220844.561357-1-nirmal.patel@intel.com>
On Mon, 13 Jul 2026 22:08:44 +0000
Nirmal Patel <nirmal.patel@intel.com> wrote:
> Copy valid OSC flags from root bridge only when OS can provide correct
> values. In virtual machine, all of the control features are disabled
> as hypervisor will not passthrough root bridge information to VM.
>
> Signed-off-by: Nirmal Patel <nirmal.patel@linux.intel.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> ---
> v3 : Removed period from commit and added a black line.
> v2 : Added descriptive boolean and removed period from commit message.
> ---
> ---
> drivers/pci/controller/vmd.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/controller/vmd.c
> b/drivers/pci/controller/vmd.c index d4ae250d4bc6..7c7d110290d6 100644
> --- a/drivers/pci/controller/vmd.c
> +++ b/drivers/pci/controller/vmd.c
> @@ -782,6 +782,7 @@ static int vmd_enable_domain(struct vmd_dev *vmd,
> unsigned long features) resource_size_t membar2_offset = 0x2000;
> struct pci_bus *child;
> struct pci_dev *dev;
> + bool vmd_in_guest;
> int ret;
>
> /*
> @@ -862,14 +863,16 @@ static int vmd_enable_domain(struct vmd_dev
> *vmd, unsigned long features) .parent = res,
> };
>
> + /* Non-zero offset means guest/direct assign view. */
> + vmd_in_guest = offset[0] || offset[1];
> +
> /*
> * Currently MSI remapping must be enabled in guest
> passthrough mode
> * due to some missing interrupt remapping plumbing. This is
> probably
> * acceptable because the guest is usually CPU-limited and
> MSI
> * remapping doesn't become a performance bottleneck.
> */
> - if (!(features & VMD_FEAT_CAN_BYPASS_MSI_REMAP) ||
> - offset[0] || offset[1]) {
> + if (!(features & VMD_FEAT_CAN_BYPASS_MSI_REMAP) ||
> vmd_in_guest) { ret = vmd_alloc_irqs(vmd);
> if (ret)
> return ret;
> @@ -910,8 +913,10 @@ static int vmd_enable_domain(struct vmd_dev
> *vmd, unsigned long features) return -ENODEV;
> }
>
> -
> vmd_copy_host_bridge_flags(pci_find_host_bridge(vmd->dev->bus),
> -
> to_pci_host_bridge(vmd->bus->bridge));
> + /* Don't copy _OSC control flags in VM, it disables
> features. */
> + if (!vmd_in_guest)
> +
> vmd_copy_host_bridge_flags(pci_find_host_bridge(vmd->dev->bus),
> +
> to_pci_host_bridge(vmd->bus->bridge));
> vmd_attach_resources(vmd);
> if (vmd->irq_domain)
Gentle reminder.
Thanks
nirmal
prev parent reply other threads:[~2026-07-20 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 22:08 [PATCH v3] PCI: vmd: Only assign OSC features in bare metal OS Nirmal Patel
2026-07-13 22:18 ` sashiko-bot
2026-07-20 21:22 ` Nirmal Patel [this message]
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=20260720142200.00004842@linux.intel.com \
--to=nirmal.patel@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=nirmal.patel@intel.com \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox