All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Guo Chao <yan@linux.vnet.ibm.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: Reset failed bridge resources in PCI realloc
Date: Wed, 3 Sep 2014 22:23:06 -0600	[thread overview]
Message-ID: <20140904042306.GG26073@google.com> (raw)
In-Reply-To: <CAE9FiQVkGcqFQ7e22Ekg7t-gWrQ9FdtadbVCASTGqU20FPE50g@mail.gmail.com>

On Wed, Jul 30, 2014 at 12:59:35PM -0700, Yinghai Lu wrote:
> On Wed, Jul 30, 2014 at 1:00 AM, Guo Chao <yan@linux.vnet.ibm.com> wrote:
> >         * However, in pbus_size_mem() we call calculate_memsize() to
> >           calculate the final size. calculate_memsize() never shrinks
> >           window, i.e. if old size is larger than newly sized result,
> >           old size will be honored. Unfortunately, the old size at this
> >           time is the sum of both normal BARs and SR-IOV BARs when doing
> >           realloc.
> >
> 
> that checking about old_size is added by:
> 
> | commit d65245c3297ac63abc51a976d92f45f2195d2854
> | Author: Yinghai Lu <yinghai@kernel.org>
> | Date:   Fri Jan 22 01:02:23 2010 -0800
> |
> |    PCI: don't shrink bridge resources
> |
> |    When clearing leaf bridge resources, trying to get a big enough one, we
> |    could shrink the bridge if there is no resource under it.  Confirm
> |    against the old resource side to make sure we're increasing the
> |    allocation.
> 
> so to make both cases ok, may need to check if there is any children devices
> on the dev->subordinate. Please check attached.

I think we should postpone this until we figure out how we're going to
manage resource start/end/flags, i.e., the IORESOURCE_UNSET and
IORESOURCE_DISABLED question.

> Thanks
> 
> Yinghai
> 
> 
> ---
>  drivers/pci/setup-bus.c |   10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> Index: linux-2.6/drivers/pci/setup-bus.c
> ===================================================================
> --- linux-2.6.orig/drivers/pci/setup-bus.c
> +++ linux-2.6/drivers/pci/setup-bus.c
> @@ -1622,8 +1622,11 @@ again:
>          res->start = fail_res->start;
>          res->end = fail_res->end;
>          res->flags = fail_res->flags;
> -        if (fail_res->dev->subordinate)
> +        if (fail_res->dev->subordinate) {
>              res->flags = 0;
> +            if (!list_empty(&fail_res->dev->subordinate->devices))
> +                res->start = res->end = 0;
> +        }
>      }
>      free_list(&fail_head);
> 
> @@ -1688,8 +1691,11 @@ again:
>          res->start = fail_res->start;
>          res->end = fail_res->end;
>          res->flags = fail_res->flags;
> -        if (fail_res->dev->subordinate)
> +        if (fail_res->dev->subordinate) {
>              res->flags = 0;
> +            if (!list_empty(&fail_res->dev->subordinate->devices))
> +                res->start = res->end = 0;
> +        }
>      }
>      free_list(&fail_head);

> ---
>  drivers/pci/setup-bus.c |   10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> Index: linux-2.6/drivers/pci/setup-bus.c
> ===================================================================
> --- linux-2.6.orig/drivers/pci/setup-bus.c
> +++ linux-2.6/drivers/pci/setup-bus.c
> @@ -1622,8 +1622,11 @@ again:
>  		res->start = fail_res->start;
>  		res->end = fail_res->end;
>  		res->flags = fail_res->flags;
> -		if (fail_res->dev->subordinate)
> +		if (fail_res->dev->subordinate) {
>  			res->flags = 0;
> +			if (!list_empty(&fail_res->dev->subordinate->devices))
> +				res->start = res->end = 0;
> +		}
>  	}
>  	free_list(&fail_head);
>  
> @@ -1688,8 +1691,11 @@ again:
>  		res->start = fail_res->start;
>  		res->end = fail_res->end;
>  		res->flags = fail_res->flags;
> -		if (fail_res->dev->subordinate)
> +		if (fail_res->dev->subordinate) {
>  			res->flags = 0;
> +			if (!list_empty(&fail_res->dev->subordinate->devices))
> +				res->start = res->end = 0;
> +		}
>  	}
>  	free_list(&fail_head);
>  


      parent reply	other threads:[~2014-09-04  4:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  8:00 [PATCH] PCI: Reset failed bridge resources in PCI realloc Guo Chao
2014-07-30 19:59 ` Yinghai Lu
2014-07-31  8:48   ` Guo Chao
2014-09-04  4:23   ` Bjorn Helgaas [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=20140904042306.GG26073@google.com \
    --to=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=yan@linux.vnet.ibm.com \
    --cc=yinghai@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.