linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH v3] PCI: Only enable IO window if supported
Date: Thu, 06 Aug 2015 09:18:23 -0700	[thread overview]
Message-ID: <55C388CF.4090501@roeck-us.net> (raw)
In-Reply-To: <CAE9FiQVDwX_-bX9sH2qv3thkKzOosFR3WvkUYWM=TsU-4oOSzA@mail.gmail.com>

On 08/06/2015 08:58 AM, Yinghai Lu wrote:
> On Wed, Aug 5, 2015 at 9:50 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> If I understand you correctly, we might need to change the code
>> in pci_read_bridge_io() as follows.
>>
>> From
>>
>>          if (!(child->bus_flags & PCI_BUS_FLAGS_SUPPORTS_IO))
>>                  return;
>>
>> to something like
>>
>>          if (!(child->bus_flags & PCI_BUS_FLAGS_SUPPORTS_IO)) {
>>                  if (dev->transparent)
>>                          return;
>>                  child->bus_flags |= PCI_BUS_FLAGS_SUPPORTS_IO;
>>          }
>>
> Then how about: the root bus really does not support IO PORT resource.
>

Ok, I admit that I am lost. Earlier it seemed that you were concerned about
this case, where no io window is available or a bus doesn't support io,
but a non-transparent child does. Now you seem to say that the non-transparent
child would not be able to support IO either.

For my education, can you list the possible options, and how you suggest
to solve them ? I can see the following situations.

- root supports IO, but has no io window assigned
- root does not support IO and has or has not an IO window assigned
- a bridge does not support IO

For the transparent case, each of those should result in all children
not even trying to assign an IO window, which is what we want,
and what my patc set tries to do.

How should those cases be handled for non-transparent bridges ?

Thanks,
Guenter


  reply	other threads:[~2015-08-06 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  2:15 [PATCH v3] PCI: Only enable IO window if supported Guenter Roeck
2015-08-06  1:14 ` Yinghai Lu
2015-08-06  1:38   ` Yinghai Lu
2015-08-06  2:22     ` Guenter Roeck
2015-08-06  4:25       ` Yinghai Lu
2015-08-06  4:50         ` Guenter Roeck
2015-08-06 15:58           ` Yinghai Lu
2015-08-06 16:18             ` Guenter Roeck [this message]
2015-08-06 23:32               ` Yinghai Lu
2015-08-07  0:32                 ` Guenter Roeck
2015-08-07  1:12                   ` Yinghai Lu
2015-08-06  1:44   ` Guenter Roeck

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=55C388CF.4090501@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).