On Wed, Feb 08, 2017 at 01:41:19PM +1100, Michael Ellerman wrote:
>Gavin Shan writes:
>
>> On Wed, Feb 08, 2017 at 10:39:55AM +1100, Andrew Donnellan wrote:
>>>On 08/02/17 10:21, Gavin Shan wrote:
On Tue, Feb 07, 2017 at 10:12:48PM +1100, Michael Ellerman wrote:
>Andrew Donnellan writes:
Gavin Shan writes:
> On Wed, Feb 08, 2017 at 10:39:55AM +1100, Andrew Donnellan wrote:
>>On 08/02/17 10:21, Gavin Shan wrote:
>>>On Tue, Feb 07, 2017 at 10:12:48PM +1100, Michael Ellerman wrote:
Andrew Donnellan writes:
>>>
>>>.../...
>>>
>The effect of this patch is to copy the memory r
On Wed, Feb 08, 2017 at 10:39:55AM +1100, Andrew Donnellan wrote:
>On 08/02/17 10:21, Gavin Shan wrote:
>>On Tue, Feb 07, 2017 at 10:12:48PM +1100, Michael Ellerman wrote:
>>>Andrew Donnellan writes:
>>
>>.../...
>>
The effect of this patch is to copy the memory resources from the *real*
P
On 08/02/17 10:21, Gavin Shan wrote:
On Tue, Feb 07, 2017 at 10:12:48PM +1100, Michael Ellerman wrote:
Andrew Donnellan writes:
.../...
The effect of this patch is to copy the memory resources from the *real*
PHB to the vPHB, as given through the device tree. It shouldn't have any
practical
On Tue, Feb 07, 2017 at 10:12:48PM +1100, Michael Ellerman wrote:
>Andrew Donnellan writes:
.../...
>> The effect of this patch is to copy the memory resources from the *real*
>> PHB to the vPHB, as given through the device tree. It shouldn't have any
>> practical effect other than squashing t
On Tue, Feb 07, 2017 at 07:14:33PM +1100, Andrew Donnellan wrote:
>On 31/01/17 14:43, Gavin Shan wrote:
>>The following error message was observed. It's complaining M32
>>memory window is missed on virtual PHB, which is a bit confusing.
>>The problem is the memory windows are never updated from its
Andrew Donnellan writes:
> On 31/01/17 14:43, Gavin Shan wrote:
>> The following error message was observed. It's complaining M32
>> memory window is missed on virtual PHB, which is a bit confusing.
>> The problem is the memory windows are never updated from its
>> device-tree node.
>>
>>PCI:
On 31/01/17 14:43, Gavin Shan wrote:
The following error message was observed. It's complaining M32
memory window is missed on virtual PHB, which is a bit confusing.
The problem is the memory windows are never updated from its
device-tree node.
PCI: Memory resource 0 not set for host bridge \
The following error message was observed. It's complaining M32
memory window is missed on virtual PHB, which is a bit confusing.
The problem is the memory windows are never updated from its
device-tree node.
PCI: Memory resource 0 not set for host bridge \
/pciex@3fffe4000/pci@0/device@0
