Displaying 17 results from an estimated 17 matches for "ndelayed".
Did you mean:
delayed
2007 Apr 18
1
RFC: const_udelay in 018-delay functions patch
So I implemented udelay and ndelay through a single paravirt_op, =
const_udelay, instead of having either two separate paravirt-ops for =
udelay or ndelay, or a redundant const_udelay paravirt_op. Anybody have =
any objection to reworking the patch this way?
-------------- next part --------------
Add paravirtualized delay mechanisms to paravirt-ops. There are two delays
used by native
2007 Apr 18
1
RFC: const_udelay in 018-delay functions patch
So I implemented udelay and ndelay through a single paravirt_op, =
const_udelay, instead of having either two separate paravirt-ops for =
udelay or ndelay, or a redundant const_udelay paravirt_op. Anybody have =
any objection to reworking the patch this way?
-------------- next part --------------
Add paravirtualized delay mechanisms to paravirt-ops. There are two delays
used by native
2007 Apr 18
0
[PATCH 5/9] Paravirt drop udelay op
Not respecting udelay causes problems with any virtual hardware that is
passed through to real hardware. This can be noticed by any device that
interacts with the real world in real time - like AP startup, which takes
real time. Or keyboard LEDs, which should blink in real-time. Or floppy
drives, but only when passed through to a real floppy controller on OSes
which can't sufficiently
2007 Apr 18
0
[PATCH 5/9] Paravirt drop udelay op
Not respecting udelay causes problems with any virtual hardware that is
passed through to real hardware. This can be noticed by any device that
interacts with the real world in real time - like AP startup, which takes
real time. Or keyboard LEDs, which should blink in real-time. Or floppy
drives, but only when passed through to a real floppy controller on OSes
which can't sufficiently
2009 Jun 01
1
LM/GLM can't find weights vector from within a function (PR#13735)
...ere rFormula is a text string, rData is a 1422 x 17 timeSeries data matrix,
both passed from the console, i is a counter, W is a 1422 x 1 numeric vector of
weights declared locally within the function.
The function definition is as follows:
redls<-function(rFormula, rData, nStart, rBeta=1., nDelayed=3)
I already tried to define W externally to the function and parse it as a
parameter, change its name, declare it as an array, declare it as a timeSeries
object, with always the same error. Invoking glm instead of lm gives also the
same error. The ls.str listing of W immediately before calling lm...
2011 Nov 24
1
[PATCH] nouveau: implement precise vblank timestamping
This patch implements the drivers hooks needed for precise vblank
timestamping. This is a complementary patch to Mario Kleiner's
patches to to improve swap scheduling. With the complete
patchset applied nouveau will be able to provide correct and
precise pageflip timestamps (compliant to OML_sync_control spec)
Kudos to Mario for his many helpful comments and testing.
Signed-off-by: Lucas
2012 Feb 15
2
[Patches][nouveau/kms]: Precise Vblank and pageflip timestamping
Hi,
these are two patches against the nouveau kms driver. The first patch
makes sure that pageflip completion events get their vblank count and
timestamp from the drm. The second patch from Lucas Stach, here included
with his permission, makes sure that the timestamps of vblanks are
calculated with high precision and robustness. Both patches together
make sure that all timestamps returned by the
2012 Apr 25
2
[PATCH 1/2] drm/nouveau: Use drm_vblank_count_and_time() for pageflip completion events.
From: Mario Kleiner <mario.kleiner at tuebingen.mpg.de>
Emit kms pageflip completion events with proper vblank count
and timestamp for the vblank interval in which the pageflip
completed. This makes the timestamps and counts consistent with
what the OML_sync_control spec defines.
v2 Lucas Stach: rebased on top of nouveau tree and resolved trivial
conflict.
Signed-off-by: Mario Kleiner
2012 Feb 16
5
[Patches][nouveau/kms]: Precise Vblank and pageflip timestamping v2
Just updated versions of the patches send by Mario Kleiner. This ones are
rebased on top of the nouveau tree and updated according to the review
feedback.
Regards,
Lucas
2007 Apr 18
8
[PATCH 0/7] x86 paravirtualization infrastructure
The following patches introduce the core infrastructure needed to
paravirtualize the 32-bit x86 Linux kernel. This is done by moving
virtualization sensitive insn's or code paths to a function table,
paravirt_ops. This structure can be populated with hypervisor specific
calls or native stubs and currently support running on bare metal, VMI,
Xen, or Lhype. These patches apply to
2007 Apr 18
8
[PATCH 0/7] x86 paravirtualization infrastructure
The following patches introduce the core infrastructure needed to
paravirtualize the 32-bit x86 Linux kernel. This is done by moving
virtualization sensitive insn's or code paths to a function table,
paravirt_ops. This structure can be populated with hypervisor specific
calls or native stubs and currently support running on bare metal, VMI,
Xen, or Lhype. These patches apply to
2007 Apr 18
20
[patch 00/20] XEN-paravirt: Xen guest implementation for paravirt_ops interface
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual block
2007 Apr 18
20
[patch 00/20] XEN-paravirt: Xen guest implementation for paravirt_ops interface
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual block
2007 Apr 18
20
[patch 00/20] XEN-paravirt: Xen guest implementation for paravirt_ops interface
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual block
2007 Apr 18
25
[patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual
2007 Apr 18
25
[patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual
2007 Apr 18
25
[patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual