All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmal Patel <nirmal.patel@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Nirmal Patel <nirmal.patel@intel.com>,
	linux-pci@vger.kernel.org, bhelgaas@google.com,
	kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
	lpieralisi@kernel.org
Subject: Re: [PATCH v2] PCI: vmd: Only assign OSC features in bare metal OS.
Date: Mon, 13 Jul 2026 11:14:57 -0700	[thread overview]
Message-ID: <20260713111457.00006fa8@linux.intel.com> (raw)
In-Reply-To: <alOIyYDz_RhsqT8v@ashevche-desk.local>

On Sun, 12 Jul 2026 15:30:01 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Fri, Jul 10, 2026 at 08:05:58PM +0000, Nirmal Patel 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.  
> 
> ...
> 
> > v2 : Added descriptive boolean and removed period from commit
> > message.  
> 
> It's still in the $Subject. You probably misinterpreted the
> comment(s).
My bad, i removed (_). Let me correct. Is (_OSC) in subject okay?
> 
> ...
> 
> > +	/* Non-zero offset means guest/direct assign view. */
> > +	vmd_in_guest = offset[0] || offset[1];  
> 
> + Blank line?
Ack.
> 
> >  	/*
> >  	 * 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;  
> 
> ...
> 
> > -
> > 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.*/  
> 
> Missing space before */.
Ack.
> 
> > +	if (!vmd_in_guest)
> > +
> > vmd_copy_host_bridge_flags(pci_find_host_bridge(vmd->dev->bus),
> > +
> > to_pci_host_bridge(vmd->bus->bridge));  
> 


  reply	other threads:[~2026-07-13 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 20:05 [PATCH v2] PCI: vmd: Only assign OSC features in bare metal OS Nirmal Patel
2026-07-10 20:15 ` sashiko-bot
2026-07-12 12:30 ` Andy Shevchenko
2026-07-13 18:14   ` Nirmal Patel [this message]
2026-07-13 21:09     ` Andy Shevchenko

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=20260713111457.00006fa8@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 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.