[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] vTPM: Fix Atmel timeout bug.
Of course we can use max, but I thought that it might be useful to have a prink to inform the user that the timeout was adjusted. InÂinit_tpm_tis the default timeouts are set using:/* Set default timeouts */
tpm->timeout_a = MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL
tpm->timeout_b = MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL
tpm->timeout_c = MILLISECS(TIS_SHORT_TIMEOUT);
tpm->timeout_d = MILLISECS(TIS_SHORT_TIMEOUT); But in kernel fix they are set as 750*1000 instead ofÂ750*1000000UL : https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n381 So if we want to integrate kernel changes I think we should use MICROSECS(TIS_SHORT_TIMEOUT) which is 750000 Also in kernel the default timeouts are initialized using msecs_to_jiffies which is different from MILLISECS macro.:Âhttps://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n548 Is there a certain reason for not usingÂmsecs_to_jiffiesÂ? On Thu, Oct 30, 2014 at 2:58 PM, Andrew Cooper <andrew.cooper3@xxxxxxxxxx> wrote:
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |