From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
ddutile@redhat.com, linux-kernel@vger.kernel.org,
lenb@kernel.org
Subject: Re: [PATCH v2 0/2] ACPI / PCI: Fix _PRT lookup for ARI enabled devices
Date: Sat, 30 May 2015 01:53:30 +0200 [thread overview]
Message-ID: <3075635.JhZ4D0jF4G@vostro.rjw.lan> (raw)
In-Reply-To: <20150529221848.GD12733@google.com>
On Friday, May 29, 2015 05:18:48 PM Bjorn Helgaas wrote:
> On Tue, May 26, 2015 at 03:11:38PM -0600, Alex Williamson wrote:
> > v2: don't modify entry->id.device
> >
> > In most cases we only use ARI with SR-IOV VFs, which do not support
> > INTx and therefore never hit this problem. However, some non-SR-IOV
> > implementations create multiple PFs, extending beyond the standard
> > 3-bit function numbers with ARI, and do support INTx for those
> > additional functions. This can happen with Solarflare SFC9120
> > adapters. The host driver typically doesn't use INTx, so we also
> > haven't noticed this problem on bare metal, but when we attempt to
> > assign the device to a VM using vfio-pci, we fail trying to setup
> > default INTx signaling. Thanks,
> >
> > Alex
> >
> > ---
> >
> > Alex Williamson (2):
> > PCI: Move pci_ari_enabled() to global header
> > ACPI / PCI: Account for ARI in _PRT lookups
>
> Rafael, do you want this or should I take it?
>
> I put it on my pci/virtualization branch for v4.2.
That's fine. Please feel free to add my ACKs to those if that helps.
Rafael
prev parent reply other threads:[~2015-05-29 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 21:11 Alex Williamson
2015-05-26 21:11 ` [PATCH v2 1/2] PCI: Move pci_ari_enabled() to global header Alex Williamson
2015-05-26 21:11 ` [PATCH v2 2/2] ACPI / PCI: Account for ARI in _PRT lookups Alex Williamson
2015-05-27 15:28 ` [PATCH v2 0/2] ACPI / PCI: Fix _PRT lookup for ARI enabled devices Don Dutile
2015-05-29 22:18 ` Bjorn Helgaas
2015-05-29 23:53 ` Rafael J. Wysocki [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=3075635.JhZ4D0jF4G@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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
all inboxes | Powered by JetHome®