All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Tony Luck <tony.luck@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lucas Stach <l.stach@pengutronix.de>,
	Richard Zhu <Richard.Zhu@freescale.com>,
	Marek Kordik <kordikmarek@gmail.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Andreas Hartmann <andihartmann@freenet.de>,
	Alexey Voronkov <zermond@gmail.com>,
	David Airlie <airlied@linux.ie>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [GIT PULL] PCI fixes for v3.19
Date: Fri, 30 Jan 2015 16:12:30 -0600	[thread overview]
Message-ID: <CAErSpo5J5aXVLXJ-Xkpr8JSF6U=itX_6+SwnD3f8EAEwNF745w@mail.gmail.com> (raw)
In-Reply-To: <CAE9FiQWM0teGrWjn2xTfbLW1hqYG0Xau8poSxJCWfjfaQhdt5Q@mail.gmail.com>

On Fri, Jan 30, 2015 at 3:49 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> On Fri, Jan 30, 2015 at 8:56 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>> On Tue, Jan 27, 2015 at 6:54 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>>> On Tue, Jan 27, 2015 at 3:24 PM, Tony Luck <tony.luck@gmail.com> wrote:
>>>> On Mon, Jan 26, 2015 at 7:43 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>>>>> Can you please get boot bog with "debug ignore_logleve"?
>>>>>
>>>>> we should get print out from
>>>>>
>>>>> +               dev_printk(KERN_DEBUG, &dev->dev, "%pR clipped to %pR\n",
>>>>> +                                &orig_res, res);
>>>>
>>>> Attached ... but I don't see any "clipped" messages
>>>
>>> Good. so the system should just work as before but have annoying warnings.
>>>
>>> Do we need to put the paper back to hide the warning?
>>
>> Ping, I'm not sure this is resolved.
>>
>> Tony, does the system work as it did before?  Is the only problem that
>> now we have more warnings than we did before?
>>
>> Yinghai, I sort of feel like I'm being left to sweep up behind your
>> changes here.  I *could* analyze this and figure out what's going on
>> and fix it, but I don't have time to do that for everybody, and I
>> consider that more your job.
>
> Sorry to hear that.
>
> I did respond the email, and gave the the explanation.
>
>>
>> If we start with the same _CRS config and same device config, ideally
>> PCI enumeration would produce the same messages, same warnings, and
>> same resource assignments no matter what arch we feed them to, because
>> enumeration is not really arch-specific.  So if ia64 does something
>> different here, I think something needs to be fixed.
>
> ia64 was doing different,
> 1. It check if the range is valid with bus resources. and only call
> pci_claim_resource for that path.
> 2. and it does not reset invalid resource to allocate new one.
>
> This patch change to call pci_claim_resource directly, so we have warning now.
> but just warning as we did not reset the resource.

OK, I guess I just didn't understand what you were saying.

So I'll consider this resolved unless I hear somebody say otherwise.

Bjorn

  reply	other threads:[~2015-01-30 22:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 20:31 [GIT PULL] PCI fixes for v3.19 Bjorn Helgaas
2015-01-26 19:58 ` Tony Luck
2015-01-26 21:02   ` Bjorn Helgaas
2015-01-26 21:24     ` Tony Luck
2015-01-26 23:53       ` Bjorn Helgaas
2015-01-27  3:55         ` Yinghai Lu
2015-01-27 14:03           ` Bjorn Helgaas
2015-01-27 23:27             ` Tony Luck
2015-01-27  3:43       ` Yinghai Lu
2015-01-27 23:24         ` Tony Luck
2015-01-28  0:54           ` Yinghai Lu
2015-01-30 16:56             ` Bjorn Helgaas
2015-01-30 18:01               ` Tony Luck
2015-01-30 18:18                 ` Bjorn Helgaas
2015-01-30 21:49               ` Yinghai Lu
2015-01-30 22:12                 ` Bjorn Helgaas [this message]
     [not found] <20150204191831.GA13785@google.com>
2015-02-11 16:48 ` 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='CAErSpo5J5aXVLXJ-Xkpr8JSF6U=itX_6+SwnD3f8EAEwNF745w@mail.gmail.com' \
    --to=bhelgaas@google.com \
    --cc=Richard.Zhu@freescale.com \
    --cc=airlied@linux.ie \
    --cc=alex.williamson@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=andihartmann@freenet.de \
    --cc=kordikmarek@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tony.luck@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@kernel.org \
    --cc=zermond@gmail.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 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.