On Thu, Oct 17, 2013 at 5:59 PM, David Ahern wrote:
> On 10/17/13 9:57 AM, Stephane Eranian wrote:
>>
>> On Thu, Oct 17, 2013 at 5:54 PM, David Ahern wrote:
>>>
>>> On 10/17/13 8:28 AM, Stephane Eranian wrote:
For now, we disable the extended MMAP record support (MMAP2).
On 10/17/13 9:57 AM, Stephane Eranian wrote:
On Thu, Oct 17, 2013 at 5:54 PM, David Ahern wrote:
On 10/17/13 8:28 AM, Stephane Eranian wrote:
For now, we disable the extended MMAP record support (MMAP2).
We have identified cases where it would not report the correct
mapping information, clon
On Thu, Oct 17, 2013 at 5:54 PM, David Ahern wrote:
> On 10/17/13 8:28 AM, Stephane Eranian wrote:
>>
>>
>> For now, we disable the extended MMAP record support (MMAP2).
>> We have identified cases where it would not report the correct
>> mapping information, clone(VM_CLONE) but with separate pids
On 10/17/13 8:28 AM, Stephane Eranian wrote:
For now, we disable the extended MMAP record support (MMAP2).
We have identified cases where it would not report the correct
mapping information, clone(VM_CLONE) but with separate pids.
We will revisit the support once we find a solution for this case
For now, we disable the extended MMAP record support (MMAP2).
We have identified cases where it would not report the correct
mapping information, clone(VM_CLONE) but with separate pids.
We will revisit the support once we find a solution for this case.
The patch changes the kernel to return EINVA
5 matches
Mail list logo