Hi:
On Mon, Dec 16, 2013 at 04:36:32PM -0800, Yinghai Lu wrote:
> On Mon, Dec 16, 2013 at 1:36 PM, Yinghai Lu wrote:
> > On Mon, Dec 16, 2013 at 10:13 AM, Yinghai Lu wrote:
> >>>
> >>> 64-bit non-prefetchable BARs are missed from caculation in the scheme,
> >>> causing assign failed eventually.
>
On Mon, Dec 16, 2013 at 1:36 PM, Yinghai Lu wrote:
> On Mon, Dec 16, 2013 at 10:13 AM, Yinghai Lu wrote:
>>>
>>> 64-bit non-prefetchable BARs are missed from caculation in the scheme,
>>> causing assign failed eventually.
>>>
>>> Will you figure out a better way to cover them or just add a 'type
On Mon, Dec 16, 2013 at 10:13 AM, Yinghai Lu wrote:
> On Mon, Dec 16, 2013 at 12:23 AM, Guo Chao wrote:
>> On Mon, Dec 09, 2013 at 10:54:43PM -0800, Yinghai Lu wrote:
>>> When one of children resources does not support MEM_64, MEM_64 for
>>> bridge get reset, so pull down whole pref resource on t
On Mon, Dec 16, 2013 at 12:23 AM, Guo Chao wrote:
> On Mon, Dec 09, 2013 at 10:54:43PM -0800, Yinghai Lu wrote:
>> When one of children resources does not support MEM_64, MEM_64 for
>> bridge get reset, so pull down whole pref resource on the bridge under 4G.
>>
>> If the bridge support pref mem 6
On Mon, Dec 09, 2013 at 10:54:43PM -0800, Yinghai Lu wrote:
> When one of children resources does not support MEM_64, MEM_64 for
> bridge get reset, so pull down whole pref resource on the bridge under 4G.
>
> If the bridge support pref mem 64, will only allocate that with pref mem64 to
> children
When one of children resources does not support MEM_64, MEM_64 for
bridge get reset, so pull down whole pref resource on the bridge under 4G.
If the bridge support pref mem 64, will only allocate that with pref mem64 to
children that support it.
For children resources if they only support pref mem
6 matches
Mail list logo
