Hi,
On 01/18/2018 04:14 AM, Sudeep Holla wrote:
On 17/01/18 18:51, Jeremy Linton wrote:
Hi,
On 01/17/2018 12:20 PM, Sudeep Holla wrote:
On 16/01/18 21:07, Jeremy Linton wrote:
Hi,
On 01/15/2018 06:33 AM, Sudeep Holla wrote:
On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
On Wed, 17 Jan 2018 10:08:27 PST (-0800), sudeep.ho...@arm.com wrote:
(Sorry, somehow I missed this email until I saw Jeremy's reply today)
On 15/01/18 16:07, Palmer Dabbelt wrote:
On Mon, 15 Jan 2018 04:33:38 PST (-0800), sudeep.ho...@arm.com wrote:
On Fri, Jan 12, 2018 at 06:59:10PM -0600, J
On 17/01/18 18:51, Jeremy Linton wrote:
> Hi,
>
> On 01/17/2018 12:20 PM, Sudeep Holla wrote:
>>
>>
>> On 16/01/18 21:07, Jeremy Linton wrote:
>>> Hi,
>>>
>>> On 01/15/2018 06:33 AM, Sudeep Holla wrote:
On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
> The original intent
Hi,
On 01/17/2018 12:20 PM, Sudeep Holla wrote:
On 16/01/18 21:07, Jeremy Linton wrote:
Hi,
On 01/15/2018 06:33 AM, Sudeep Holla wrote:
On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
The original intent in cacheinfo was that an architecture
specific populate_cache_leaves()
On 16/01/18 21:07, Jeremy Linton wrote:
> Hi,
>
> On 01/15/2018 06:33 AM, Sudeep Holla wrote:
>> On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
>>> The original intent in cacheinfo was that an architecture
>>> specific populate_cache_leaves() would probe the hardware
>>> and then
(Sorry, somehow I missed this email until I saw Jeremy's reply today)
On 15/01/18 16:07, Palmer Dabbelt wrote:
> On Mon, 15 Jan 2018 04:33:38 PST (-0800), sudeep.ho...@arm.com wrote:
>> On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
>>> The original intent in cacheinfo was that an
Hi,
On 01/15/2018 10:07 AM, Palmer Dabbelt wrote:
On Mon, 15 Jan 2018 04:33:38 PST (-0800), sudeep.ho...@arm.com wrote:
On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
The original intent in cacheinfo was that an architecture
specific populate_cache_leaves() would probe the hard
Hi,
On 01/15/2018 06:33 AM, Sudeep Holla wrote:
On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
The original intent in cacheinfo was that an architecture
specific populate_cache_leaves() would probe the hardware
and then cache_shared_cpu_map_setup() and
cache_override_properties(
On Mon, 15 Jan 2018 04:33:38 PST (-0800), sudeep.ho...@arm.com wrote:
On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
The original intent in cacheinfo was that an architecture
specific populate_cache_leaves() would probe the hardware
and then cache_shared_cpu_map_setup() and
cache
On Fri, Jan 12, 2018 at 06:59:10PM -0600, Jeremy Linton wrote:
> The original intent in cacheinfo was that an architecture
> specific populate_cache_leaves() would probe the hardware
> and then cache_shared_cpu_map_setup() and
> cache_override_properties() would provide firmware help to
> extend/ex
The original intent in cacheinfo was that an architecture
specific populate_cache_leaves() would probe the hardware
and then cache_shared_cpu_map_setup() and
cache_override_properties() would provide firmware help to
extend/expand upon what was probed. Arm64 was really
the only architecture that wa
11 matches
Mail list logo