Displaying 20 results from an estimated 1000 matches similar to: "monotonic clock"
2015 Mar 05
1
Roadmap to 2.7.3
For reference: https://github.com/networkupstools/nut/issues/10
On Mar 5, 2015, at 1:09 AM, Baruch Even <baruch at ev-en.org> wrote:
> Hi,
>
> There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some
2014 Nov 13
1
Static build failure
Hi dovecot list,
Static build of dovecot fails because src/lib/module-dir.c refers to
MODULE_SUFFIX that is undefined when building statically. This least to the
following build failure:
module-dir.c: In function 'module_file_get_name':
module-dir.c:624:20: error: 'MODULE_SUFFIX' undeclared (first use in this function)
p = strstr(fname, MODULE_SUFFIX);
^
2012 Sep 27
3
NUT Bugs #313634 & #313714: unification & encapsulation of timer proposition
?Hello everybody,
I'm working on the "Use difftime for time comparison" bug (#313634).
Charles directed me to the other one "Use monotonic clock for monitoring"
attended to by Baruch; I believe that's very good idea, however I'd use a bit
more encapsulated & general approach:
1/ I'd create an opaque timer type and its get/set/cmp/inc/dec etc interface
2015 Mar 05
0
Roadmap to 2.7.3
Hi,
There is one issue that I would consider as a major issue and not fixed
yet. It is the use of wall time for scheduling ups polls instead of a
monotonic clock source. I provided a (partial) patch in the past and I
believe there was some work on it.
The bug manifests itself as a stop of monitoring with no alarm when the
clock is moved backwards in time.
Please consider adding this to the
2017 Nov 05
2
What pattern string corresponds to CopyToReg?
Well, that's the thing: I thought that was CopyToReg. I don't know what the
name of the node is to load one value into a register, so I don't know how
to construct such a pattern.
On Sat, Nov 4, 2017 at 9:23 PM Craig Topper <craig.topper at gmail.com> wrote:
> Do you have a pattern for loading an i16 immediate into a 16-bit register?
>
> ~Craig
>
> On Sat, Nov 4,
2014 Apr 16
6
[Bug 2228] New: ssh-agent passwords do not timeout properly
https://bugzilla.mindrot.org/show_bug.cgi?id=2228
Bug ID: 2228
Summary: ssh-agent passwords do not timeout properly
Product: Portable OpenSSH
Version: 6.4p1
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: ssh-agent
Assignee: unassigned-bugs at
2013 Aug 03
2
Call for testing: OpenSSH-6.3
On 2013-08-03 01:41, Darren Tucker wrote:
> On Sat, Aug 3, 2013 at 5:58 PM, Damien Miller <djm at mindrot.org> wrote:
>>> Looking at failure logs - this is what's killing it:
>>> clock_gettime: Invalid argument
> [...]
>> Maybe these platforms lack CLOCK_MONOTONIC? Darren, perhaps we should
>> wrap clock_gettime and have a fallback for
2017 Nov 05
2
What pattern string corresponds to CopyToReg?
Hmm, okay. Then what's the problem being reported here? I'm not sure what
I'm supposed to do with "LLVM ERROR: Cannot select: t1: i16 =
Constant<127>".BTW, the function is:
; ModuleID = 'return.c'
source_filename = "return.c"
target datalayout =
"E-m:e-p:16:16:16-i1:16:16-i8:16:16-i16:16:16-i32:16:16-i64:16:16-S16-n16"
target triple =
2007 Mar 20
1
Re: [nut-commits] svn commit r879 - in trunk: . drivers
Julius: I just realized after committing Michal's patch that you have
a more comprehensive patch on the tracker that approaches this piece
of code differently.
We can go ahead and apply the following patch to the trunk if you
still think it's relevant:
https://alioth.debian.org/tracker/index.php?func=detail&aid=303719&group_id=30602&atid=411544
If you have a newer version of
2018 Oct 08
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
On Mon, Oct 08, 2018 at 10:38:22AM -0700, Andy Lutomirski wrote:
> On Mon, Oct 8, 2018 at 8:27 AM Marcelo Tosatti <mtosatti at redhat.com> wrote:
> >
> > On Sat, Oct 06, 2018 at 03:28:05PM -0700, Andy Lutomirski wrote:
> > > On Sat, Oct 6, 2018 at 1:29 PM Marcelo Tosatti <mtosatti at redhat.com> wrote:
> > > >
> > > > On Thu, Oct 04, 2018
2018 Oct 08
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
On Mon, Oct 08, 2018 at 10:38:22AM -0700, Andy Lutomirski wrote:
> On Mon, Oct 8, 2018 at 8:27 AM Marcelo Tosatti <mtosatti at redhat.com> wrote:
> >
> > On Sat, Oct 06, 2018 at 03:28:05PM -0700, Andy Lutomirski wrote:
> > > On Sat, Oct 6, 2018 at 1:29 PM Marcelo Tosatti <mtosatti at redhat.com> wrote:
> > > >
> > > > On Thu, Oct 04, 2018
2018 Oct 11
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
On Tue, Oct 09, 2018 at 01:09:42PM -0700, Andy Lutomirski wrote:
> On Tue, Oct 9, 2018 at 8:28 AM Marcelo Tosatti <mtosatti at redhat.com> wrote:
> >
> > On Mon, Oct 08, 2018 at 10:38:22AM -0700, Andy Lutomirski wrote:
> > > On Mon, Oct 8, 2018 at 8:27 AM Marcelo Tosatti <mtosatti at redhat.com> wrote:
>
> > > I read the comment three more times and
2018 Oct 11
2
[patch 00/11] x86/vdso: Cleanups, simmplifications and CLOCK_TAI support
On Tue, Oct 09, 2018 at 01:09:42PM -0700, Andy Lutomirski wrote:
> On Tue, Oct 9, 2018 at 8:28 AM Marcelo Tosatti <mtosatti at redhat.com> wrote:
> >
> > On Mon, Oct 08, 2018 at 10:38:22AM -0700, Andy Lutomirski wrote:
> > > On Mon, Oct 8, 2018 at 8:27 AM Marcelo Tosatti <mtosatti at redhat.com> wrote:
>
> > > I read the comment three more times and
2001 Sep 13
4
Setup exits with empty dialog box!
Hi all,
I'm just getting started using WINE. I set it up, and it runs the
canonical Solitaire game just fine. My WINE config file is attached.
I popped in a Sierra Generations Family Tree Deluxe CD and ran its setup
program. A small window titled "Setup" appears with a gas gauge and the
text "Generations(R) 4.2 Setup is preparing the InstallShield(R) Wizard
which will
2012 Feb 13
3
RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)
2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>:
> Hi,
Hi Thomas,
> I want the driver report the battery status from ABM charging controllers
> -patch attached- :
thanks for your patch.
since it introduces a new variable (battery.status.abm), I prefer to
step back and think to something useful more widely.
thus, I'm thinking about a generic
2019 Jan 25
0
[klibc:update-dash] histedit: fix build with musl libc
Commit-ID: e3e5ce11c99ce4e5638df44ed87661945a241632
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e3e5ce11c99ce4e5638df44ed87661945a241632
Author: Baruch Siach <baruch at tkos.co.il>
AuthorDate: Fri, 2 Mar 2018 08:32:16 +0200
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] histedit: fix build with musl
2020 Mar 28
0
[klibc:update-dash] dash: histedit: fix build with musl libc
Commit-ID: a2020fbd897e3c3d41c75294f4e43a0e07487822
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=a2020fbd897e3c3d41c75294f4e43a0e07487822
Author: Baruch Siach <baruch at tkos.co.il>
AuthorDate: Fri, 2 Mar 2018 08:32:16 +0200
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:54 +0000
[klibc] dash: histedit: fix build with
2014 Nov 03
0
RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)
Hi,
Am 13.02.2012 um 18:58 schrieb Arnaud Quette:
> 2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>:
>> Hi,
>
> Hi Thomas,
>
>> I want the driver report the battery status from ABM charging controllers
>> -patch attached- :
>
> For now, I've tracked your patch here:
>
2015 Mar 04
5
Roadmap to 2.7.3
We only have a few open items that I think should be resolved before releasing 2.7.3. The list grew a bit in the past week, but we'll cover that later. Here is the list:
* #93: Devices Dumps Library improvements <https://github.com/networkupstools/nut/issues/93>
* #158: Powerware BCMXCP advanced features <https://github.com/networkupstools/nut/pull/158>
* #185: insecure storage
2018 Sep 14
0
[patch 11/11] x66/vdso: Add CLOCK_TAI support
With the storage array in place it's now trivial to support CLOCK_TAI in
the vdso. Instead of extending the array to accomodate CLOCK_TAI, make use
of the fact that:
- CLOCK ids are set in stone
- CLOCK_THREAD_CPUTIME is never going to be supported in the VDSO so
the array slot 3 is unused
- CLOCK_TAI is id 11 which results in 3 when masked with 0x3
Add the mask to the basetime array