* Sanidhya Kashyap (sanidhya.ii...@gmail.com) wrote:
> >
> > 1) Do you have some examples of output?
> >Can you see hot areas in the kernel or something else?
> >
>
> I looked at it sometimes back. I will try to provide some images (as
> suggested by you earlier) to see any consistently used
>
> 1) Do you have some examples of output?
>Can you see hot areas in the kernel or something else?
>
I looked at it sometimes back. I will try to provide some images (as
suggested by you earlier) to see any consistently used areas.
> 2) 'frequency' is probably the wrong name for the paramet
On 07/18/2014 04:56 AM, Dr. David Alan Gilbert wrote:
> * Sanidhya Kashyap (sanidhya.ii...@gmail.com) wrote:
>> Hi,
>>
>> The following patches introduce the support of the dirty bitmap logging and
>> dumping to a specified file. This patch addresses the previous issues raised
>> by David and Juan.
On 07/17/2014 05:21 AM, Sanidhya Kashyap wrote:
> Hi,
>
> The following patches introduce the support of the dirty bitmap logging and
> dumping to a specified file. This patch addresses the previous issues raised
> by David and Juan. Since, I have not received any comments on the runstates,
> I'll
* Sanidhya Kashyap (sanidhya.ii...@gmail.com) wrote:
> Hi,
>
> The following patches introduce the support of the dirty bitmap logging and
> dumping to a specified file. This patch addresses the previous issues raised
> by David and Juan. Since, I have not received any comments on the runstates,
>
Hi,
The following patches introduce the support of the dirty bitmap logging and
dumping to a specified file. This patch addresses the previous issues raised
by David and Juan. Since, I have not received any comments on the runstates,
I'll keep them in the patch series.
v3 --> v4
* Added new qmp i
