On Thu, Sep 05, 2024 at 08:00:54PM +0200, Denis V. Lunev wrote:
> On 9/5/24 19:52, Peter Xu wrote:
> > On Thu, Sep 05, 2024 at 06:51:46PM +0200, Denis V. Lunev via wrote:
> > > Right now this tracepoint is just saying that the guest has been
> > > throttled, but this is not that good for debugging
On 9/5/24 19:52, Peter Xu wrote:
On Thu, Sep 05, 2024 at 06:51:46PM +0200, Denis V. Lunev via wrote:
Right now this tracepoint is just saying that the guest has been
throttled, but this is not that good for debugging purposes. We should
also know how much the guest is throttled in order to under
On Thu, Sep 05, 2024 at 06:51:46PM +0200, Denis V. Lunev via wrote:
> Right now this tracepoint is just saying that the guest has been
> throttled, but this is not that good for debugging purposes. We should
> also know how much the guest is throttled in order to understand
> consequences for the g
Right now this tracepoint is just saying that the guest has been
throttled, but this is not that good for debugging purposes. We should
also know how much the guest is throttled in order to understand
consequences for the guest behaviour.
The patch moves the tracepoint from migration_trigger_throt
