public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marek Kordík" <kordikmarek@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>,
	Wei Yang <weiyang@linux.vnet.ibm.com>,
	Alexey Voronkov <zermond@gmail.com>,
	Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: Clear bridge MEM_64 flag if one child does not support it
Date: Tue, 09 Dec 2014 19:07:01 +0100	[thread overview]
Message-ID: <54873A45.3050009@gmail.com> (raw)
In-Reply-To: <CAE9FiQWz=vdR=QSkoEs5XjUxg_y4vJgnChQAc1-U_9xzfQpknQ@mail.gmail.com>

On 12/09/2014 08:20 AM, Yinghai Lu wrote:
> On Mon, Dec 8, 2014 at 6:26 PM, Wei Yang <weiyang@linux.vnet.ibm.com> wrote:
>> On Tue, Dec 09, 2014 at 11:11:19AM +1100, Gavin Shan wrote:
>>>
>>> I'm going to give it a spin and Richard, could you please apply Yinghai's
>>> patch to see if your SRIOV code can work properly?
>>>
>>
>> I did a quick test on my machine. This patch doesn't affect the MMIO
>> allocation on out platform, so SRIOV works fine.
>>
>> I will spend more time to read the patch to get more understanding about the
>> problem.
>
> Hi Marek,
>
> Can you boot following branch with "debug ignore_loglevel pci=realloc"
> on your setup?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> for-pci-allocate-fit-3.18
>
> it has
> 8f74af9: PCI, x86: Allocate mmio near end of free range
> 1ff91c1: PCI: Don't allocate small resource in big free space.
> 108b43b: resources: Add allocate_resource_fit()
> b6a22f0: resources: Make find_resource could return just fit resource
> cf50e16: resources: Split out __allocate_resource()
>
> on top the v3.18, and it will allocate resource in fit way.
>
> Thanks
>
> Yinghai
>
Hi Yinghai,

I have built and booted your branch and it works well. Do you want me to 
attach some logs?
(I am new here and I have read http://www.tux.org/lkml/ and I don't want 
to break some rules for attachment size)

Marek

  parent reply	other threads:[~2014-12-09 18:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 21:52 [PATCH] PCI: Clear bridge MEM_64 flag if one child does not support it Yinghai Lu
2014-12-08 22:56 ` Benjamin Herrenschmidt
2014-12-08 23:00   ` Benjamin Herrenschmidt
2014-12-09  0:09     ` Yinghai Lu
2014-12-09 21:39       ` Yinghai Lu
2014-12-08 23:59   ` Yinghai Lu
2014-12-09  0:11     ` Gavin Shan
2014-12-09  2:26       ` Wei Yang
2014-12-09  7:20         ` Yinghai Lu
2014-12-09  7:56           ` Wei Yang
2014-12-09 18:21             ` Bjorn Helgaas
2014-12-10  9:42               ` Wei Yang
2014-12-09 19:49             ` Yinghai Lu
2014-12-09 18:07           ` Marek Kordík [this message]
2014-12-09 18:22             ` Bjorn Helgaas
2014-12-09 19:42               ` Yinghai Lu
2014-12-09 22:15                 ` Marek Kordík
2014-12-09 23:16                   ` Yinghai Lu
2014-12-09  1:08     ` Gavin Shan
2014-12-09  1:38       ` Yinghai Lu

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=54873A45.3050009@gmail.com \
    --to=kordikmarek@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=weiyang@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox