> -Original Message-
> From: Avi Kivity [mailto:a...@redhat.com]
> Sent: Thursday, March 24, 2011 3:51 PM
> To: Bhushan Bharat-R65777
> Cc: Alexander Graf; kvm@vger.kernel.org; bharatb.ya...@gmail.com
> Subject: Re: [PATCH] KVM:PPC Issue in exit timing clearance
>
On 03/24/2011 04:21 AM, Bhushan Bharat-R65777 wrote:
> Tracepoints are wonderful for debugging problems in the field, from my
> experience. Removing the special timing code (or rather, moving it to
> userspace) is just a bonus.
>
I think that we can always switch to tracepoints mechanism som
> -Original Message-
> From: Avi Kivity [mailto:a...@redhat.com]
> Sent: Wednesday, March 23, 2011 2:50 PM
> To: Alexander Graf
> Cc: Bhushan Bharat-R65777; kvm@vger.kernel.org; bharatb.ya...@gmail.com;
> Bhushan Bharat-R65777
> Subject: Re: [PATCH] KVM:PPC Issue in
On 03/22/2011 04:27 PM, Alexander Graf wrote:
What about using vcpu->requests to have the statistics cleared in
vcpu context?
What about dropping the whole thing and replacing it with tracepoints?
That should work. The question is if it's worth the effort. The
current code is there after
On 03/22/2011 01:43 PM, Avi Kivity wrote:
On 03/16/2011 06:37 PM, Bharat Bhushan wrote:
Following dump is observed on host when clearing the exit timing
counters
[root@p1021mds kvm]# echo -n 'c'> vm1200_vcpu0_timing
INFO: task echo:1276 blocked for more than 120 seconds.
"echo 0> /proc/sys/k
On 03/16/2011 06:37 PM, Bharat Bhushan wrote:
Following dump is observed on host when clearing the exit timing counters
[root@p1021mds kvm]# echo -n 'c'> vm1200_vcpu0_timing
INFO: task echo:1276 blocked for more than 120 seconds.
"echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this
Following dump is observed on host when clearing the exit timing counters
[root@p1021mds kvm]# echo -n 'c' > vm1200_vcpu0_timing
INFO: task echo:1276 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
echo D 0ff5bf94 0 1276
