Zhaoming Luo, le sam. 03 mai 2025 08:30:10 +0800, a ecrit:
> On Sat, May 03, 2025 at 02:21:31AM +0200, Samuel Thibault wrote:
> > Zhaoming Luo, le sam. 03 mai 2025 08:17:52 +0800, a ecrit:
> > > On Sat, May 03, 2025 at 02:10:12AM +0200, Samuel Thibault wrote:
> > > > Zhaoming Luo, le ven. 02 mai 20
On Sat, May 03, 2025 at 02:21:31AM +0200, Samuel Thibault wrote:
> Zhaoming Luo, le sam. 03 mai 2025 08:17:52 +0800, a ecrit:
> > On Sat, May 03, 2025 at 02:10:12AM +0200, Samuel Thibault wrote:
> > > Zhaoming Luo, le ven. 02 mai 2025 22:45:44 +0800, a ecrit:
> > > > Get the time with higher resolu
Zhaoming Luo, le sam. 03 mai 2025 08:17:52 +0800, a ecrit:
> On Sat, May 03, 2025 at 02:10:12AM +0200, Samuel Thibault wrote:
> > Zhaoming Luo, le ven. 02 mai 2025 22:45:44 +0800, a ecrit:
> > > Get the time with higher resolution from kernel using host_get_time64()
> > > when possible.
> >
> > It
On Sat, May 03, 2025 at 02:10:12AM +0200, Samuel Thibault wrote:
> Zhaoming Luo, le ven. 02 mai 2025 22:45:44 +0800, a ecrit:
> > Get the time with higher resolution from kernel using host_get_time64()
> > when possible.
>
> It seems there's a misunderstanding. I explained that the mapped time
> d
Zhaoming Luo, le ven. 02 mai 2025 22:45:44 +0800, a ecrit:
> Get the time with higher resolution from kernel using host_get_time64()
> when possible.
It seems there's a misunderstanding. I explained that the mapped time
does have 64bit precision fields, that's what I mean we want to use,
rather th
Get the time with higher resolution from kernel using host_get_time64()
when possible.
---
libdiskfs/node-times.c | 25 +
1 file changed, 17 insertions(+), 8 deletions(-)
diff --git a/libdiskfs/node-times.c b/libdiskfs/node-times.c
index 60eabc0f..203232da 100644
--- a/li
