search for: inexhaust

...is not supported) - so this scheme wouldn?t introduce additional overhead over RDMSR. >> >> Because then guest user code will think that rdrand is there and will >> try to use it, resulting in abysmal performance. >> > > Yes, the presence of RDRAND implies a cheap and inexhaustible entropy > source. A guest kernel couldn't make it look like RDRAND is not present to guest userspace? Christopher -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.

...is not supported) - so this scheme wouldn?t introduce additional overhead over RDMSR. >> >> Because then guest user code will think that rdrand is there and will >> try to use it, resulting in abysmal performance. >> > > Yes, the presence of RDRAND implies a cheap and inexhaustible entropy > source. A guest kernel couldn't make it look like RDRAND is not present to guest userspace? Christopher -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.

...hooking up fences, I advise you to also hook up drm_syncobj. > Internally they each resolve to another fence, so the mechanics are > identical, you just need another array in the uABI for in/out syncobj. > The advantage of drm_syncobj is that userspace can track internal fences > using inexhaustible handles, reserving the precious fd for IPC or KMS. I'm not sure that I properly understand how to use these. It looks as if they are better fence FDs, so in case where you submit internal work you would go with a drm_syncobj and when you need access to the fence from a different process or...

On Fri, Sep 19, 2014 at 1:21 PM, Nadav Amit <nadav.amit at gmail.com> wrote: > > On Sep 19, 2014, at 9:42 PM, Andy Lutomirski <luto at amacapital.net> wrote: > >> On Fri, Sep 19, 2014 at 11:30 AM, Christopher Covington >> <cov at codeaurora.org> wrote: >>> On 09/17/2014 10:50 PM, Andy Lutomirski wrote: >>>> Hi all- >>>>

On Fri, Sep 19, 2014 at 1:21 PM, Nadav Amit <nadav.amit at gmail.com> wrote: > > On Sep 19, 2014, at 9:42 PM, Andy Lutomirski <luto at amacapital.net> wrote: > >> On Fri, Sep 19, 2014 at 11:30 AM, Christopher Covington >> <cov at codeaurora.org> wrote: >>> On 09/17/2014 10:50 PM, Andy Lutomirski wrote: >>>> Hi all- >>>>

...hook up drm_syncobj. > > > Internally they each resolve to another fence, so the mechanics are > > > identical, you just need another array in the uABI for in/out syncobj. > > > The advantage of drm_syncobj is that userspace can track internal fences > > > using inexhaustible handles, reserving the precious fd for IPC or KMS. > > > > I'm not sure that I properly understand how to use these. It looks as if > > they are better fence FDs, so in case where you submit internal work you > > would go with a drm_syncobj and when you need access...

...or the GPU. Whilst hooking up fences, I advise you to also hook up drm_syncobj. Internally they each resolve to another fence, so the mechanics are identical, you just need another array in the uABI for in/out syncobj. The advantage of drm_syncobj is that userspace can track internal fences using inexhaustible handles, reserving the precious fd for IPC or KMS. -Chris

...I advise you to also hook up drm_syncobj. > > Internally they each resolve to another fence, so the mechanics are > > identical, you just need another array in the uABI for in/out syncobj. > > The advantage of drm_syncobj is that userspace can track internal fences > > using inexhaustible handles, reserving the precious fd for IPC or KMS. > > I'm not sure that I properly understand how to use these. It looks as if > they are better fence FDs, so in case where you submit internal work you > would go with a drm_syncobj and when you need access to the fence from a...

...DRAND executed while it is not supported) - so this scheme wouldn?t introduce additional overhead over RDMSR. > > Because then guest user code will think that rdrand is there and will > try to use it, resulting in abysmal performance. > Yes, the presence of RDRAND implies a cheap and inexhaustible entropy source. -hpa

...this scheme wouldn?t introduce additional overhead over RDMSR. >>> >>> Because then guest user code will think that rdrand is there and will >>> try to use it, resulting in abysmal performance. >>> >> >> Yes, the presence of RDRAND implies a cheap and inexhaustible entropy >> source. > > A guest kernel couldn't make it look like RDRAND is not present to guest > userspace? > It could, but how would you enumerate that? A new "RDRAND-CPL-0" CPUID bit pretty much would be required. -hpa

* NEW CHANNEL DRIVER FOR ASTERISK 1.6 AND VOXSWITCH 3 ADDS AUDIO AND VIDEO TO MICROBLOGGING! In a surprising move, Digium in partnership with Edvina today released a new channel driver for Asterisk, chan_tweet. The driver connects seamlessly to several microblogging platforms, including Twitter, Facebook, Laconi.ca/Identi.ca and GSM text/SMS. The main feature of this new module is to

From: Thierry Reding <treding at nvidia.com> This set of patches adds support for fences to Tegra DRM and complements the fence FD support for Nouveau. Technically this isn't necessary for a fence-based synchronization loop with Nouveau because the KMS core takes care of all that, but engines behind host1x can use the IOCTL extensions provided here to emit fence FDs that in turn can be