Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Philipp Stanner <pstanner@redhat.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	 Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	dakr@redhat.com,  dri-devel@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>,
	 linux-pci@vger.kernel.org
Subject: Re: [PATCH v7 09/13] PCI: Give pcim_set_mwi() its own devres callback
Date: Fri, 14 Jun 2024 10:15:22 +0200	[thread overview]
Message-ID: <105f167697e4421237884ebece1cf9a28293c762.camel@redhat.com> (raw)
In-Reply-To: <17445053-18a1-a56d-79d0-3b3d3ecab033@linux.intel.com>

On Thu, 2024-06-13 at 20:19 +0300, Ilpo Järvinen wrote:
> On Wed, 5 Jun 2024, Philipp Stanner wrote:
> 
> > Managing pci_set_mwi() with devres can easily be done with its own
> > callback, without the necessity to store any state about it in a
> > device-related struct.
> > 
> > Remove the MWI state from struct pci_devres.
> > Give pcim_set_mwi() a separate devres-callback.
> > 
> > Signed-off-by: Philipp Stanner <pstanner@redhat.com>
> > ---
> >  drivers/pci/devres.c | 29 ++++++++++++++++++-----------
> >  drivers/pci/pci.h    |  1 -
> >  2 files changed, 18 insertions(+), 12 deletions(-)
> > 
> > diff --git a/drivers/pci/devres.c b/drivers/pci/devres.c
> > index 936369face4b..0bafb67e1886 100644
> > --- a/drivers/pci/devres.c
> > +++ b/drivers/pci/devres.c
> > @@ -361,24 +361,34 @@ void __iomem
> > *devm_pci_remap_cfg_resource(struct device *dev,
> >  }
> >  EXPORT_SYMBOL(devm_pci_remap_cfg_resource);
> >  
> > +static void __pcim_clear_mwi(void *pdev_raw)
> > +{
> > +       struct pci_dev *pdev = pdev_raw;
> > +
> > +       pci_clear_mwi(pdev);
> > +}
> > +
> >  /**
> >   * pcim_set_mwi - a device-managed pci_set_mwi()
> > - * @dev: the PCI device for which MWI is enabled
> > + * @pdev: the PCI device for which MWI is enabled
> >   *
> >   * Managed pci_set_mwi().
> >   *
> >   * RETURNS: An appropriate -ERRNO error value on error, or zero
> > for success.
> >   */
> > -int pcim_set_mwi(struct pci_dev *dev)
> > +int pcim_set_mwi(struct pci_dev *pdev)
> >  {
> > -       struct pci_devres *dr;
> > +       int ret;
> >  
> > -       dr = find_pci_dr(dev);
> > -       if (!dr)
> > -               return -ENOMEM;
> > +       ret = devm_add_action(&pdev->dev, __pcim_clear_mwi, pdev);
> > +       if (ret != 0)
> > +               return ret;
> > +
> > +       ret = pci_set_mwi(pdev);
> > +       if (ret != 0)
> > +               devm_remove_action(&pdev->dev, __pcim_clear_mwi,
> > pdev);
> 
> I'm sorry if this is a stupid question but why this cannot use 
> devm_add_action_or_reset()?

For MWI that could be done.

This is basically just consistent with the new pcim_enable_device() in
patch No.11 where devm_add_action_or_reset() could collide with
pcim_pin_device().

We could squash usage of devm_add_action_or_reset() in here. I don't
care.

P.


> 
> > -       dr->mwi = 1;
> > -       return pci_set_mwi(dev);
> > +       return ret;
> >  }
> >  EXPORT_SYMBOL(pcim_set_mwi);
> 


  reply	other threads:[~2024-06-14  8:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  8:15 [PATCH v7 00/13] Make PCI's devres API more consistent Philipp Stanner
2024-06-05  8:15 ` [PATCH v7 01/13] PCI: Add and use devres helper for bit masks Philipp Stanner
2024-06-13 16:57   ` Ilpo Järvinen
2024-06-05  8:15 ` [PATCH v7 02/13] PCI: Add devres helpers for iomap table Philipp Stanner
2024-06-05  8:15 ` [PATCH v7 03/13] PCI: Reimplement plural devres functions Philipp Stanner
2024-06-13 16:54   ` Ilpo Järvinen
2024-06-13 18:45     ` Bjorn Helgaas
2024-06-05  8:15 ` [PATCH v7 04/13] PCI: Deprecate two surplus " Philipp Stanner
2024-06-05  8:15 ` [PATCH v7 05/13] PCI: Make devres region requests consistent Philipp Stanner
2024-06-05  8:15 ` [PATCH v7 06/13] PCI: Warn users about complicated devres nature Philipp Stanner
2024-06-05  8:15 ` [PATCH v7 07/13] PCI: Move dev-enabled status bit to struct pci_dev Philipp Stanner
2024-06-05 21:11   ` Bjorn Helgaas
2024-06-06  7:59     ` Philipp Stanner
2024-06-05  8:16 ` [PATCH v7 08/13] PCI: Move pinned " Philipp Stanner
2024-06-05  8:16 ` [PATCH v7 09/13] PCI: Give pcim_set_mwi() its own devres callback Philipp Stanner
2024-06-13 17:19   ` Ilpo Järvinen
2024-06-14  8:15     ` Philipp Stanner [this message]
2024-06-05  8:16 ` [PATCH v7 10/13] PCI: Give pci(m)_intx " Philipp Stanner
2024-06-13 17:23   ` Ilpo Järvinen
2024-06-13 18:47     ` Bjorn Helgaas
2024-06-05  8:16 ` [PATCH v7 11/13] PCI: Remove legacy pcim_release() Philipp Stanner
2024-06-05  8:16 ` [PATCH v7 12/13] PCI: Add pcim_iomap_range() Philipp Stanner
2024-06-05  8:16 ` [PATCH v7 13/13] drm/vboxvideo: fix mapping leaks Philipp Stanner
2024-06-07 19:40 ` [PATCH v7 00/13] Make PCI's devres API more consistent Bjorn Helgaas

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=105f167697e4421237884ebece1cf9a28293c762.camel@redhat.com \
    --to=pstanner@redhat.com \
    --cc=airlied@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dakr@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tzimmermann@suse.de \
    /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