On 05.01.22 06:41, Alexander Motin wrote:
> Or may be it can be avoided somehow 20 years later?
I'd be super happy if this was removed. On my old laptop I had to disable this
code for many years because it lead to hangs in my (non-standard) setup at the
time:
On Wed, Jan 5, 2022 at 9:39 AM Warner Losh wrote:
>
>
> On Tue, Jan 4, 2022 at 10:42 PM Alexander Motin wrote:
>
>> Hi,
>>
>> As I see, one of the most active threaded callouts on idle VMware VM and
>> some hardware is atkbd_timeout(), called 10 times per second. Plus it
>> is also one of few
On Tue, Jan 4, 2022 at 10:42 PM Alexander Motin wrote:
> Hi,
>
> As I see, one of the most active threaded callouts on idle VMware VM and
> some hardware is atkbd_timeout(), called 10 times per second. Plus it
> is also one of few remaining non-MP-safe callouts. According to the
> comment it
Hi,
As I see, one of the most active threaded callouts on idle VMware VM and
some hardware is atkbd_timeout(), called 10 times per second. Plus it
is also one of few remaining non-MP-safe callouts. According to the
comment it seems to be only a workaround for some lost interrupts. That
makes
