search for: kabylakes

...lt; > llvm-dev at lists.llvm.org> wrote: > >> Hi, >> >> I have a JIT compiler using the legacy JIT on LLVM 3.5 that, when run on >> the Xeon v5 Skylakes produces "Cannot select: intrinsic % >> llvm.x86.sse41.round.sd". Note, this does not occur on i7 Kabylakes. To >> get this far I had to disable AVX512 code gen. >> >> Upgrading the system I am looking at from 3.5 to a later version is a big >> job that I'd prefer not to have on my critical path. >> >> Does anyone have any tips on where I would look to debug this s...

...Andy Schneider via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> I have a JIT compiler using the legacy JIT on LLVM 3.5 that, when run on the Xeon v5 Skylakes produces "Cannot select: intrinsic %llvm.x86.sse41.round.sd". Note, this does not occur on i7 Kabylakes. To get this far I had to disable AVX512 code gen. >> >> Upgrading the system I am looking at from 3.5 to a later version is a big job that I'd prefer not to have on my critical path. >> >> Does anyone have any tips on where I would look to debug this sort of issue? I&...

Hi, I have a JIT compiler using the legacy JIT on LLVM 3.5 that, when run on the Xeon v5 Skylakes produces "Cannot select: intrinsic %llvm.x86.sse41.round.sd". Note, this does not occur on i7 Kabylakes. To get this far I had to disable AVX512 code gen. Upgrading the system I am looking at from 3.5 to a later version is a big job that I'd prefer not to have on my critical path. Does anyone have any tips on where I would look to debug this sort of issue? I'm new to LLVM. Thanks Andy

On Tue, Oct 1, 2019 at 10:47 AM Mika Westerberg <mika.westerberg at linux.intel.com> wrote: > > On Mon, Sep 30, 2019 at 06:36:12PM +0200, Karol Herbst wrote: > > On Mon, Sep 30, 2019 at 6:30 PM Mika Westerberg > > <mika.westerberg at linux.intel.com> wrote: > > > > > > On Mon, Sep 30, 2019 at 06:05:14PM +0200, Karol Herbst wrote: > > > >

On Tue, Oct 1, 2019 at 11:11 AM Mika Westerberg <mika.westerberg at linux.intel.com> wrote: > > On Tue, Oct 01, 2019 at 10:56:39AM +0200, Karol Herbst wrote: > > On Tue, Oct 1, 2019 at 10:47 AM Mika Westerberg > > <mika.westerberg at linux.intel.com> wrote: > > > > > > On Mon, Sep 30, 2019 at 06:36:12PM +0200, Karol Herbst wrote: > > > >

Here's a new libdrm release, which I needed in order to use the new vc4 ioctl in Mesa. Alex Deucher (2): tests/amdgpu: expand write/copy tests to compute tests/amdgpu: expand write/copy tests to compute Christian König (1): amdgpu: fix fence status query Eric Anholt (2): vc4: Update kernel headers for getparam addition. Bump version to 2.4.69 for release. Jan

A new intel-gpu-tools quarterly release is available with the following changes: - New test: kms_atomic tests atomic mode setting (Daniel Stone) - New test: core_prop_blob tests blob properties (Daniel Stone) - New test: gem_request_retire targets request retirement code paths (Tvrtko Ursulin) - New test: core_setmaster_vs_auth checks that drop/setMaster correctly transfer master state

On Tue, Oct 01, 2019 at 10:56:39AM +0200, Karol Herbst wrote: > On Tue, Oct 1, 2019 at 10:47 AM Mika Westerberg > <mika.westerberg at linux.intel.com> wrote: > > > > On Mon, Sep 30, 2019 at 06:36:12PM +0200, Karol Herbst wrote: > > > On Mon, Sep 30, 2019 at 6:30 PM Mika Westerberg > > > <mika.westerberg at linux.intel.com> wrote: > > > >

On Wed, Oct 16, 2019 at 11:37 PM Bjorn Helgaas <helgaas at kernel.org> wrote: > > [+cc linux-acpi] > > On Wed, Oct 16, 2019 at 09:18:32PM +0200, Karol Herbst wrote: > > but setting the PCI_DEV_FLAGS_NO_D3 flag does prevent using the > > platform means of putting the device into D3cold, right? That's > > actually what should still happen, just the D3hot step

Hello, A new intel-gpu-tools quarterly release is available with the following changes: - Build automatically tests required when issueing a make check, Tests/subtests that receive a crash signal should print a backtrace when i-g-t is built with libunwind support (Marius Vlad) - lib/igt_kms: Force connector probing on first use (Chris Wilson) - vc4: Add a test for BO lookup failure error path

https://bugs.freedesktop.org/show_bug.cgi?id=104621 Bug ID: 104621 Summary: Nouveau prevents booting on Pascal Gpu Product: Mesa Version: 17.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

A new intel-gpu-tools quarterly release is available with the following changes: Library changes: - Added an iterator that generate primes for creating input data that should not fall into any patterns that may be optimised by the drivers. (Chris Wilson) - Crashes in fixture blocks now print a stacktrace. (Marius Vlad) - Added support for various system suspend/resume options. (Imre Deak)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alex Deucher (7): tests/amdgpu: make amdgpu_sdma_test_exec_cs() generic (v2) tests/amdgpu: make amdgpu_command_submission_sdma_write_linear generic tests/amdgpu: add a test for cp write data tests/amdgpu: make amdgpu_command_submission_sdma_const_fill generic tests/amdgpu: add a test for cp dma fill

On Mon, Sep 30, 2019 at 06:36:12PM +0200, Karol Herbst wrote: > On Mon, Sep 30, 2019 at 6:30 PM Mika Westerberg > <mika.westerberg at linux.intel.com> wrote: > > > > On Mon, Sep 30, 2019 at 06:05:14PM +0200, Karol Herbst wrote: > > > still happens with your patch applied. The machine simply gets shut down. > > > > > > dmesg can be found here: >

On Mon, Oct 21, 2019 at 3:33 PM Mika Westerberg <mika.westerberg at intel.com> wrote: > > On Wed, Oct 16, 2019 at 11:48:22PM +0200, Karol Herbst wrote: > > On Wed, Oct 16, 2019 at 11:37 PM Bjorn Helgaas <helgaas at kernel.org> wrote: > > > > > > [+cc linux-acpi] > > > > > > On Wed, Oct 16, 2019 at 09:18:32PM +0200, Karol Herbst wrote:

On Mon, Sep 30, 2019 at 6:30 PM Mika Westerberg <mika.westerberg at linux.intel.com> wrote: > > On Mon, Sep 30, 2019 at 06:05:14PM +0200, Karol Herbst wrote: > > still happens with your patch applied. The machine simply gets shut down. > > > > dmesg can be found here: > >

Hi, We are facing a suspend/resume problem with many different Asus laptop models (30+ products) with Intel chipsets (multiple generations) and nvidia GPUs (several different ones). Reproducers include: 1. Boot 2. Suspend/resume 3. Load nouveau driver 4. Start X 5. Observe slow X startup and many many errors in logs (primarily nouveau fifo faults) or 1. Boot 2. Load nouveau driver 3. Start X

On Wed, Oct 16, 2019 at 11:48:22PM +0200, Karol Herbst wrote: > On Wed, Oct 16, 2019 at 11:37 PM Bjorn Helgaas <helgaas at kernel.org> wrote: > > > > [+cc linux-acpi] > > > > On Wed, Oct 16, 2019 at 09:18:32PM +0200, Karol Herbst wrote: > > > but setting the PCI_DEV_FLAGS_NO_D3 flag does prevent using the > > > platform means of putting the device

Hi Daniel, On Fri, Aug 24, 2018 at 11:31:54AM +0800, Daniel Drake wrote: > Hi, > > We are facing a suspend/resume problem with many different Asus laptop > models (30+ products) with Intel chipsets (multiple generations) and > nvidia GPUs (several different ones). Reproducers include: Are these systems also affected through runtime power management? For example: modprobe

https://bugs.freedesktop.org/show_bug.cgi?id=101573 Bug ID: 101573 Summary: GP107 crash with no HDMI connected on 4.12.rc6 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at