- On Nov 10, 2017, at 5:32 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Nov 10, 2017, at 5:20 PM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>>
>>> On Fri, Nov 10, 2017
- On Nov 10, 2017, at 5:32 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Nov 10, 2017, at 5:20 PM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>>
>>> On Fri, Nov 10, 2017
- On Nov 10, 2017, at 5:36 PM, Andy Lutomirski l...@amacapital.net wrote:
>> On Nov 10, 2017, at 2:20 PM, Mathieu Desnoyers
>>
>> wrote:
>>
>> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>>
>>> On Fri, Nov 10, 2017 at 1:37 PM,
- On Nov 10, 2017, at 5:36 PM, Andy Lutomirski l...@amacapital.net wrote:
>> On Nov 10, 2017, at 2:20 PM, Mathieu Desnoyers
>>
>> wrote:
>>
>> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>>
>>> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
>>> wrote:
> On Nov 10, 2017, at 2:20 PM, Mathieu Desnoyers
> wrote:
>
> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>
>> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
>> wrote:
>>> Introduce an
> On Nov 10, 2017, at 2:20 PM, Mathieu Desnoyers
> wrote:
>
> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>
>> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
>> wrote:
>>> Introduce an architecture function that ensures the current CPU
>>> issues a core
- On Nov 10, 2017, at 5:20 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>
>> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
>> wrote:
>>> Introduce an architecture
- On Nov 10, 2017, at 5:20 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>
>> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
>> wrote:
>>> Introduce an architecture function that ensures the
- On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
> wrote:
>> Introduce an architecture function that ensures the current CPU
>> issues a core serializing instruction before returning to
- On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
> wrote:
>> Introduce an architecture function that ensures the current CPU
>> issues a core serializing instruction before returning to usermode.
>>
>> This is needed
On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
wrote:
> Introduce an architecture function that ensures the current CPU
> issues a core serializing instruction before returning to usermode.
>
> This is needed to fix an existing core serialization bug on
>
On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
wrote:
> Introduce an architecture function that ensures the current CPU
> issues a core serializing instruction before returning to usermode.
>
> This is needed to fix an existing core serialization bug on
> thread migration, and also needed by
Introduce an architecture function that ensures the current CPU
issues a core serializing instruction before returning to usermode.
This is needed to fix an existing core serialization bug on
thread migration, and also needed by the membarrier "sync_core" command.
Architectures defining the
Introduce an architecture function that ensures the current CPU
issues a core serializing instruction before returning to usermode.
This is needed to fix an existing core serialization bug on
thread migration, and also needed by the membarrier "sync_core" command.
Architectures defining the
14 matches
Mail list logo