[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202405091030597804KUqLDPPj2FpTIBrZZ5Eo@zte.com.cn>
Date: Thu, 9 May 2024 10:30:59 +0800 (CST)
From: <cheng.lin130@....com.cn>
To: <seanjc@...gle.com>
Cc: <pbonzini@...hat.com>, <kvm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <jiang.yong5@....com.cn>,
<wang.liang82@....com.cn>, <jiang.xuexin@....com.cn>
Subject: Re: [PATCH] KVM: introduce vm's max_halt_poll_ns to debugfs
> From: seanjc <seanjc@...gle.com>
> > From: Cheng Lin <cheng.lin130@....com.cn>
> >
> > Introduce vm's max_halt_poll_ns and override_halt_poll_ns to
> > debugfs. Provide a way to check and modify them.
> Why?
If a vm's max_halt_poll_ns has been set using KVM_CAP_HALT_POLL,
the module parameter kvm.halt_poll.ns will no longer indicate the maximum
halt pooling interval for that vm. After introducing these two attributes into
debugfs, it can be used to check whether the individual configuration of the
vm is enabled and the working value.
This patch provides a way to check and modify them through the debugfs.
Powered by blists - more mailing lists