search for: kabylake

...ineBuilder i think. The CPU autodetection code lives in getHostCPUName in lib/Support/Host.cpp, but I don't think the JIT calls into. I think its expected the user would call it or pass a specific CPU string to the MCPU for the EngineBuilder. But getHostCPUName in LLVM 3.5 doesn't recognize Kabylake or Skylake. The Cannot select: means that an intrinsic was used but no pattern could be found in lib/Target/X86/X86GenDAGISel.inc that applies to the enabled feature set. We have separate patterns for that intrinsic for at least SSE4.1 and AVX1 in 3.5. So that implies that the EngineBuilder thinks...

Thank you. I'm letting it auto detect by setting the target using getProcessTarget. I disabled avx512 support by passing -avx512f (and the other variants) to setMAttrs on EngineBuilder. I can see refs to avx512 in X86.td. It's the exact same executable running on Kabylake. What does the Cannot select: specifically mean? Is there some table that doesn't have a definition for a key in it that I would need to patch up? Am I answering your questions? > On 8 May 2017, at 17:32, Craig Topper <craig.topper at gmail.com> wrote: > > I can try to help...

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

...t don't decrease the reference count when probe() ends. > the thing is, it does work for a lot of laptops. We could only observe this on kaby lake and skylake ones. Even on Cannon Lakes it seems to work just fine. > I think that would be much better than blocking any devices behind > Kabylake PCIe root ports from entering D3 (I don't really think the > problem is in the root ports itself but there is something we are > missing when the NVIDIA GPU is put into D3cold or back from there). I highly doubt there is anything wrong with the GPU alone as we have too many indications w...

...nds. > > > > > > > the thing is, it does work for a lot of laptops. We could only observe > > this on kaby lake and skylake ones. Even on Cannon Lakes it seems to > > work just fine. > > Can't you then limit it to those? > > I've experienced that Kabylake root ports can enter and exit in D3cold > just fine because we do that for Thunderbolt for example. But that > always requires help from ACPI. If the system is using non-standard ACPI > methods for example that may require some tricks in the driver side. > yeah.. I am not quite sure wh...

...of pointers in drmProcessPciDevice Qiang Yu (1): drm: fix multi GPU drmGetDevices only return one device Rob Clark (1): freedreno/msm: fix memory leak on ringbuffer free Rob Herring (1): Android: strip out header files from sources list Rodrigo Vivi (2): intel: Add more Kabylake PCI IDs. intel: Removing PCI IDs that are no longer listed as Kabylake. Sonny Jiang (1): tests/amdgpu: adapt to new polaris10/11 uvd fw git tag: libdrm-2.4.69 http://dri.freedesktop.org/libdrm/libdrm-2.4.69.tar.bz2 MD5: 2cee933bdef3e10d552d97b3a8fb640f libdrm-2.4.69.tar.bz2 SHA1: 0...

...hecks that drop/setMaster correctly transfer master state (Thomas Hellstrom/Daniel Vetter) - Wildcard characters are now accepted when using the --run-subtest command line option to specify multiple subtests to run. (Thomas Wood) - Add support for Broxton in intel_audio_dump (Han Lu) - Added Kabylake support (Rodrigo Vivi/Wayne Boyer) - Many other bug fixes and improvements Complete list of changes since 1.12: Ander Conselvan de Oliveira (1): testdisplay: Fix segfault after first modeset fails Ben Widawsky (1): igt/intel_aubdump: Use the right ring Chris Wilson (24): ben...

...ecrease the reference count when probe() ends. > > > > the thing is, it does work for a lot of laptops. We could only observe > this on kaby lake and skylake ones. Even on Cannon Lakes it seems to > work just fine. Can't you then limit it to those? I've experienced that Kabylake root ports can enter and exit in D3cold just fine because we do that for Thunderbolt for example. But that always requires help from ACPI. If the system is using non-standard ACPI methods for example that may require some tricks in the driver side. > > I think that would be much better than...

...was talking with others in the past about it, Windows is doing that before using ACPI calls, but maybe they have some similar workarounds for certain intel bridges as well? I am sure it affects more than the one I am blacklisting here, but I rather want to check each device before blacklisting all kabylake and sky lake bridges (as those are the ones were this issue can be observed). Sadly we had no luck getting any information about such workaround out of Nvidia or Intel. > > On Wed, Oct 16, 2019 at 9:14 PM Bjorn Helgaas <helgaas at kernel.org> wrote: > > > > > > On We...

...hris Wilson) - Various modifications to intel_chipset: Replace lookup of GT size with computation, remove unused PCI_CHIP ids, converting platforms names using device info (Chris Wilson) - tests/kms_chv_cursor_fail: Run the tests with fewer steps (Maarten Lankhorst) - lib/intel_chipset: Add more Kabylake PCI IDs and removed PCI IDs that are no longer listed as Kabylake (Rodrigo Vivi) - Basic framework for GVT-g testing has landed (Chris Wilson) - Various improvements to tests/kms_flip (Ville Syrj�l�) - igt/kms_cursor_legacy: Add a rudimentary test to detect stalled cursors, detect pageflip e...

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

...- Added a generic dummy workload helper for submitting GPU workloads that consume exactly a specified amount of time. (Abdiel Janulgue) - Added C functions for driver loading/unloading, pkill and lsof, for converting shell script tests to C code. (Marius Vlad) Tools changes: - intel_reg: Add Kabylake support. (Jani Nikula) - intel_bios_reader: Also dump PSR info. (Ville Syrjälä) - intel_guc_logger: New tool for capturing logs from the GuC firmware. (Akash Goel) - intel_aubdump: Added commandline option to stream the dump to another process. (Lionel Landwerlin) - intel_aubdump: Annotate...

...ols-check radeon: Pass radeon_bo_open flags to the DRM_RADEON_GEM_CREATE ioctl Rob Clark (4): freedreno: update uapi freedreno: small refactor for get_param freedreno: add support for FD_MAX_FREQ Bump version for release Rodrigo Vivi (1): intel/kbl: Add Kabylake PCI ids Stefan Agner (2): kmstest: Use util_open() tests: add fsl-dcu-drm to modules Sumit Semwal (1): android: enable building static version of libdrm Thierry Reding (1): tests: util: Fixup util_open() parameter order Ville Syrjälä (1): Fix memory...

...driver until this is understood better? That can be done by calling pm_runtime_forbid() (or not calling pm_runtime_allow() in the driver). Or in case of PCI driver you just don't decrease the reference count when probe() ends. I think that would be much better than blocking any devices behind Kabylake PCIe root ports from entering D3 (I don't really think the problem is in the root ports itself but there is something we are missing when the NVIDIA GPU is put into D3cold or back from there).

...ut it, Windows is > > doing that before using ACPI calls, but maybe they have some similar > > workarounds for certain intel bridges as well? I am sure it affects > > more than the one I am blacklisting here, but I rather want to check > > each device before blacklisting all kabylake and sky lake bridges (as > > those are the ones were this issue can be observed). > > > > Sadly we had no luck getting any information about such workaround out > > of Nvidia or Intel. > > I really would like to provide you more information about such > workaround b...

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: > >

...vidia card in some way. After a lot of experimentation I found a workaround: during resume, set the value of PCI_PREF_BASE_UPPER32 to 0 on the parent PCI bridge. Easily done in drivers/pci/quirks.c. Now all nvidia stuff works fine. As an example of an affected product, take the Asus X542UQ (Intel KabyLake i7-7500U with Nvidia GeForce 940MX). The PCI bridge is: 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d10] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 120 Bus: primary=00, secondary=01, subordinate=01, se...

...hers in the past about it, Windows is > doing that before using ACPI calls, but maybe they have some similar > workarounds for certain intel bridges as well? I am sure it affects > more than the one I am blacklisting here, but I rather want to check > each device before blacklisting all kabylake and sky lake bridges (as > those are the ones were this issue can be observed). > > Sadly we had no luck getting any information about such workaround out > of Nvidia or Intel. I really would like to provide you more information about such workaround but I'm not aware of any ;-) I...

...tion GP107M [GeForce GTX 1050 Mobile] 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05) Under 00:1c.0, there is a wireless adapter. > As an example of an affected product, take the Asus X542UQ (Intel > KabyLake i7-7500U with Nvidia GeForce 940MX). The PCI bridge is: > > 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI > Express Root Port [8086:9d10] (rev f1) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0, IRQ 120 > Bus: primary=00, seconda...

...Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: harry_x at babylon5.cz QA Contact: xorg-team at lists.x.org When starting the machine on Dell Inspiron 7000 (Kabylake, GTX 1050 Ti) with HDMI monitor connected (HDMI output is provided by NVIDIA card, eDP is connected to internal), everything seems to work (using reverse prime that is automatically setup). There is lot of tearing, but it works. But when starting the machine without HDMI output connected (so the N...