All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	Linux PCI <linux-pci@vger.kernel.org>,
	Dave Airlie <airlied@linux.ie>,
	"Deucher, Alexander" <alexander.deucher@amd.com>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] PCI: pci_unignore_hotplug()
Date: Fri, 6 Mar 2015 12:49:20 -0600	[thread overview]
Message-ID: <20150306184920.GI20077@google.com> (raw)
In-Reply-To: <CADnq5_PDjww+TkPWVV7HLLA50az2n20SfD5ShVp+OpT8Cy4Dew@mail.gmail.com>

On Tue, Feb 24, 2015 at 03:23:27PM -0500, Alex Deucher wrote:
> On Tue, Feb 24, 2015 at 3:12 PM, Alex Williamson
> <alex.williamson@redhat.com> wrote:
> > I'd kinda like to use pci_ignore_hotplug() for devices in use by a
> > user via vfio-pci, but the interface seems only partially implemented
> > since we can only set ignore_hotplug and not clear it.  This adds the
> > capability to clear the flag and applies it as seems to be appropriate
> > to the existing users.  I don't have a system with power control for
> > a radeon or nouveau device, so I'd certainly appreciate testing.  It
> > seems though that once the device is in D0, we've passed the critical
> > point where the device could be accidentally unplugged.  Thanks,
> 
> Something re-broke this recently.  See:
> https://bugzilla.kernel.org/show_bug.cgi?id=61891
> https://bugzilla.kernel.org/show_bug.cgi?id=89731

I'm not opposed to adding pci_unignore_hotplug() when we have users for it.
I don't really want to throw in the nouveau and radeon changes while there
are open issues in the same area, though.

I haven't looked at the bugzillas above.  Let me know if I should.

Bjorn

WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <bhelgaas@google.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	"Deucher, Alexander" <alexander.deucher@amd.com>
Subject: Re: [PATCH 0/2] PCI: pci_unignore_hotplug()
Date: Fri, 6 Mar 2015 12:49:20 -0600	[thread overview]
Message-ID: <20150306184920.GI20077@google.com> (raw)
In-Reply-To: <CADnq5_PDjww+TkPWVV7HLLA50az2n20SfD5ShVp+OpT8Cy4Dew@mail.gmail.com>

On Tue, Feb 24, 2015 at 03:23:27PM -0500, Alex Deucher wrote:
> On Tue, Feb 24, 2015 at 3:12 PM, Alex Williamson
> <alex.williamson@redhat.com> wrote:
> > I'd kinda like to use pci_ignore_hotplug() for devices in use by a
> > user via vfio-pci, but the interface seems only partially implemented
> > since we can only set ignore_hotplug and not clear it.  This adds the
> > capability to clear the flag and applies it as seems to be appropriate
> > to the existing users.  I don't have a system with power control for
> > a radeon or nouveau device, so I'd certainly appreciate testing.  It
> > seems though that once the device is in D0, we've passed the critical
> > point where the device could be accidentally unplugged.  Thanks,
> 
> Something re-broke this recently.  See:
> https://bugzilla.kernel.org/show_bug.cgi?id=61891
> https://bugzilla.kernel.org/show_bug.cgi?id=89731

I'm not opposed to adding pci_unignore_hotplug() when we have users for it.
I don't really want to throw in the nouveau and radeon changes while there
are open issues in the same area, though.

I haven't looked at the bugzillas above.  Let me know if I should.

Bjorn
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-03-06 18:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 20:12 [PATCH 0/2] PCI: pci_unignore_hotplug() Alex Williamson
2015-02-24 20:12 ` Alex Williamson
2015-02-24 20:12 ` [PATCH 1/2] pci: Add reciprocal function for pci_ignore_hotplug() Alex Williamson
2015-02-24 20:12   ` Alex Williamson
2015-02-24 20:12 ` [PATCH 2/2] nouveau/radeon: Un-ignore hotplug on resume Alex Williamson
2015-02-24 20:12   ` Alex Williamson
2015-02-24 20:23 ` [PATCH 0/2] PCI: pci_unignore_hotplug() Alex Deucher
2015-03-06 18:49   ` Bjorn Helgaas [this message]
2015-03-06 18:49     ` Bjorn Helgaas
2015-03-06 22:12     ` Alex Deucher

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=20150306184920.GI20077@google.com \
    --to=bhelgaas@google.com \
    --cc=airlied@linux.ie \
    --cc=alex.williamson@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.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 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.