[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211020064128.y2bjsbdmpojn7pjo@vireshk-i7>
Date: Wed, 20 Oct 2021 12:11:28 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Jie Deng <jie.deng@...el.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Wolfram Sang <wsa@...nel.org>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
virtualization@...ts.linux-foundation.org,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...s.com
Subject: Re: [PATCH 1/2] i2c: virtio: disable timeout handling
On 20-10-21, 14:35, Jie Deng wrote:
> Yes, but we need to know what's the best value to be configured for a
> specific "other side".
>
> I think the "other side" should be more aware of what value is reasonable to
> be used.
If we _really_ need that, then it would require an update to the
specification first.
I am not sure if the other side is the only party in play here. It
depends on the entire setup and not just the hardware device.
Specially with virtualisation things become really slow because of
context switches, etc. It may be better for the guest userspace to
decide on the value.
Since this is specially for virtualisation, the kernel may set the
value to few HZ by default, lets say 10 (Yeah its really high) :).
--
viresh
Powered by blists - more mailing lists