mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: "Ian Campbell" <ian.campbell@citrix.com>
Cc: <Stefano.Stabellini@eu.citrix.com>, <jeremy@goop.org>,
	<xen-devel@lists.xensource.com>, <konrad.wilk@oracle.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen: use PCI interfaces to request IO and MEM resources on platform device.
Date: Tue, 11 Jan 2011 12:48:21 +0000	[thread overview]
Message-ID: <4D2C5FA5020000780002BB21@vpn.id2.novell.com> (raw)
In-Reply-To: <1294746628-20396-1-git-send-email-ian.campbell@citrix.com>

>>> On 11.01.11 at 12:50, Ian Campbell <ian.campbell@citrix.com> wrote:
> This is the correct interface to use and something has broken the use
> of the previous incorrect interface (which fails because the request
> conflicts with the resources assigned for the PCI device itself
> instead of nesting like the PCI interfaces do).

While I agree that using the PCI interface is preferable, I can't see
how this can make a functional difference: __pci_request_region()
calls request_region() for the port resource and
__request_mem_region() for the mmio one exactly like what was
open coded before (request_mem_region() being equivalent to
__request_mem_region(..., 0), so I don't follow how this fixes
anything but half of the potentially incorrect use of "long" for
mmio_addr.

I'm mainly asking because if it really addresses some problem,
then unmodified_drivers/linux-2.6/platform-pci/platform-pci.c
in -unstable should probably get updated too.

Jan

> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Cc: stable@kernel.org # 2.6.37 only
> ---
>  drivers/xen/platform-pci.c |   21 +++++++--------------
>  1 files changed, 7 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/xen/platform-pci.c b/drivers/xen/platform-pci.c
> index c01b5dd..afbe041 100644
> --- a/drivers/xen/platform-pci.c
> +++ b/drivers/xen/platform-pci.c
> @@ -105,7 +105,7 @@ static int __devinit platform_pci_init(struct pci_dev 
> *pdev,
>  				       const struct pci_device_id *ent)
>  {
>  	int i, ret;
> -	long ioaddr, iolen;
> +	long ioaddr;
>  	long mmio_addr, mmio_len;
>  	unsigned int max_nr_gframes;
>  
> @@ -114,7 +114,6 @@ static int __devinit platform_pci_init(struct pci_dev 
> *pdev,
>  		return i;
>  
>  	ioaddr = pci_resource_start(pdev, 0);
> -	iolen = pci_resource_len(pdev, 0);
>  
>  	mmio_addr = pci_resource_start(pdev, 1);
>  	mmio_len = pci_resource_len(pdev, 1);
> @@ -125,19 +124,13 @@ static int __devinit platform_pci_init(struct pci_dev 
> *pdev,
>  		goto pci_out;
>  	}
>  
> -	if (request_mem_region(mmio_addr, mmio_len, DRV_NAME) == NULL) {
> -		dev_err(&pdev->dev, "MEM I/O resource 0x%lx @ 0x%lx busy\n",
> -		       mmio_addr, mmio_len);
> -		ret = -EBUSY;
> +	ret = pci_request_region(pdev, 1, DRV_NAME);
> +	if (ret < 0)
>  		goto pci_out;
> -	}
>  
> -	if (request_region(ioaddr, iolen, DRV_NAME) == NULL) {
> -		dev_err(&pdev->dev, "I/O resource 0x%lx @ 0x%lx busy\n",
> -		       iolen, ioaddr);
> -		ret = -EBUSY;
> +	ret = pci_request_region(pdev, 0, DRV_NAME);
> +	if (ret < 0)
>  		goto mem_out;
> -	}
>  
>  	platform_mmio = mmio_addr;
>  	platform_mmiolen = mmio_len;
> @@ -169,9 +162,9 @@ static int __devinit platform_pci_init(struct pci_dev 
> *pdev,
>  	return 0;
>  
>  out:
> -	release_region(ioaddr, iolen);
> +	pci_release_region(pdev, 0);
>  mem_out:
> -	release_mem_region(mmio_addr, mmio_len);
> +	pci_release_region(pdev, 1);
>  pci_out:
>  	pci_disable_device(pdev);
>  	return ret;





  reply	other threads:[~2011-01-11 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 11:50 Ian Campbell
2011-01-11 12:48 ` Jan Beulich [this message]
2011-01-11 13:01   ` [Xen-devel] " Ian Campbell
2011-01-11 14:10     ` Jan Beulich
2011-01-11 14:18       ` Ian Campbell
2011-01-11 14:27         ` Jan Beulich
2011-01-11 14:33           ` Ian Campbell

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=4D2C5FA5020000780002BB21@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.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

all inboxes | Powered by JetHome®