>>> On 16.05.18 at 18:44, wrote:
> Jan Beulich wrote:
> On 15.05.18 at 16:11, wrote:
>>> --- a/arch/x86/include/asm/refcount.h
>>> +++ b/arch/x86/include/asm/refcount.h
>>> @@ -14,34 +14,43 @@
>>> * central refcount exception. The fixup address for the exception points
>>> * back to the re
Jan Beulich wrote:
On 15.05.18 at 16:11, wrote:
>> --- a/arch/x86/include/asm/refcount.h
>> +++ b/arch/x86/include/asm/refcount.h
>> @@ -14,34 +14,43 @@
>> * central refcount exception. The fixup address for the exception points
>> * back to the regular execution flow in .text.
>> */
>>
Kees Cook wrote:
> On Tue, May 15, 2018 at 7:11 AM, Nadav Amit wrote:
>> GCC considers the number of statements in inlined assembly blocks,
>> according to new-lines and semicolons, as an indication to the cost of
>> the block in time and space. This data is distorted by the kernel code,
>> whic
On Tue, May 15, 2018 at 7:11 AM, Nadav Amit wrote:
> GCC considers the number of statements in inlined assembly blocks,
> according to new-lines and semicolons, as an indication to the cost of
> the block in time and space. This data is distorted by the kernel code,
> which puts information in alt
>>> On 15.05.18 at 16:11, wrote:
> --- a/arch/x86/include/asm/refcount.h
> +++ b/arch/x86/include/asm/refcount.h
> @@ -14,34 +14,43 @@
> * central refcount exception. The fixup address for the exception points
> * back to the regular execution flow in .text.
> */
> -#define _REFCOUNT_EXCEPTI
5 matches
Mail list logo