Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - JeGX

Pages: 1 ... 4 5 [6] 7 8 ... 103
A new class of side channel vulnerabilities impacting all modern Intel chips have been disclosed, which can use speculative execution to potentially leak sensitive data from a system’s CPU.

Intel said that the newest class of vulnerabilities, dubbed Microarchitectural Data Sampling (MDS), consist of four different attacks, which all ultimately depend on different ways of executing side channel attacks to siphon data from impacted systems.


The  four different attack vectors are dubbed ZombieLoad, Fallout, RIDL (Rogue In-Flight Data Load) and Store-to-Leak Forwarding.


Intel said that the new MDS class of flaws is addressed in hardware starting with select 8th and 9th Generation Intel Core processors, as well as the 2nd Generation Intel Xeon Scalable processor family. Future chips will also have integrated fixes.

Source: Intel CPUs Impacted By New Class of Spectre-Like Attacks

CVEs assigned for MSD vulnerabilities
- CVE-2018-12126: Microarchitectural Store Buffer Data Sampling (MSBDS) - CVSS score 6.5: Medium, exploited by Fallout attack
- CVE-2018-12127: Microarchitectural Load Port Data Sampling (MLPDS) - CVSS score 6.5: Medium, exploited by RIDL attack
- CVE-2018-12130: Microarchitectural Fill Buffer Data Sampling (MFBDS) - CVSS score 6.5: Medium, exploited by RIDL attack
- CVE-2019-11091: Microarchitectural Data Sampling Uncacheable Memory (MDSUM) - CVSS score 3.8: Low, exploited by RIDL attack

Source: New RIDL and Fallout Attacks Impact All Modern Intel CPUs

Radeon GPU Profiler (RGP) is a tool from AMD that allows for deep inspection of GPU workloads.

The Radeon GPU Profiler (RGP) is a ground-breaking low-level optimization tool from AMD. It provides detailed timing information on Radeon Graphics using custom, built-in, hardware thread-tracing, allowing the developer deep inspection of GPU workloads.

This unique tool generates easy to understand visualizations of how your DirectX 12 and Vulkan games interact with the GPU at the hardware level. Profiling a game is both a quick, and simple process using the Radeon Developer Panel and the public display driver.

The new version 1.5.1 brings the following changes:

This release has support for detailed instruction tracing. This feature is currently available in the 19.10 driver for Ubuntu and the Adrenalin 2019 Edition 19.5.1 for Windows. Newer drivers will continue to support this feature.

Radeon GPU Profiler

-  Support for displaying profiles taken with instruction tracing data
-  Support for displaying user events in the Wavefront Occupancy timeline view
-  Support to display GCN ISA disassembly in the Pipeline state view
-  Support for showing and colorizing API PSO hash for each event
-  New grouping modes based on API PSO hash
-  Improved grouping of events and waves
-  Additional state bucket to support API PSO hashes
-  Barriers pane now has sortable columns in the table
-  Version number added to title bar
-  A Check For Updates feature has been added to alert users when a new version of the tool is available.

Radeon Developer Panel

- Support to capture detailed instruction tracing data based on API PSO hash
- Connection pane redesign with basic and advanced modes, allowing for a simpler workflow.
- Bug/stability fixes


Radeon GPU profiler

Change log for May 13, 2019 Vulkan 1.1.108 spec update:

  * Update release number to 108.

Internal Issues:

  * Clarify that only external resources can be bound to external memory in
    valid usage statements for flink:vkBindBufferMemory,
    flink:vkBindImageMemory, slink:VkSparseMemoryBind, and
    slink:VkSparseImageMemoryBind (internal issue 1496).
  * Move all `vk.xml`requirements for
    flink:vkGetDeviceGroupSurfacePresentModes2EXT into
    `<<VK_EXT_full_screen_exclusive>>` (internal issue 1622).
  * Add some missing valid usage statements for
    flink:vkCmdEndQueryIndexedEXT (internal issue 1638).
  * Specify rules for defining "`New Flags and Bitmask Types`" in that
    section of the style guide (internal issue 1649).
  * Add a comment to the `vk.xml` extension block for
    `VK_ANDROID_native_buffer` explaining why the extension is tagged
    `"disabled"` (internal issue 1657).
  * Fix typos in the description of slink:VkImageViewCreateInfo (internal
    issue 1661).
  * Modify valid usage statements for slink:VkImageViewCreateInfo to fix the
    description about the restriction for pname:baseArrayLayer and
    pname:layerCount from pname:extent.depth to the depth of mipmap level
    while creating a 2D array image view on a 3D image.
  * Forbid structures that contain opaque types (images or samplers) in the
    SPIR-V <<spirvenv-module-validation, Validation Rules within a Module>>
  * Minor editorial changes for the `VK_EXT_swapchain_colorspace` extension
    in the description of slink:VkColorSpace KHR and `vk.xml`, including:
  ** Consistently specify which function (OETF or Inverse-EOTF) is being
  ** Remove the Display P3 EOTF, since no other EOTFs are defined;
  ** Include luminance range for the HLG OETF;
  ** Remove a duplicated paragraph; and,
  ** Rename ename:VK_COLOR_SPACE_DISPLAY_P3_LINEAR_EXT, leaving the old
     ename:VK_COLOR_SPACE_DCI_P3_LINEAR_EXT token as an alias.

New Extensions:

  * `<<VK_NV_framebuffer_mixed_samples_coverage_reduction_mode>>`
  * `<<VK_KHR_uniform_buffer_standard_layout>>`


New extensions:
- VK_KHR_uniform_buffer_standard_layout
- VK_NV_framebuffer_mixed_samples_coverage_reduction_mode: not yet documented.

Toon rendering.

GeeXLab - Toon / cel-shading

Testing some outline techniques.

GeeXLab - Outline rendering

GeeXLab - Outline rendering

Geeks3D's GPU Tools / Glitches in Seascape demo, the return!
« on: May 12, 2019, 09:46:40 AM »
I received this screenshot:

GPU Caps Viewer - Seascape demo, visual glitches

Hardware: GeForce GTX 960M with latest 430.64 driver.

The artifacts are also visible on my RTX 2070. In Vulkan and OpenGL.
It's weird, because I never saw these artifacts nor received feedbacks before. Looks like something has changed in NV drivers recently...

I'm working on the demo...

NVIDIA has fixed several security flaws in recent graphics drivers and, for GeForce users / gamers, it's recommended to install the latest 430.64 that includes all security patches.

NVIDIA has released a software security update for the NVIDIA GPU Display Driver. This update addresses issues that may lead to denial of service, escalation of privileges, code execution, or information disclosure.

NVIDIA Windows GPU Display Driver contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape where the product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes, which may lead to denial of service, escalation of privileges, or information disclosure.

NVIDIA Windows GPU Display Driver installer software contains a vulnerability in which it incorrectly loads Windows system DLLs without validating the path or signature (also known as a binary planting or DLL preloading attack), leading to escalation of privileges through code execution.

NVIDIA Windows GPU Display Driver contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DeviceIoControl where the software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer, which may lead to denial of service.


NVIDIA security patches in graphics driver - May 2019

We're continuing to expand the impact of Vulkan on Android, our implementation of the low-overhead, cross-platform API for high-performance 3D graphics. We’re working together with our device manufacturer partners to make Vulkan 1.1 a requirement on all 64-bit devices running Android Q and higher, and a recommendation for all 32-bit devices. For game and graphics developers using OpenGL, we’re also working towards a standard, updateable OpenGL driver for all devices built on Vulkan. In Android Q we're adding experimental support for ANGLE on top of Vulkan on Android devices. 

Android Q is the 10th version of Android.


Android Q

New features and changes:
Game Ready
- Provides the optimal gaming experience for RAGE 2, Total War: Three Kingdoms, and World War Z

Fixed Issues
- Fixes higher CPU usage by NVDisplay.Container.exe introduced in 430.39 driver. [2577118]
- [3DMark Time Spy]: Flickering observed when benchmark is launched. [200511272]
- [BeamNG]: The application crashes when the game is launched. [2575392]
- [Shadow of the Tomb Raider]: The game freezes when launched in SLI mode. [2575536]
- [Hitman 2 DirectX 12]: The game crashes. [2584342]
- The desktop flickers when videos are played on the secondary monitor. [2552316 2565509]

- Latest GeForce driver @ Geeks3D
- 430.64 win10 64-bit (desktop + notebook) @ NVIDIA
- 425.31 win7 64-bit (desktop) @ NVIDIA

GRD 430.64 exposes  OpenGL 4.6 (419 extensions) and Vulkan 1.1.99 for a GeForce RTX 2070, like previous GeForce 430.39

GPU Caps Viewer + RTX 2080

Do you happen to know, how to select the GPU in Linux?

I believe you can force the GPU by launching the app on the monitor connected to the GPU you want to test (assuming you have a monitor connector to each GPU). But I'm not sure. Maybe there is a way to force a particular display in command line using args like "localhost:0.1"...  Let me know if you find something interesting.

Beginning with Windows Insiders builds this Summer, we will include an in-house custom-built Linux kernel to underpin the newest version of the Windows Subsystem for Linux (WSL). This marks the first time that the Linux kernel will be included as a component in Windows. This is an exciting day for all of us on the Linux team at Microsoft and we are thrilled to be able to tell you a little bit about it.


The kernel itself will initially be based on version 4.19, the latest long-term stable release of Linux. The kernel will be rebased at the designation of new long-term stable releases to ensure that the WSL kernel always has the latest Linux goodness.


During Intel's Investor Day, Intel has revealed some details about its upcoming processors and their manufacturing process:

- Intel Details Manufacturing through 2023: 7nm, 7+, 7++, with Next Gen Packaging
- Intel Reveals "Tiger Lake" Architecture with 2020 release plans

Intel roadmap 2020 - Ice Lake in June 2019

Intel roadmap 2020 - Ice Lake, Lakefield and tiger lake

Intel 14nm, 10nm and 7nm roadmap

Intel wants to power the world

A demo showing how to use NVIDIA FleX engine in a simple scene: particles + collision shapes.
32k particles are animated in realtime.

Requires GeeXLab 0.28+ and a CUDA-capable graphics card (GeForce or Quadro).



- FleX demo
- GeeXLab

NVIDIA FleX demo - GeeXLab

A new GeeXLab is available for for Windows 64-bit, Linux 64-bit and macOS.

Release notes:


The Scripting API

The rootard guide:
- GeeXLab Rootard Guide
- Guide du Rootard GeeXLab

Full changelog:

Version - 2019.05.04
! (2019.05.04) updated gh_imgui lib with missing color elements for
  tabs (see IMGUI_TAB_COLOR, etc. in the scripting API doc).
* (2019.05.03) fixed minor bugs in the stopping phase of some plugins
  (Bullet3 and FleX).
+ (2019.05.03) added screenshot functionality at the end of a demo
  (command line).
+ (2019.05.02) [Windows / Linux] added new library: gh_flex to deal
  with NVIDIA FleX plugin.
+ (2019.05.02) [Windows / Linux] added NVIDIA FleX plugin for particles
  and fluids simulation.
* (2019.05.02) fixed a bug in the OpenGL renderer: VAOs were not enabled
  with VBOs in the gh_vb library: drawing with gh_vb lib was not
  possible with an OpenGL 3 core profile.

GeeXLab 3D programming tool

This part of the DDGI article describes integrated ray-traced glossy GI and dynamic diffuse GI at a level suitable for a product manager or art director to begin evaluating the technique. I describe the previous state of the art techniques and show many examples of DDGI handling particularly difficult cases.


The current GpuTest is OpenGL only and on Windows only the primary GPU can be used for rendering. But some graphics drivers (NVIDIA for example) allow you to select the GPU (see here).  On Linux there is particular option for selecting the GPU. I'm working on the successor of GpuTest ( :P ) and I will try to add this option.

I never tested the Radeon VII and I don't know how this GPU handles FurMark.
Maybe try to increase the power target using WattMan.

First contact with ray tracing in Vulkan. The easiest part  :P

GeeXLab + Vulkan raytracing information

GeeXLab - english forum / Shadertoy Demopack - Warp Tunnel
« on: May 07, 2019, 08:49:36 AM »
Demo Warp Tunnel ported to GeeXLab.

Location in the demopack: gl-32-shadertoy-01/gl32-warp-tunnel.xml

- Shadertoy demopack for GeeXLab
- GeeXLab downloads

Rendering speed (GeForce RTX 2070 + driver 430.53):
- 800x480: 1100 FPS
- 2560x1440: 150 FPS

Shadertoy demo ported to GeeXLab

Geeks3D's GPU Tools / ASUS FurMark ROG released
« on: May 07, 2019, 08:36:55 AM »
A new version of FurMark ROG has been released.



Version - 2019.05.06
+ added support of GeForce GTX 1650
! updated user execution level to highestAvailable.
! updated with latest GeeXLab framework.

Version - 2019.04.14
+ added online scores submission.
+ added four new FurMark-based tests that allocate
  lot of graphics memory (VRAM): 1700MB, 3200MB, 5200MB
  and 6500MB.
- removed old rog07 / GPU-Memtest.
+ added support of recent GeForce and Radeon GPUs
+ disallow screen saver and screen blanking.
+ added logging of GPU data (command line).
! increased fur density of ROG mesh
! updated command line options.
* fixed bugs in the Vulkan renderer.
! updated with latest GeeXLab framework.


Pages: 1 ... 4 5 [6] 7 8 ... 103