public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org, Yu Zhao <yu.zhao@intel.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] pci: dmar/intr_remapping/iov use physfn to search drhd
Date: Mon, 10 Aug 2009 09:30:22 -0700	[thread overview]
Message-ID: <20090810093022.710a09f8@jbarnes-g45> (raw)
In-Reply-To: <4A785A57.8050505@kernel.org>

For Dave.

On Tue, 04 Aug 2009 08:57:11 -0700
Yinghai Lu <yinghai@kernel.org> wrote:

> 
> when virtfn is used, we should use physfn to find correct drhd
> 
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> 
> ---
>  drivers/pci/dmar.c           |    5 +++++
>  2 files changed, 12 insertions(+), 1 deletion(-)
> 
> Index: linux-2.6/drivers/pci/dmar.c
> ===================================================================
> --- linux-2.6.orig/drivers/pci/dmar.c
> +++ linux-2.6/drivers/pci/dmar.c
> @@ -493,6 +493,11 @@ dmar_find_matched_drhd_unit(struct pci_d
>  	struct dmar_drhd_unit *dmaru = NULL;
>  	struct acpi_dmar_hardware_unit *drhd;
>  
> +#ifdef CONFIG_PCI_IOV
> +	if (dev->is_virtfn)
> +		dev = dev->physfn;
> +#endif
> +
>  	list_for_each_entry(dmaru, &dmar_drhd_units, list) {
>  		drhd = container_of(dmaru->hdr,
>  				    struct acpi_dmar_hardware_unit,
> 


-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2009-08-10 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 15:57 [PATCH] pci: dmar/intr_remapping/iov use physfn to search drhd Yinghai Lu
2009-08-10 16:30 ` Jesse Barnes [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=20090810093022.710a09f8@jbarnes-g45 \
    --to=jbarnes@virtuousgeek.org \
    --cc=dwmw2@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=yinghai@kernel.org \
    --cc=yu.zhao@intel.com \
    /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