public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: "Cheng, Collins" <Collins.Cheng@amd.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Zytaruk, Kelly" <Kelly.Zytaruk@amd.com>,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform
Date: Wed, 24 May 2017 08:57:12 -0600	[thread overview]
Message-ID: <20170524085712.4947e575@w520.home> (raw)
In-Reply-To: <BN6PR12MB124978AC5216B07455A0CD06ECFE0@BN6PR12MB1249.namprd12.prod.outlook.com>

On Wed, 24 May 2017 08:57:53 +0000
"Cheng, Collins" <Collins.Cheng@amd.com> wrote:

> Hi Alex,
> 
> How do you know "particular this system offers no 64-bit MMIO", from dmesg log?

>From this:

> [    0.891319] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
> [    0.891321] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
> [    0.891322] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
> [    0.891323] pci_bus 0000:00: root bus resource [mem 0x88800000-0xdfffffff window]
> [    0.891324] pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window]
> [    0.891325] pci_bus 0000:00: root bus resource [bus 00-fe]

There are only 32-bit ranges listed.  Thanks,

Alex

  reply	other threads:[~2017-05-24 14:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12  2:50 [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform Cheng, Collins
2017-05-12  3:20 ` Alex Williamson
2017-05-12  3:42   ` Cheng, Collins
2017-05-12  4:01     ` Alex Williamson
2017-05-12  4:51       ` Cheng, Collins
2017-05-12 14:43         ` Alex Williamson
2017-05-15  8:19           ` Cheng, Collins
2017-05-15 17:53             ` Alex Williamson
2017-05-16  8:45               ` Cheng, Collins
2017-05-19 15:43               ` Alexander Duyck
2017-05-20  4:53                 ` Cheng, Collins
2017-05-20 10:27                   ` Zytaruk, Kelly
2017-05-20 10:37                     ` Cheng, Collins
2017-05-20 14:29                       ` Zytaruk, Kelly
2017-05-21  0:03                         ` Alexander Duyck
2017-05-22 15:44                 ` Alex Williamson
2017-05-23  3:41                   ` Cheng, Collins
2017-05-23 16:02                     ` Alexander Duyck
2017-05-23 18:20                     ` Alex Williamson
2017-05-24  8:56                       ` Cheng, Collins
2017-05-24  8:57                       ` Cheng, Collins
2017-05-24 14:57                         ` Alex Williamson [this message]
2017-05-26  1:52                       ` Cheng, Collins
2017-05-26 15:52                         ` Alex Williamson
2017-05-27  8:17                           ` Cheng, Collins
2017-05-12  3:44   ` Zytaruk, Kelly
2017-05-23 12:15 ` Deucher, Alexander

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=20170524085712.4947e575@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Collins.Cheng@amd.com \
    --cc=Kelly.Zytaruk@amd.com \
    --cc=alexander.duyck@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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