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,
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
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
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
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
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
On Thu, Oct 17, 2013 at 5:54 PM, David Ahern dsah...@gmail.com 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
On 10/17/13 9:57 AM, Stephane Eranian wrote:
On Thu, Oct 17, 2013 at 5:54 PM, David Ahern dsah...@gmail.com 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
On Thu, Oct 17, 2013 at 5:59 PM, David Ahern dsah...@gmail.com wrote:
On 10/17/13 9:57 AM, Stephane Eranian wrote:
On Thu, Oct 17, 2013 at 5:54 PM, David Ahern dsah...@gmail.com wrote:
On 10/17/13 8:28 AM, Stephane Eranian wrote:
For now, we disable the extended MMAP record support
10 matches
Mail list logo