On 03/06/2017 04:34 PM, Sergei Shtylyov wrote:
> On 3/6/2017 10:21 AM, jsun4 wrote:
>
If asid_cache(cpu) overflows, there may be two tasks with the same
asid. It is a risk that the two different tasks may have the same
address space.
A process will update its asid to new
On 3/6/2017 10:21 AM, jsun4 wrote:
If asid_cache(cpu) overflows, there may be two tasks with the same
asid. It is a risk that the two different tasks may have the same
address space.
A process will update its asid to newer version only when switch_mm()
is called and matches the following condit
Hello Sergei,
Thanks for your reply.
On 03/05/2017 05:38 PM, Sergei Shtylyov wrote:
> Hello!
>
> On 3/5/2017 6:24 AM, Jiwei Sun wrote:
>
>> If asid_cache(cpu) overflows, there may be two tasks with the same
>> asid. It is a risk that the two different tasks may have the same
>> address space.
>
Hello!
On 3/5/2017 6:24 AM, Jiwei Sun wrote:
If asid_cache(cpu) overflows, there may be two tasks with the same
asid. It is a risk that the two different tasks may have the same
address space.
A process will update its asid to newer version only when switch_mm()
is called and matches the follo
If asid_cache(cpu) overflows, there may be two tasks with the same
asid. It is a risk that the two different tasks may have the same
address space.
A process will update its asid to newer version only when switch_mm()
is called and matches the following condition:
if ((cpu_context(cpu, next) ^
5 matches
Mail list logo