Changes in Makefile

597473720f4dc69749542bfcfed4a927a43d935e - Merge branch 'next' into for-linus

Thu, 11 Jul 2019 08:24:10 +0200

Merge branch 'next' into for-linusPrepare input updates for 5.3 merge window. List of files: /linux/drivers/gpu/drm/xen/Makefile

2a267e7c41aa88215de2b542de797d03d16ecdfd - Merge tag 'v5.1' into next

Fri, 10 May 2019 20:43:46 +0200

Merge tag 'v5.1' into nextSync up with mainline to bring in the latest APIs. List of files: /linux/drivers/gpu/drm/xen/Makefile

95d002e0a34cb0f238abb39987f9980f325d8332 - Merge tag 'drm-intel-next-2019-04-04' into gvt-next

Tue, 16 Apr 2019 10:50:34 +0200

Merge tag 'drm-intel-next-2019-04-04' into gvt-nextMerge back drm-intel-next for engine name definition refinementand 54939ea0bd85 ("drm/i915: Switch to use HWS indices rather than addresses")that would need gvt fixes to depend on.Signed-off-by: Zhenyu Wang List of files: /linux/drivers/gpu/drm/xen/Makefile

82ffd0454bd9bd57780966d47bfd56d579dd4fb3 - Merge tag 'v5.0-rc5' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into fbdev-for-next

Thu, 07 Feb 2019 16:44:43 +0100

Merge tag 'v5.0-rc5' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into fbdev-for-nextLinux 5.0-rc5Sync with upstream (which now contains fbdev-v5.0-rc3 changes) toprepare a base for fbdev-v5.1 changes. List of files: /linux/drivers/gpu/drm/xen/Makefile

3eb66e91a25497065c5322b1268cbc3953642227 - Merge tag 'v4.20' into for-linus

Tue, 15 Jan 2019 00:33:23 +0100

Merge tag 'v4.20' into for-linusSync with mainline to get linux/overflow.h among other things. List of files: /linux/drivers/gpu/drm/xen/Makefile

4116941b7a703f8c770998bb3a59966608cb5bb2 - Merge tag 'v4.20' into next

Mon, 14 Jan 2019 07:35:32 +0100

Merge tag 'v4.20' into nextMerge with mainline to bring in the new APIs. List of files: /linux/drivers/gpu/drm/xen/Makefile

23d19ba06b9c5614d6457f5fed349ec8f6d4dac9 - Merge drm/drm-next into drm-misc-next

Fri, 11 Jan 2019 16:32:10 +0100

Merge drm/drm-next into drm-misc-nextdrm-next has been forwarded to 5.0-rc1, and we need it to apply the damagehelper for dirtyfb series from Noralf Trønnes.Signed-off-by: Maxime Ripard List of files: /linux/drivers/gpu/drm/xen/Makefile

49e41801b335f64610bbfd23e8f2bbaf34d46276 - Merge tag 'v5.0-rc1' into next-general

Thu, 10 Jan 2019 20:41:59 +0100

Merge tag 'v5.0-rc1' into next-generalLinux 5.0-rc1Sync to pick up LSM stacking work (which is based on -rc1). List of files: /linux/drivers/gpu/drm/xen/Makefile

3eb0930a425b086bdab38156aa4708427479a201 - Merge drm/drm-next into drm-intel-next-queued

Tue, 08 Jan 2019 09:50:22 +0100

Merge drm/drm-next into drm-intel-next-queuedGenerally catch up with 5.0-rc1, and specifically get the changes:96d4f267e40f ("Remove 'type' argument from access_ok() function")0b2c8f8b6b0c ("i915: fix missing user_access_end() in page fault exception case")594cc251fdd0 ("make 'user_access_begin()' do 'access_ok()'")Signed-off-by: Jani Nikula List of files: /linux/drivers/gpu/drm/xen/Makefile

460023a5d1d2aa0f733b6708b2fae5ea9f9dfec0 - Merge tag 'for-linus-4.21-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip

Wed, 26 Dec 2018 20:35:07 +0100

Merge tag 'for-linus-4.21-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tipPull xen updates from Juergen Gross: "Xen features and fixes: - a series to enable KVM guests to be booted by qemu via the Xen PVH boot entry for speeding up KVM guest tests - a series for a common driver to be used by Xen PV frontends (right now drm and sound) - two other fixes in Xen related code"* tag 'for-linus-4.21-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip: ALSA: xen-front: Use Xen common shared buffer implementation drm/xen-front: Use Xen common shared buffer implementation xen: Introduce shared buffer helpers for page directory... xen/pciback: Check dev_data before using it kprobes/x86/xen: blacklist non-attachable xen interrupt functions KVM: x86: Allow Qemu/KVM to use PVH entry point xen/pvh: Add memory map pointer to hvm_start_info struct xen/pvh: Move Xen code for getting mem map via hcall out of common file xen/pvh: Move Xen specific PVH VM initialization out of common file xen/pvh: Create a new file for Xen specific PVH code xen/pvh: Move PVH entry code out of Xen specific tree xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH List of files: /linux/drivers/gpu/drm/xen/Makefile

5641f19bdfc4193f1c2d5a829896c25dd5c0ec3d - drm/xen-front: Use Xen common shared buffer implementation

Fri, 30 Nov 2018 08:42:04 +0100

drm/xen-front: Use Xen common shared buffer implementationUse page directory based shared buffer implementationnow available as common code for Xen frontend drivers.Remove flushing of shared buffer on page flip as thisworkaround needs a proper fix.Signed-off-by: Oleksandr Andrushchenko Reviewed-by: Noralf Trønnes Signed-off-by: Boris Ostrovsky List of files: /linux/drivers/gpu/drm/xen/Makefile

6b16f5d12202a23d875915349cc031c07fe1b3ec - Merge tag 'v4.18-rc2' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into fbdev-for-next

Thu, 28 Jun 2018 14:07:57 +0200

Merge tag 'v4.18-rc2' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into fbdev-for-nextLinux 4.18-rc2 List of files: /linux/drivers/gpu/drm/xen/Makefile

57b54d74dd5c559bd35f2affaf11d8828aaf5733 - Merge tag 'v4.18-rc2' into next-general

Mon, 25 Jun 2018 18:20:40 +0200

Merge tag 'v4.18-rc2' into next-generalMerge to Linux 4.18-rc2 for security subsystem developers. List of files: /linux/drivers/gpu/drm/xen/Makefile

7731b8bc94e599c9a79e428f3359ff2c34b7576a - Merge branch 'linus' into x86/urgent

Fri, 22 Jun 2018 21:20:35 +0200

Merge branch 'linus' into x86/urgentRequired to queue a dependent fix. List of files: /linux/drivers/gpu/drm/xen/Makefile

135c5504a600ff9b06e321694fbcac78a9530cd4 - Merge tag 'drm-next-2018-06-06-1' of git://anongit.freedesktop.org/drm/drm

Wed, 06 Jun 2018 17:16:33 +0200

Merge tag 'drm-next-2018-06-06-1' of git://anongit.freedesktop.org/drm/drmPull drm updates from Dave Airlie: "This starts to support NVIDIA volta hardware with nouveau, and adds amdgpu support for the GPU in the Kabylake-G (the intel + radeon single package chip), along with some initial Intel icelake enabling. Summary: New Drivers: - v3d - driver for broadcom V3D V3.x+ hardware - xen-front - XEN PV display frontend core: - handle zpos normalization in the core - stop looking at legacy pointers in atomic paths - improved scheduler documentation - improved aspect ratio validation - aspect ratio support for 64:27 and 256:135 - drop unused control node code. i915: - Icelake (ICL) enabling - GuC/HuC refactoring - PSR/PSR2 enabling and fixes - DPLL management refactoring - DP MST fixes - NV12 enabling - HDCP improvements - GEM/Execlist/reset improvements - GVT improvements - stolen memory first 4k fix amdgpu: - Vega 20 support - VEGAM support (Kabylake-G) - preOS scanout buffer reservation - power management gfxoff support for raven - SR-IOV fixes - Vega10 power profiles and clock voltage control - scatter/gather display support on CZ/ST amdkfd: - GFX9 dGPU support - userptr memory mapping nouveau: - major refactoring for Volta GV100 support tda998x: - HDMI i2c CEC support etnaviv: - removed unused logging code - license text cleanups - MMU handling improvements - timeout fence fix for 50 days uptime tegra: - IOMMU support in gr2d/gr3d drivers - zpos support vc4: - syncobj support - CTM, plane alpha and async cursor support analogix_dp: - HPD and aux chan fixes sun4i: - MIPI DSI support tilcdc: - clock divider fixes for OMAP-l138 LCDK board rcar-du: - R8A77965 support - dma-buf fences fixes - hardware indexed crtc/du group handling - generic zplane property support atmel-hclcdc: - generic zplane property support mediatek: - use generic video mode function exynos: - S5PV210 FIMD variant support - IPP v2 framework - more HW overlays support"* tag 'drm-next-2018-06-06-1' of git://anongit.freedesktop.org/drm/drm: (1286 commits) drm/amdgpu: fix 32-bit build warning drm/exynos: fimc: signedness bug in fimc_setup_clocks() drm/exynos: scaler: fix static checker warning drm/amdgpu: Use dev_info() to report amdkfd is not supported for this ASIC drm/amd/display: Remove use of division operator for long longs drm/amdgpu: Update GFX info structure to match what vega20 used drm/amdgpu/pp: remove duplicate assignment drm/sched: add rcu_barrier after entity fini drm/amdgpu: move VM BOs on LRU again drm/amdgpu: consistenly use VM moved flag drm/amdgpu: kmap PDs/PTs in amdgpu_vm_update_directories drm/amdgpu: further optimize amdgpu_vm_handle_moved drm/amdgpu: cleanup amdgpu_vm_validate_pt_bos v2 drm/amdgpu: rework VM state machine lock handling v2 drm/amdgpu: Add runtime VCN PG support drm/amdgpu: Enable VCN static PG by default on RV drm/amdgpu: Add VCN static PG support on RV drm/amdgpu: Enable VCN CG by default on RV drm/amdgpu: Add static CG control for VCN on RV drm/exynos: Fix default value for zpos plane property ... List of files: /linux/drivers/gpu/drm/xen/Makefile

bba9525520b6028ecbe7486e13216e9ede8636be - Merge branch 'drm-intel-next-queued' into gvt-next

Sun, 13 May 2018 23:19:07 +0200

Merge branch 'drm-intel-next-queued' into gvt-nextSigned-off-by: Zhi Wang List of files: /linux/drivers/gpu/drm/xen/Makefile

53f071e19d566e7d0a4eada1bd8313a4cdb660a4 - Merge drm/drm-next into drm-intel-next-queued

Wed, 02 May 2018 11:20:32 +0200

Merge drm/drm-next into drm-intel-next-queuedNeed d224985a5e31 ("sched/wait, drivers/drm: Convert wait_on_atomic_t()usage to the new wait_var_event() API") in dinq to be able to fixhttps://bugs.freedesktop.org/show_bug.cgi?id=106085.Signed-off-by: Jani Nikula List of files: /linux/drivers/gpu/drm/xen/Makefile

0ab390262c4920f26f8202063a268d5fc829728e - Merge tag 'drm-misc-next-2018-04-26' of git://anongit.freedesktop.org/drm/drm-misc into drm-next

Mon, 30 Apr 2018 01:32:34 +0200

Merge tag 'drm-misc-next-2018-04-26' of git://anongit.freedesktop.org/drm/drm-misc into drm-nextdrm-misc-next for v4.18:UAPI Changes:- Add support for a generic plane alpha property to sun4i, rcar-du and atmel-hclcdc. (Maxime)Core Changes:- Stop looking at legacy plane->fb and crtc members in atomic drivers. (Ville)- mode_valid return type fixes. (Luc)- Handle zpos normalization in the core. (Peter)Driver Changes:- Implement CTM, plane alpha and generic async cursor support in vc4. (Stefan)- Various fixes for HPD and aux chan in drm_bridge/analogix_dp. (Lin, Zain, Douglas)- Add support for MIPI DSI to sun4i. (Maxime)Signed-off-by: Dave Airlie # gpg: Signature made Thu 26 Apr 2018 08:21:01 PM AEST# gpg: using RSA key FE558C72A67013C3# gpg: Can't check signature: public key not foundLink: https://patchwork.freedesktop.org/patch/msgid/b33da7eb-efc9-ae6f-6f69-b7acd6df6797@mblankhorst.nl List of files: /linux/drivers/gpu/drm/xen/Makefile

4394e96423444c1b37c8bb1ed0b1de8391dedafa - drm/xen-front: Remove CMA support

Tue, 17 Apr 2018 09:40:12 +0200

drm/xen-front: Remove CMA supportIt turns out this was only needed to paper over a bug in the CMAhelpers, which was addressed incommit 998fb1a0f478b83492220ff79583bf9ad538bdd8Author: Liviu Dudau Date: Fri Nov 10 13:33:10 2017 +0000 drm: gem_cma_helper.c: Allow importing of contiguous scatterlists with nents > 1Without this the following pipeline didn't work:domU:1. xen-front allocates a non-contig buffer2. creates grants out of itdom0:3. converts the grants into a dma-buf. Since they're non-contig, thescatter-list is huge.4. imports it into rcar-du, which requires dma-contig memory forscanout.-> On this given platform there's an IOMMU, so in theory this shouldwork. But in practice this failed, because of the huge number of sgentries, even though the IOMMU driver mapped it all into a dma-contigrange.With a guest-contig buffer allocated in step 1, this problem doesn'texist. But there's technically no reason to require guest-contigmemory for xen buffer sharing using grants.Given all that, the xen-front cma support is not needed and should beremoved.Signed-off-by: Oleksandr Andrushchenko Suggested-by: Daniel Vetter Acked-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/20180417074012.21311-1-andr2000@gmail.com List of files: /linux/drivers/gpu/drm/xen/Makefile

c575b7eeb89f94356997abd62d6d5a0590e259b7 - drm/xen-front: Add support for Xen PV display frontend

Tue, 03 Apr 2018 13:23:17 +0200

drm/xen-front: Add support for Xen PV display frontendAdd support for Xen para-virtualized frontend display driver.Accompanying backend [1] is implemented as a user-space applicationand its helper library [2], capable of running as a Weston clientor DRM master.Configuration of both backend and frontend is done viaXen guest domain configuration options [3].Driver limitations: 1. Only primary plane without additional properties is supported. 2. Only one video mode supported which resolution is configured via XenStore. 3. All CRTCs operate at fixed frequency of 60Hz.1. Implement Xen bus state machine for the frontend driver according tothe state diagram and recovery flow from display para-virtualizedprotocol: xen/interface/io/displif.h.2. Read configuration values from Xen store accordingto xen/interface/io/displif.h protocol: - read connector(s) configuration - read buffer allocation mode (backend/frontend)3. Handle Xen event channels: - create for all configured connectors and publish corresponding ring references and event channels in Xen store, so backend can connect - implement event channels interrupt handlers - create and destroy event channels with respect to Xen bus state4. Implement shared buffer handling according to thepara-virtualized display device protocol at xen/interface/io/displif.h: - handle page directories according to displif protocol: - allocate and share page directories - grant references to the required set of pages for the page directory - allocate xen balllooned pages via Xen balloon driver with alloc_xenballooned_pages/free_xenballooned_pages - grant references to the required set of pages for the shared buffer itself - implement pages map/unmap for the buffers allocated by the backend (gnttab_map_refs/gnttab_unmap_refs)5. Implement kernel modesetiing/connector handling usingDRM simple KMS helper pipeline:- implement KMS part of the driver with the help of DRM simple pipepline helper which is possible due to the fact that the para-virtualized driver only supports a single (primary) plane: - initialize connectors according to XenStore configuration - handle frame done events from the backend - create and destroy frame buffers and propagate those to the backend - propagate set/reset mode configuration to the backend on display enable/disable callbacks - send page flip request to the backend and implement logic for reporting backend IO errors on prepare fb callback- implement virtual connector handling: - support only pixel formats suitable for single plane modes - make sure the connector is always connected - support a single video mode as per para-virtualized driver configuration6. Implement GEM handling depending on driver mode of operation:depending on the requirements for the para-virtualized environment,namely requirements dictated by the accompanying DRM/(v)GPU driversrunning in both host and guest environments, number of operatingmodes of para-virtualized display driver are supported: - display buffers can be allocated by either frontend driver or backend - display buffers can be allocated to be contiguous in memory or notNote! Frontend driver itself has no dependency on contiguous memory forits operation.6.1. Buffers allocated by the frontend driver.The below modes of operation are configured at compile-time viafrontend driver's kernel configuration.6.1.1. Front driver configured to use GEM CMA helpers This use-case is useful when used with accompanying DRM/vGPU driver in guest domain which was designed to only work with contiguous buffers, e.g. DRM driver based on GEM CMA helpers: such drivers can only import contiguous PRIME buffers, thus requiring frontend driver to provide such. In order to implement this mode of operation para-virtualized frontend driver can be configured to use GEM CMA helpers.6.1.2. Front driver doesn't use GEM CMA If accompanying drivers can cope with non-contiguous memory then, to lower pressure on CMA subsystem of the kernel, driver can allocate buffers from system memory.Note! If used with accompanying DRM/(v)GPU drivers this mode of operationmay require IOMMU support on the platform, so accompanying DRM/vGPUhardware can still reach display buffer memory while importing PRIMEbuffers from the frontend driver.6.2. Buffers allocated by the backendThis mode of operation is run-time configured via guest domainconfiguration through XenStore entries.For systems which do not provide IOMMU support, but having specificrequirements for display buffers it is possible to allocate such buffersat backend side and share those with the frontend.For example, if host domain is 1:1 mapped and has DRM/GPU hardwareexpecting physically contiguous memory, this allows implementingzero-copying use-cases.Note, while using this scenario the following should be considered: a) If guest domain dies then pages/grants received from the backend cannot be claimed back b) Misbehaving guest may send too many requests to the backend exhausting its grant references and memory (consider this from security POV).Note! Configuration options 1.1 (contiguous display buffers) and 2(backend allocated buffers) are not supported at the same time.7. Handle communication with the backend: - send requests and wait for the responses according to the displif protocol - serialize access to the communication channel - time-out used for backend communication is set to 3000 ms - manage display buffers shared with the backend[1] https://github.com/xen-troops/displ_be[2] https://github.com/xen-troops/libxenbe[3] https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=docs/man/xl.cfg.pod.5.in;h=a699367779e2ae1212ff8f638eff0206ec1a1cc9;hb=refs/heads/master#l1257Signed-off-by: Oleksandr Andrushchenko Reviewed-by: Boris Ostrovsky Reviewed-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/20180403112317.28751-2-andr2000@gmail.com List of files: /linux/drivers/gpu/drm/xen/Makefile