2014-04-21 19:13:04 -04:00
|
|
|
/* -*- mode: C; c-file-style: "gnu"; indent-tabs-mode: nil; -*- */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Copyright (C) 2014 Red Hat
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License as
|
|
|
|
* published by the Free Software Foundation; either version 2 of the
|
|
|
|
* License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful, but
|
|
|
|
* WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
|
|
|
|
* 02111-1307, USA.
|
|
|
|
*
|
|
|
|
* Written by:
|
|
|
|
* Jasper St. Pierre <jstpierre@mecheye.net>
|
|
|
|
*/
|
|
|
|
|
2018-10-19 03:15:54 -04:00
|
|
|
/**
|
|
|
|
* SECTION:meta-backend-native
|
|
|
|
* @title: MetaBackendNative
|
|
|
|
* @short_description: A native (KMS/evdev) MetaBackend
|
|
|
|
*
|
|
|
|
* MetaBackendNative is an implementation of #MetaBackend that uses "native"
|
|
|
|
* technologies like DRM/KMS and libinput/evdev to perform the necessary
|
|
|
|
* functions.
|
|
|
|
*/
|
|
|
|
|
2014-04-21 19:13:04 -04:00
|
|
|
#include "config.h"
|
|
|
|
|
2018-07-10 04:36:24 -04:00
|
|
|
#include "backends/native/meta-backend-native.h"
|
|
|
|
#include "backends/native/meta-backend-native-private.h"
|
2020-11-20 17:53:46 -05:00
|
|
|
#include "backends/native/meta-input-thread.h"
|
2015-01-16 03:50:51 -05:00
|
|
|
|
2019-02-27 13:02:25 -05:00
|
|
|
#include <sched.h>
|
2018-07-10 04:36:24 -04:00
|
|
|
#include <stdlib.h>
|
2014-04-21 19:13:04 -04:00
|
|
|
|
2015-07-10 05:01:22 -04:00
|
|
|
#include "backends/meta-cursor-tracker-private.h"
|
2018-03-20 05:59:04 -04:00
|
|
|
#include "backends/meta-idle-monitor-private.h"
|
2019-11-13 21:59:25 -05:00
|
|
|
#include "backends/meta-keymap-utils.h"
|
2016-12-12 21:37:11 -05:00
|
|
|
#include "backends/meta-logical-monitor.h"
|
2016-11-30 23:59:47 -05:00
|
|
|
#include "backends/meta-monitor-manager-private.h"
|
2015-06-17 00:10:52 -04:00
|
|
|
#include "backends/meta-pointer-constraint.h"
|
2019-02-27 13:02:25 -05:00
|
|
|
#include "backends/meta-settings-private.h"
|
2018-05-02 12:53:11 -04:00
|
|
|
#include "backends/meta-stage-private.h"
|
2016-05-04 04:19:23 -04:00
|
|
|
#include "backends/native/meta-clutter-backend-native.h"
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
#include "backends/native/meta-kms.h"
|
|
|
|
#include "backends/native/meta-kms-device.h"
|
2018-07-10 04:36:24 -04:00
|
|
|
#include "backends/native/meta-launcher.h"
|
2020-12-17 16:12:41 -05:00
|
|
|
#include "backends/native/meta-monitor-manager-native.h"
|
2016-05-07 11:07:46 -04:00
|
|
|
#include "backends/native/meta-renderer-native.h"
|
2019-09-25 17:04:25 -04:00
|
|
|
#include "backends/native/meta-seat-native.h"
|
Introduce regional stage rendering
Add support for drawing a stage using multiple framebuffers each making
up one part of the stage. This works by the stage backend
(ClutterStageWindow) providing a list of views which will be for
splitting up the stage in different regions.
A view layout, for now, is a set of rectangles. The stage window (i.e.
stage "backend" will use this information when drawing a frame, using
one framebuffer for each view. The scene graph is adapted to explictly
take a view when painting the stage. It will use this view, its
assigned framebuffer and layout to offset and clip the drawing
accordingly.
This effectively removes any notion of "stage framebuffer", since each
stage now may consist of multiple framebuffers. Therefore, API
involving this has been deprecated and made no-ops; namely
clutter_stage_ensure_context(). Callers are now assumed to either
always use a framebuffer reference explicitly, or push/pop the
framebuffer of a given view where the code has not yet changed to use
the explicit-buffer-using cogl API.
Currently only the nested X11 backend supports this mode fully, and the
per view framebuffers are all offscreen. Upon frame completion, it'll
blit each view's framebuffer onto the onscreen framebuffer before
swapping.
Other backends (X11 CM and native/KMS) are adapted to manage a
full-stage view. The X11 CM backend will continue to use this method,
while the native/KMS backend will be adopted to use multiple view
drawing.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-26 23:09:24 -04:00
|
|
|
#include "backends/native/meta-stage-native.h"
|
2020-02-17 12:32:35 -05:00
|
|
|
#include "cogl/cogl.h"
|
2018-07-10 04:36:24 -04:00
|
|
|
#include "core/meta-border.h"
|
|
|
|
#include "meta/main.h"
|
2015-10-28 10:45:20 -04:00
|
|
|
|
2020-06-17 11:50:17 -04:00
|
|
|
#ifdef HAVE_REMOTE_DESKTOP
|
|
|
|
#include "backends/meta-screen-cast.h"
|
|
|
|
#endif
|
|
|
|
|
2020-03-05 15:35:57 -05:00
|
|
|
enum
|
|
|
|
{
|
|
|
|
PROP_0,
|
|
|
|
|
|
|
|
PROP_HEADLESS,
|
|
|
|
|
|
|
|
N_PROPS
|
|
|
|
};
|
|
|
|
|
|
|
|
static GParamSpec *obj_props[N_PROPS];
|
|
|
|
|
2016-11-30 05:46:20 -05:00
|
|
|
struct _MetaBackendNative
|
|
|
|
{
|
|
|
|
MetaBackend parent;
|
|
|
|
|
2014-04-21 19:47:04 -04:00
|
|
|
MetaLauncher *launcher;
|
2019-01-10 05:30:02 -05:00
|
|
|
MetaUdev *udev;
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
MetaKms *kms;
|
2019-01-11 09:35:42 -05:00
|
|
|
|
2020-03-05 15:35:57 -05:00
|
|
|
gboolean is_headless;
|
|
|
|
|
2019-11-15 19:25:52 -05:00
|
|
|
gulong udev_device_added_handler_id;
|
2014-04-21 19:47:04 -04:00
|
|
|
};
|
|
|
|
|
2017-07-24 00:31:32 -04:00
|
|
|
static GInitableIface *initable_parent_iface;
|
|
|
|
|
|
|
|
static void
|
|
|
|
initable_iface_init (GInitableIface *initable_iface);
|
|
|
|
|
|
|
|
G_DEFINE_TYPE_WITH_CODE (MetaBackendNative, meta_backend_native, META_TYPE_BACKEND,
|
|
|
|
G_IMPLEMENT_INTERFACE (G_TYPE_INITABLE,
|
|
|
|
initable_iface_init))
|
2014-04-21 19:13:04 -04:00
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
static void
|
|
|
|
disconnect_udev_device_added_handler (MetaBackendNative *native);
|
|
|
|
|
2014-09-19 11:25:22 -04:00
|
|
|
static void
|
2021-01-19 16:14:01 -05:00
|
|
|
meta_backend_native_dispose (GObject *object)
|
2014-09-19 11:25:22 -04:00
|
|
|
{
|
|
|
|
MetaBackendNative *native = META_BACKEND_NATIVE (object);
|
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
if (native->udev_device_added_handler_id)
|
2021-01-19 16:14:01 -05:00
|
|
|
{
|
|
|
|
disconnect_udev_device_added_handler (native);
|
|
|
|
native->udev_device_added_handler_id = 0;
|
|
|
|
}
|
2019-01-11 09:35:42 -05:00
|
|
|
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
g_clear_object (&native->kms);
|
2020-10-09 11:30:05 -04:00
|
|
|
g_clear_object (&native->udev);
|
2014-09-19 11:25:22 -04:00
|
|
|
|
2021-01-19 16:14:01 -05:00
|
|
|
G_OBJECT_CLASS (meta_backend_native_parent_class)->dispose (object);
|
2021-01-15 04:26:01 -05:00
|
|
|
|
|
|
|
g_clear_pointer (&native->launcher, meta_launcher_free);
|
2014-09-19 11:25:22 -04:00
|
|
|
}
|
|
|
|
|
2016-05-04 04:19:23 -04:00
|
|
|
static ClutterBackend *
|
|
|
|
meta_backend_native_create_clutter_backend (MetaBackend *backend)
|
|
|
|
{
|
|
|
|
return g_object_new (META_TYPE_CLUTTER_BACKEND_NATIVE, NULL);
|
|
|
|
}
|
|
|
|
|
2020-06-17 11:50:17 -04:00
|
|
|
#ifdef HAVE_REMOTE_DESKTOP
|
|
|
|
static void
|
|
|
|
maybe_disable_screen_cast_dma_bufs (MetaBackendNative *native)
|
|
|
|
{
|
|
|
|
MetaBackend *backend = META_BACKEND (native);
|
2020-09-14 12:23:10 -04:00
|
|
|
MetaSettings *settings = meta_backend_get_settings (backend);
|
2020-06-17 11:50:17 -04:00
|
|
|
MetaRenderer *renderer = meta_backend_get_renderer (backend);
|
|
|
|
MetaRendererNative *renderer_native = META_RENDERER_NATIVE (renderer);
|
2020-09-14 05:36:25 -04:00
|
|
|
MetaScreenCast *screen_cast = meta_backend_get_screen_cast (backend);
|
2020-06-17 11:50:17 -04:00
|
|
|
MetaGpuKms *primary_gpu;
|
|
|
|
MetaKmsDevice *kms_device;
|
|
|
|
const char *driver_name;
|
2020-09-14 05:36:25 -04:00
|
|
|
static const char *enable_dma_buf_drivers[] = {
|
|
|
|
"i915",
|
2020-06-17 11:50:17 -04:00
|
|
|
NULL,
|
|
|
|
};
|
|
|
|
|
|
|
|
primary_gpu = meta_renderer_native_get_primary_gpu (renderer_native);
|
|
|
|
kms_device = meta_gpu_kms_get_kms_device (primary_gpu);
|
|
|
|
driver_name = meta_kms_device_get_driver_name (kms_device);
|
|
|
|
|
2020-09-14 05:36:25 -04:00
|
|
|
if (g_strv_contains (enable_dma_buf_drivers, driver_name))
|
|
|
|
return;
|
2020-06-17 11:50:17 -04:00
|
|
|
|
2020-09-14 12:23:10 -04:00
|
|
|
if (meta_settings_is_experimental_feature_enabled (settings,
|
|
|
|
META_EXPERIMENTAL_FEATURE_DMA_BUF_SCREEN_SHARING))
|
|
|
|
return;
|
|
|
|
|
2020-09-14 05:36:25 -04:00
|
|
|
g_message ("Disabling DMA buffer screen sharing for driver '%s'.",
|
|
|
|
driver_name);
|
2020-06-17 11:50:17 -04:00
|
|
|
|
2020-09-14 05:36:25 -04:00
|
|
|
meta_screen_cast_disable_dma_bufs (screen_cast);
|
2020-06-17 11:50:17 -04:00
|
|
|
}
|
|
|
|
#endif /* HAVE_REMOTE_DESKTOP */
|
|
|
|
|
2020-07-16 10:41:02 -04:00
|
|
|
static void
|
|
|
|
update_viewports (MetaBackend *backend)
|
|
|
|
{
|
|
|
|
MetaMonitorManager *monitor_manager =
|
|
|
|
meta_backend_get_monitor_manager (backend);
|
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
|
|
|
MetaSeatNative *seat =
|
|
|
|
META_SEAT_NATIVE (clutter_backend_get_default_seat (clutter_backend));
|
|
|
|
MetaViewportInfo *viewports;
|
|
|
|
|
|
|
|
viewports = meta_monitor_manager_get_viewports (monitor_manager);
|
|
|
|
meta_seat_native_set_viewports (seat, viewports);
|
|
|
|
g_object_unref (viewports);
|
|
|
|
}
|
|
|
|
|
2014-04-22 12:40:51 -04:00
|
|
|
static void
|
|
|
|
meta_backend_native_post_init (MetaBackend *backend)
|
|
|
|
{
|
2019-02-27 13:02:25 -05:00
|
|
|
MetaSettings *settings = meta_backend_get_settings (backend);
|
2020-08-11 12:33:07 -04:00
|
|
|
|
2020-08-12 06:47:07 -04:00
|
|
|
META_BACKEND_CLASS (meta_backend_native_parent_class)->post_init (backend);
|
|
|
|
|
2019-02-27 13:02:25 -05:00
|
|
|
if (meta_settings_is_experimental_feature_enabled (settings,
|
|
|
|
META_EXPERIMENTAL_FEATURE_RT_SCHEDULER))
|
|
|
|
{
|
|
|
|
int retval;
|
|
|
|
struct sched_param sp = {
|
|
|
|
.sched_priority = sched_get_priority_min (SCHED_RR)
|
|
|
|
};
|
|
|
|
|
|
|
|
retval = sched_setscheduler (0, SCHED_RR | SCHED_RESET_ON_FORK, &sp);
|
|
|
|
|
|
|
|
if (retval != 0)
|
|
|
|
g_warning ("Failed to set RT scheduler: %m");
|
|
|
|
}
|
2020-04-27 07:30:26 -04:00
|
|
|
|
2020-06-17 11:50:17 -04:00
|
|
|
#ifdef HAVE_REMOTE_DESKTOP
|
|
|
|
maybe_disable_screen_cast_dma_bufs (META_BACKEND_NATIVE (backend));
|
|
|
|
#endif
|
|
|
|
|
2020-07-16 10:41:02 -04:00
|
|
|
update_viewports (backend);
|
|
|
|
|
2020-04-27 07:30:26 -04:00
|
|
|
#ifdef HAVE_WAYLAND
|
|
|
|
meta_backend_init_wayland (backend);
|
|
|
|
#endif
|
2014-04-22 12:40:51 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
static MetaMonitorManager *
|
2017-07-06 04:00:56 -04:00
|
|
|
meta_backend_native_create_monitor_manager (MetaBackend *backend,
|
|
|
|
GError **error)
|
2014-04-22 12:40:51 -04:00
|
|
|
{
|
2020-07-16 10:41:02 -04:00
|
|
|
MetaMonitorManager *manager;
|
|
|
|
|
2020-12-17 16:12:41 -05:00
|
|
|
manager = g_initable_new (META_TYPE_MONITOR_MANAGER_NATIVE, NULL, error,
|
2020-07-16 10:41:02 -04:00
|
|
|
"backend", backend,
|
|
|
|
NULL);
|
2021-01-18 16:35:35 -05:00
|
|
|
if (!manager)
|
|
|
|
return NULL;
|
|
|
|
|
2020-07-16 10:41:02 -04:00
|
|
|
g_signal_connect_swapped (manager, "monitors-changed-internal",
|
|
|
|
G_CALLBACK (update_viewports), backend);
|
|
|
|
|
|
|
|
return manager;
|
2014-04-22 12:40:51 -04:00
|
|
|
}
|
|
|
|
|
2014-04-22 15:15:11 -04:00
|
|
|
static MetaCursorRenderer *
|
2020-07-10 17:28:50 -04:00
|
|
|
meta_backend_native_get_cursor_renderer (MetaBackend *backend,
|
|
|
|
ClutterInputDevice *device)
|
2014-04-22 15:15:11 -04:00
|
|
|
{
|
2020-07-10 17:28:50 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
|
|
|
MetaSeatNative *seat_native =
|
|
|
|
META_SEAT_NATIVE (clutter_backend_get_default_seat (clutter_backend));
|
|
|
|
|
|
|
|
return meta_seat_native_maybe_ensure_cursor_renderer (seat_native, device);
|
2014-04-22 15:15:11 -04:00
|
|
|
}
|
|
|
|
|
2016-05-07 11:07:46 -04:00
|
|
|
static MetaRenderer *
|
2017-07-05 06:01:47 -04:00
|
|
|
meta_backend_native_create_renderer (MetaBackend *backend,
|
|
|
|
GError **error)
|
2016-05-07 11:07:46 -04:00
|
|
|
{
|
2019-01-11 09:35:42 -05:00
|
|
|
MetaBackendNative *native = META_BACKEND_NATIVE (backend);
|
2016-05-09 09:22:01 -04:00
|
|
|
MetaRendererNative *renderer_native;
|
2016-05-07 11:09:59 -04:00
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
renderer_native = meta_renderer_native_new (native, error);
|
2016-05-09 09:22:01 -04:00
|
|
|
if (!renderer_native)
|
2017-07-05 06:01:47 -04:00
|
|
|
return NULL;
|
2016-05-09 09:22:01 -04:00
|
|
|
|
|
|
|
return META_RENDERER (renderer_native);
|
2016-05-07 11:07:46 -04:00
|
|
|
}
|
|
|
|
|
2017-04-10 05:31:50 -04:00
|
|
|
static MetaInputSettings *
|
2020-11-19 10:00:12 -05:00
|
|
|
meta_backend_native_get_input_settings (MetaBackend *backend)
|
2017-04-10 05:31:50 -04:00
|
|
|
{
|
2020-11-21 06:52:45 -05:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
|
|
|
MetaSeatNative *seat_native =
|
|
|
|
META_SEAT_NATIVE (clutter_backend_get_default_seat (clutter_backend));
|
2020-08-04 08:17:39 -04:00
|
|
|
|
2020-11-21 06:52:45 -05:00
|
|
|
return meta_seat_impl_get_input_settings (seat_native->impl);
|
2017-04-10 05:31:50 -04:00
|
|
|
}
|
|
|
|
|
2016-11-30 23:59:47 -05:00
|
|
|
static MetaLogicalMonitor *
|
|
|
|
meta_backend_native_get_current_logical_monitor (MetaBackend *backend)
|
|
|
|
{
|
|
|
|
MetaCursorTracker *cursor_tracker = meta_backend_get_cursor_tracker (backend);
|
|
|
|
MetaMonitorManager *monitor_manager =
|
|
|
|
meta_backend_get_monitor_manager (backend);
|
2020-07-13 06:06:12 -04:00
|
|
|
graphene_point_t point;
|
2016-11-30 23:59:47 -05:00
|
|
|
|
2020-07-13 06:06:12 -04:00
|
|
|
meta_cursor_tracker_get_pointer (cursor_tracker, &point, NULL);
|
|
|
|
return meta_monitor_manager_get_logical_monitor_at (monitor_manager,
|
|
|
|
point.x, point.y);
|
2016-11-30 23:59:47 -05:00
|
|
|
}
|
|
|
|
|
2014-08-04 10:47:35 -04:00
|
|
|
static void
|
|
|
|
meta_backend_native_set_keymap (MetaBackend *backend,
|
|
|
|
const char *layouts,
|
|
|
|
const char *variants,
|
|
|
|
const char *options)
|
|
|
|
{
|
2020-05-26 16:11:06 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
2019-10-04 09:44:27 -04:00
|
|
|
ClutterSeat *seat;
|
2014-08-04 10:47:35 -04:00
|
|
|
|
2020-05-26 16:11:06 -04:00
|
|
|
seat = clutter_backend_get_default_seat (clutter_backend);
|
2020-08-12 06:47:07 -04:00
|
|
|
meta_seat_native_set_keyboard_map (META_SEAT_NATIVE (seat),
|
|
|
|
layouts, variants, options);
|
2014-08-04 10:47:35 -04:00
|
|
|
|
2017-03-29 02:30:10 -04:00
|
|
|
meta_backend_notify_keymap_changed (backend);
|
2014-08-04 10:47:35 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
static struct xkb_keymap *
|
|
|
|
meta_backend_native_get_keymap (MetaBackend *backend)
|
|
|
|
{
|
2020-05-26 16:11:06 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
2019-10-04 09:44:27 -04:00
|
|
|
ClutterSeat *seat;
|
|
|
|
|
2020-05-26 16:11:06 -04:00
|
|
|
seat = clutter_backend_get_default_seat (clutter_backend);
|
2019-10-04 09:44:27 -04:00
|
|
|
return meta_seat_native_get_keyboard_map (META_SEAT_NATIVE (seat));
|
2014-08-04 10:47:35 -04:00
|
|
|
}
|
|
|
|
|
2017-08-17 05:01:50 -04:00
|
|
|
static xkb_layout_index_t
|
|
|
|
meta_backend_native_get_keymap_layout_group (MetaBackend *backend)
|
|
|
|
{
|
2020-05-26 16:11:06 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
2019-10-04 09:44:27 -04:00
|
|
|
ClutterSeat *seat;
|
2017-08-17 05:01:50 -04:00
|
|
|
|
2020-05-26 16:11:06 -04:00
|
|
|
seat = clutter_backend_get_default_seat (clutter_backend);
|
2019-10-04 09:44:27 -04:00
|
|
|
return meta_seat_native_get_keyboard_layout_index (META_SEAT_NATIVE (seat));
|
2017-08-17 05:01:50 -04:00
|
|
|
}
|
|
|
|
|
2014-08-04 10:47:35 -04:00
|
|
|
static void
|
|
|
|
meta_backend_native_lock_layout_group (MetaBackend *backend,
|
|
|
|
guint idx)
|
|
|
|
{
|
2020-05-26 16:11:06 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
2017-08-21 02:37:52 -04:00
|
|
|
xkb_layout_index_t old_idx;
|
2019-10-04 09:44:27 -04:00
|
|
|
ClutterSeat *seat;
|
2017-08-21 02:37:52 -04:00
|
|
|
|
|
|
|
old_idx = meta_backend_native_get_keymap_layout_group (backend);
|
|
|
|
if (old_idx == idx)
|
|
|
|
return;
|
2017-03-29 02:30:10 -04:00
|
|
|
|
2020-05-26 16:11:06 -04:00
|
|
|
seat = clutter_backend_get_default_seat (clutter_backend);
|
2019-10-04 09:44:27 -04:00
|
|
|
meta_seat_native_set_keyboard_layout_index (META_SEAT_NATIVE (seat), idx);
|
2017-03-29 02:30:10 -04:00
|
|
|
meta_backend_notify_keymap_layout_group_changed (backend, idx);
|
2014-08-04 10:47:35 -04:00
|
|
|
}
|
|
|
|
|
2021-01-18 16:38:21 -05:00
|
|
|
const char *
|
|
|
|
meta_backend_native_get_seat_id (MetaBackendNative *backend_native)
|
|
|
|
{
|
|
|
|
return meta_launcher_get_seat_id (backend_native->launcher);
|
|
|
|
}
|
|
|
|
|
2020-07-08 12:17:13 -04:00
|
|
|
static void
|
|
|
|
meta_backend_native_set_pointer_constraint (MetaBackend *backend,
|
|
|
|
MetaPointerConstraint *constraint)
|
|
|
|
{
|
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
|
|
|
ClutterSeat *seat = clutter_backend_get_default_seat (clutter_backend);
|
|
|
|
MetaPointerConstraintImpl *constraint_impl = NULL;
|
|
|
|
cairo_region_t *region;
|
|
|
|
|
|
|
|
if (constraint)
|
|
|
|
{
|
|
|
|
region = meta_pointer_constraint_get_region (constraint);
|
|
|
|
constraint_impl = meta_pointer_constraint_impl_native_new (constraint,
|
|
|
|
region);
|
|
|
|
}
|
|
|
|
|
|
|
|
meta_seat_native_set_pointer_constraint (META_SEAT_NATIVE (seat),
|
|
|
|
constraint_impl);
|
|
|
|
}
|
|
|
|
|
2016-05-20 03:36:05 -04:00
|
|
|
static void
|
|
|
|
meta_backend_native_update_screen_size (MetaBackend *backend,
|
|
|
|
int width, int height)
|
|
|
|
{
|
Introduce regional stage rendering
Add support for drawing a stage using multiple framebuffers each making
up one part of the stage. This works by the stage backend
(ClutterStageWindow) providing a list of views which will be for
splitting up the stage in different regions.
A view layout, for now, is a set of rectangles. The stage window (i.e.
stage "backend" will use this information when drawing a frame, using
one framebuffer for each view. The scene graph is adapted to explictly
take a view when painting the stage. It will use this view, its
assigned framebuffer and layout to offset and clip the drawing
accordingly.
This effectively removes any notion of "stage framebuffer", since each
stage now may consist of multiple framebuffers. Therefore, API
involving this has been deprecated and made no-ops; namely
clutter_stage_ensure_context(). Callers are now assumed to either
always use a framebuffer reference explicitly, or push/pop the
framebuffer of a given view where the code has not yet changed to use
the explicit-buffer-using cogl API.
Currently only the nested X11 backend supports this mode fully, and the
per view framebuffers are all offscreen. Upon frame completion, it'll
blit each view's framebuffer onto the onscreen framebuffer before
swapping.
Other backends (X11 CM and native/KMS) are adapted to manage a
full-stage view. The X11 CM backend will continue to use this method,
while the native/KMS backend will be adopted to use multiple view
drawing.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-26 23:09:24 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
|
|
|
MetaStageNative *stage_native;
|
2016-05-20 03:36:05 -04:00
|
|
|
ClutterActor *stage = meta_backend_get_stage (backend);
|
|
|
|
|
Introduce regional stage rendering
Add support for drawing a stage using multiple framebuffers each making
up one part of the stage. This works by the stage backend
(ClutterStageWindow) providing a list of views which will be for
splitting up the stage in different regions.
A view layout, for now, is a set of rectangles. The stage window (i.e.
stage "backend" will use this information when drawing a frame, using
one framebuffer for each view. The scene graph is adapted to explictly
take a view when painting the stage. It will use this view, its
assigned framebuffer and layout to offset and clip the drawing
accordingly.
This effectively removes any notion of "stage framebuffer", since each
stage now may consist of multiple framebuffers. Therefore, API
involving this has been deprecated and made no-ops; namely
clutter_stage_ensure_context(). Callers are now assumed to either
always use a framebuffer reference explicitly, or push/pop the
framebuffer of a given view where the code has not yet changed to use
the explicit-buffer-using cogl API.
Currently only the nested X11 backend supports this mode fully, and the
per view framebuffers are all offscreen. Upon frame completion, it'll
blit each view's framebuffer onto the onscreen framebuffer before
swapping.
Other backends (X11 CM and native/KMS) are adapted to manage a
full-stage view. The X11 CM backend will continue to use this method,
while the native/KMS backend will be adopted to use multiple view
drawing.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-26 23:09:24 -04:00
|
|
|
stage_native = meta_clutter_backend_native_get_stage_native (clutter_backend);
|
2017-07-24 00:31:32 -04:00
|
|
|
meta_stage_native_rebuild_views (stage_native);
|
Introduce regional stage rendering
Add support for drawing a stage using multiple framebuffers each making
up one part of the stage. This works by the stage backend
(ClutterStageWindow) providing a list of views which will be for
splitting up the stage in different regions.
A view layout, for now, is a set of rectangles. The stage window (i.e.
stage "backend" will use this information when drawing a frame, using
one framebuffer for each view. The scene graph is adapted to explictly
take a view when painting the stage. It will use this view, its
assigned framebuffer and layout to offset and clip the drawing
accordingly.
This effectively removes any notion of "stage framebuffer", since each
stage now may consist of multiple framebuffers. Therefore, API
involving this has been deprecated and made no-ops; namely
clutter_stage_ensure_context(). Callers are now assumed to either
always use a framebuffer reference explicitly, or push/pop the
framebuffer of a given view where the code has not yet changed to use
the explicit-buffer-using cogl API.
Currently only the nested X11 backend supports this mode fully, and the
per view framebuffers are all offscreen. Upon frame completion, it'll
blit each view's framebuffer onto the onscreen framebuffer before
swapping.
Other backends (X11 CM and native/KMS) are adapted to manage a
full-stage view. The X11 CM backend will continue to use this method,
while the native/KMS backend will be adopted to use multiple view
drawing.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-26 23:09:24 -04:00
|
|
|
|
2016-05-20 03:36:05 -04:00
|
|
|
clutter_actor_set_size (stage, width, height);
|
|
|
|
}
|
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
static MetaGpuKms *
|
|
|
|
create_gpu_from_udev_device (MetaBackendNative *native,
|
|
|
|
GUdevDevice *device,
|
|
|
|
GError **error)
|
|
|
|
{
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
MetaKmsDeviceFlag flags = META_KMS_DEVICE_FLAG_NONE;
|
2019-01-11 09:35:42 -05:00
|
|
|
const char *device_path;
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
MetaKmsDevice *kms_device;
|
2019-01-11 09:35:42 -05:00
|
|
|
|
|
|
|
if (meta_is_udev_device_platform_device (device))
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
flags |= META_KMS_DEVICE_FLAG_PLATFORM_DEVICE;
|
2019-01-11 09:35:42 -05:00
|
|
|
|
|
|
|
if (meta_is_udev_device_boot_vga (device))
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
flags |= META_KMS_DEVICE_FLAG_BOOT_VGA;
|
2019-01-11 09:35:42 -05:00
|
|
|
|
2020-09-14 14:36:17 -04:00
|
|
|
if (meta_is_udev_device_requires_modifiers (device))
|
|
|
|
flags |= META_KMS_DEVICE_FLAG_REQUIRES_MODIFIERS;
|
|
|
|
|
2020-11-14 04:41:23 -05:00
|
|
|
if (meta_is_udev_device_preferred_primary (device))
|
|
|
|
flags |= META_KMS_DEVICE_FLAG_PREFERRED_PRIMARY;
|
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
device_path = g_udev_device_get_device_file (device);
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
|
|
|
|
kms_device = meta_kms_create_device (native->kms, device_path, flags,
|
|
|
|
error);
|
|
|
|
if (!kms_device)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
return meta_gpu_kms_new (native, kms_device, error);
|
2019-01-11 09:35:42 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
on_udev_device_added (MetaUdev *udev,
|
|
|
|
GUdevDevice *device,
|
|
|
|
MetaBackendNative *native)
|
|
|
|
{
|
|
|
|
MetaBackend *backend = META_BACKEND (native);
|
|
|
|
g_autoptr (GError) error = NULL;
|
|
|
|
const char *device_path;
|
|
|
|
MetaGpuKms *new_gpu_kms;
|
|
|
|
GList *gpus, *l;
|
|
|
|
|
|
|
|
if (!meta_udev_is_drm_device (udev, device))
|
|
|
|
return;
|
|
|
|
|
|
|
|
device_path = g_udev_device_get_device_file (device);
|
|
|
|
|
2020-07-28 04:11:07 -04:00
|
|
|
gpus = meta_backend_get_gpus (backend);
|
2019-01-11 09:35:42 -05:00
|
|
|
for (l = gpus; l; l = l->next)
|
|
|
|
{
|
|
|
|
MetaGpuKms *gpu_kms = l->data;
|
|
|
|
|
|
|
|
if (!g_strcmp0 (device_path, meta_gpu_kms_get_file_path (gpu_kms)))
|
|
|
|
{
|
|
|
|
g_warning ("Failed to hotplug secondary gpu '%s': %s",
|
|
|
|
device_path, "device already present");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
new_gpu_kms = create_gpu_from_udev_device (native, device, &error);
|
|
|
|
if (!new_gpu_kms)
|
|
|
|
{
|
|
|
|
g_warning ("Failed to hotplug secondary gpu '%s': %s",
|
|
|
|
device_path, error->message);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
meta_backend_add_gpu (backend, META_GPU (new_gpu_kms));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
connect_udev_device_added_handler (MetaBackendNative *native)
|
|
|
|
{
|
|
|
|
native->udev_device_added_handler_id =
|
|
|
|
g_signal_connect (native->udev, "device-added",
|
|
|
|
G_CALLBACK (on_udev_device_added), native);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
disconnect_udev_device_added_handler (MetaBackendNative *native)
|
|
|
|
{
|
2019-11-15 19:25:52 -05:00
|
|
|
g_clear_signal_handler (&native->udev_device_added_handler_id, native->udev);
|
2019-01-11 09:35:42 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
static gboolean
|
|
|
|
init_gpus (MetaBackendNative *native,
|
|
|
|
GError **error)
|
|
|
|
{
|
|
|
|
MetaBackend *backend = META_BACKEND (native);
|
|
|
|
MetaUdev *udev = meta_backend_native_get_udev (native);
|
|
|
|
GList *devices;
|
|
|
|
GList *l;
|
|
|
|
|
|
|
|
devices = meta_udev_list_drm_devices (udev, error);
|
|
|
|
if (!devices)
|
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
for (l = devices; l; l = l->next)
|
|
|
|
{
|
|
|
|
GUdevDevice *device = l->data;
|
|
|
|
MetaGpuKms *gpu_kms;
|
|
|
|
GError *local_error = NULL;
|
|
|
|
|
|
|
|
gpu_kms = create_gpu_from_udev_device (native, device, &local_error);
|
|
|
|
|
|
|
|
if (!gpu_kms)
|
|
|
|
{
|
|
|
|
g_warning ("Failed to open gpu '%s': %s",
|
|
|
|
g_udev_device_get_device_file (device),
|
|
|
|
local_error->message);
|
|
|
|
g_clear_error (&local_error);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
meta_backend_add_gpu (backend, META_GPU (gpu_kms));
|
|
|
|
}
|
|
|
|
|
|
|
|
g_list_free_full (devices, g_object_unref);
|
|
|
|
|
|
|
|
if (g_list_length (meta_backend_get_gpus (backend)) == 0)
|
|
|
|
{
|
|
|
|
g_set_error (error, G_IO_ERROR, G_IO_ERROR_NOT_FOUND,
|
|
|
|
"No GPUs found");
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
connect_udev_device_added_handler (native);
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
2017-07-24 00:31:32 -04:00
|
|
|
static gboolean
|
|
|
|
meta_backend_native_initable_init (GInitable *initable,
|
|
|
|
GCancellable *cancellable,
|
|
|
|
GError **error)
|
|
|
|
{
|
2019-01-10 05:30:02 -05:00
|
|
|
MetaBackendNative *native = META_BACKEND_NATIVE (initable);
|
|
|
|
|
2017-07-24 00:31:32 -04:00
|
|
|
if (!meta_is_stage_views_enabled ())
|
|
|
|
{
|
|
|
|
g_set_error (error, G_IO_ERROR, G_IO_ERROR_FAILED,
|
|
|
|
"The native backend requires stage views");
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|
2019-01-10 05:54:07 -05:00
|
|
|
native->launcher = meta_launcher_new (error);
|
|
|
|
if (!native->launcher)
|
|
|
|
return FALSE;
|
|
|
|
|
2020-04-27 07:30:26 -04:00
|
|
|
#ifdef HAVE_WAYLAND
|
|
|
|
meta_backend_init_wayland_display (META_BACKEND (native));
|
|
|
|
#endif
|
|
|
|
|
2019-01-10 12:07:12 -05:00
|
|
|
native->udev = meta_udev_new (native);
|
2019-01-10 05:30:02 -05:00
|
|
|
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
native->kms = meta_kms_new (META_BACKEND (native), error);
|
|
|
|
if (!native->kms)
|
|
|
|
return FALSE;
|
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
if (!init_gpus (native, error))
|
|
|
|
return FALSE;
|
|
|
|
|
2017-07-24 00:31:32 -04:00
|
|
|
return initable_parent_iface->init (initable, cancellable, error);
|
|
|
|
}
|
|
|
|
|
2020-03-05 15:35:57 -05:00
|
|
|
static void
|
|
|
|
meta_backend_native_set_property (GObject *object,
|
|
|
|
guint prop_id,
|
|
|
|
const GValue *value,
|
|
|
|
GParamSpec *pspec)
|
|
|
|
{
|
|
|
|
MetaBackendNative *backend_native = META_BACKEND_NATIVE (object);
|
|
|
|
|
|
|
|
switch (prop_id)
|
|
|
|
{
|
|
|
|
case PROP_HEADLESS:
|
|
|
|
backend_native->is_headless = g_value_get_boolean (value);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-07-24 00:31:32 -04:00
|
|
|
static void
|
|
|
|
initable_iface_init (GInitableIface *initable_iface)
|
|
|
|
{
|
|
|
|
initable_parent_iface = g_type_interface_peek_parent (initable_iface);
|
|
|
|
|
|
|
|
initable_iface->init = meta_backend_native_initable_init;
|
|
|
|
}
|
|
|
|
|
2014-04-22 12:40:51 -04:00
|
|
|
static void
|
|
|
|
meta_backend_native_class_init (MetaBackendNativeClass *klass)
|
|
|
|
{
|
|
|
|
MetaBackendClass *backend_class = META_BACKEND_CLASS (klass);
|
2014-09-19 11:25:22 -04:00
|
|
|
GObjectClass *object_class = G_OBJECT_CLASS (klass);
|
|
|
|
|
2020-03-05 15:35:57 -05:00
|
|
|
object_class->set_property = meta_backend_native_set_property;
|
2021-01-19 16:14:01 -05:00
|
|
|
object_class->dispose = meta_backend_native_dispose;
|
2014-04-22 12:40:51 -04:00
|
|
|
|
2016-05-04 04:19:23 -04:00
|
|
|
backend_class->create_clutter_backend = meta_backend_native_create_clutter_backend;
|
|
|
|
|
2014-04-22 12:40:51 -04:00
|
|
|
backend_class->post_init = meta_backend_native_post_init;
|
2016-05-04 04:19:23 -04:00
|
|
|
|
2014-04-22 12:40:51 -04:00
|
|
|
backend_class->create_monitor_manager = meta_backend_native_create_monitor_manager;
|
2020-07-10 17:28:50 -04:00
|
|
|
backend_class->get_cursor_renderer = meta_backend_native_get_cursor_renderer;
|
2016-05-07 11:07:46 -04:00
|
|
|
backend_class->create_renderer = meta_backend_native_create_renderer;
|
2020-11-19 10:00:12 -05:00
|
|
|
backend_class->get_input_settings = meta_backend_native_get_input_settings;
|
2014-05-27 14:21:54 -04:00
|
|
|
|
2016-11-30 23:59:47 -05:00
|
|
|
backend_class->get_current_logical_monitor = meta_backend_native_get_current_logical_monitor;
|
|
|
|
|
2014-08-04 10:47:35 -04:00
|
|
|
backend_class->set_keymap = meta_backend_native_set_keymap;
|
|
|
|
backend_class->get_keymap = meta_backend_native_get_keymap;
|
2017-08-17 05:01:50 -04:00
|
|
|
backend_class->get_keymap_layout_group = meta_backend_native_get_keymap_layout_group;
|
2014-08-04 10:47:35 -04:00
|
|
|
backend_class->lock_layout_group = meta_backend_native_lock_layout_group;
|
2016-05-20 03:36:05 -04:00
|
|
|
backend_class->update_screen_size = meta_backend_native_update_screen_size;
|
2020-07-08 12:17:13 -04:00
|
|
|
|
|
|
|
backend_class->set_pointer_constraint = meta_backend_native_set_pointer_constraint;
|
2020-03-05 15:35:57 -05:00
|
|
|
|
|
|
|
obj_props[PROP_HEADLESS] =
|
|
|
|
g_param_spec_boolean ("headless",
|
|
|
|
"headless",
|
|
|
|
"Headless",
|
|
|
|
FALSE,
|
|
|
|
G_PARAM_WRITABLE |
|
|
|
|
G_PARAM_CONSTRUCT_ONLY |
|
|
|
|
G_PARAM_STATIC_STRINGS);
|
|
|
|
g_object_class_install_properties (object_class, N_PROPS, obj_props);
|
2014-04-22 12:40:51 -04:00
|
|
|
}
|
|
|
|
|
2014-04-21 19:13:04 -04:00
|
|
|
static void
|
|
|
|
meta_backend_native_init (MetaBackendNative *native)
|
|
|
|
{
|
2014-04-21 19:47:04 -04:00
|
|
|
}
|
|
|
|
|
2017-07-06 04:00:56 -04:00
|
|
|
MetaLauncher *
|
|
|
|
meta_backend_native_get_launcher (MetaBackendNative *native)
|
|
|
|
{
|
2018-09-06 08:14:59 -04:00
|
|
|
return native->launcher;
|
2017-07-06 04:00:56 -04:00
|
|
|
}
|
|
|
|
|
2019-01-10 05:30:02 -05:00
|
|
|
MetaUdev *
|
|
|
|
meta_backend_native_get_udev (MetaBackendNative *native)
|
|
|
|
{
|
|
|
|
return native->udev;
|
|
|
|
}
|
|
|
|
|
backends/native: Add basic KMS abstraction building blocks
The intention with KMS abstraction is to hide away accessing the drm
functions behind an API that allows us to have different kind of KMS
implementations, including legacy non-atomic and atomic. The intention
is also that the code interacting with the drm device should be able to
be run in a different thread than the main thread. This means that we
need to make sure that all drm*() API usage must only occur from within
tasks that eventually can be run in the dedicated thread.
The idea here is that MetaKms provides a outward facing API other places
of mutter can use (e.g. MetaGpuKms and friends), while MetaKmsImpl is
an internal implementation that only gets interacted with via "tasks"
posted via the MetaKms object. These tasks will in the future
potentially be run on the dedicated KMS thread. Initially, we don't
create any new threads.
Likewise, MetaKmsDevice is a outward facing representation of a KMS
device, while MetaKmsImplDevice is the corresponding implementation,
which only runs from within the MetaKmsImpl tasks.
This commit only moves opening and closing the device to this new API,
while leaking the fd outside of the impl enclosure, effectively making
the isolation for drm*() calls pointless. This, however, is necessary to
allow gradual porting of drm interaction, and eventually the file
descriptor in MetaGpuKms will be removed. For now, it's harmless, since
everything still run in the main thread.
https://gitlab.gnome.org/GNOME/mutter/issues/548
https://gitlab.gnome.org/GNOME/mutter/merge_requests/525
2019-01-29 04:24:44 -05:00
|
|
|
MetaKms *
|
|
|
|
meta_backend_native_get_kms (MetaBackendNative *native)
|
|
|
|
{
|
|
|
|
return native->kms;
|
|
|
|
}
|
|
|
|
|
2014-04-21 19:47:04 -04:00
|
|
|
gboolean
|
|
|
|
meta_activate_vt (int vt, GError **error)
|
|
|
|
{
|
|
|
|
MetaBackend *backend = meta_get_backend ();
|
|
|
|
MetaBackendNative *native = META_BACKEND_NATIVE (backend);
|
2017-07-06 04:00:56 -04:00
|
|
|
MetaLauncher *launcher = meta_backend_native_get_launcher (native);
|
2014-04-21 19:47:04 -04:00
|
|
|
|
2017-07-06 04:00:56 -04:00
|
|
|
return meta_launcher_activate_vt (launcher, vt, error);
|
2014-04-21 19:47:04 -04:00
|
|
|
}
|
|
|
|
|
2017-03-10 00:55:33 -05:00
|
|
|
void
|
|
|
|
meta_backend_native_pause (MetaBackendNative *native)
|
|
|
|
{
|
2017-03-10 03:29:11 -05:00
|
|
|
MetaBackend *backend = META_BACKEND (native);
|
|
|
|
MetaMonitorManager *monitor_manager =
|
|
|
|
meta_backend_get_monitor_manager (backend);
|
2020-12-17 16:12:41 -05:00
|
|
|
MetaMonitorManagerNative *monitor_manager_native =
|
|
|
|
META_MONITOR_MANAGER_NATIVE (monitor_manager);
|
2020-05-26 16:11:06 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
2019-09-25 17:04:25 -04:00
|
|
|
MetaSeatNative *seat =
|
|
|
|
META_SEAT_NATIVE (clutter_backend_get_default_seat (clutter_backend));
|
clutter: Paint views with individual frame clocks
Replace the default master clock with multiple frame clocks, each
driving its own stage view. As each stage view represents one CRTC, this
means we draw each CRTC with its own designated frame clock,
disconnected from all the others.
For example this means we when using the native backend will never need
to wait for one monitor to vsync before painting another, so e.g. having
a 144 Hz monitor next to a 60 Hz monitor, things including both Wayland
and X11 applications and shell UI will be able to render at the
corresponding monitor refresh rate.
This also changes a warning about missed frames when sending
_NETWM_FRAME_TIMINGS messages to a debug log entry, as it's expected
that we'll start missing frames e.g. when a X11 window (via Xwayland) is
exclusively within a stage view that was not painted, while another one
was, still increasing the global frame clock.
Addititonally, this also requires the X11 window actor to schedule
timeouts for _NET_WM_FRAME_DRAWN/_NET_WM_FRAME_TIMINGS event emitting,
if the actor wasn't on any stage views, as now we'll only get the frame
callbacks on actors when they actually were painted, while in the past,
we'd invoke that vfunc when anything was painted.
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/903
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1285
2020-05-29 18:27:56 -04:00
|
|
|
MetaRenderer *renderer = meta_backend_get_renderer (backend);
|
2017-03-10 03:29:11 -05:00
|
|
|
|
2019-08-27 06:11:07 -04:00
|
|
|
COGL_TRACE_BEGIN_SCOPED (MetaBackendNativePause,
|
|
|
|
"Backend (pause)");
|
|
|
|
|
2019-09-25 17:04:25 -04:00
|
|
|
meta_seat_native_release_devices (seat);
|
clutter: Paint views with individual frame clocks
Replace the default master clock with multiple frame clocks, each
driving its own stage view. As each stage view represents one CRTC, this
means we draw each CRTC with its own designated frame clock,
disconnected from all the others.
For example this means we when using the native backend will never need
to wait for one monitor to vsync before painting another, so e.g. having
a 144 Hz monitor next to a 60 Hz monitor, things including both Wayland
and X11 applications and shell UI will be able to render at the
corresponding monitor refresh rate.
This also changes a warning about missed frames when sending
_NETWM_FRAME_TIMINGS messages to a debug log entry, as it's expected
that we'll start missing frames e.g. when a X11 window (via Xwayland) is
exclusively within a stage view that was not painted, while another one
was, still increasing the global frame clock.
Addititonally, this also requires the X11 window actor to schedule
timeouts for _NET_WM_FRAME_DRAWN/_NET_WM_FRAME_TIMINGS event emitting,
if the actor wasn't on any stage views, as now we'll only get the frame
callbacks on actors when they actually were painted, while in the past,
we'd invoke that vfunc when anything was painted.
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/903
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1285
2020-05-29 18:27:56 -04:00
|
|
|
meta_renderer_pause (renderer);
|
2017-03-10 03:29:11 -05:00
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
disconnect_udev_device_added_handler (native);
|
|
|
|
|
2020-12-17 16:12:41 -05:00
|
|
|
meta_monitor_manager_native_pause (monitor_manager_native);
|
2017-03-10 00:55:33 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
void meta_backend_native_resume (MetaBackendNative *native)
|
|
|
|
{
|
|
|
|
MetaBackend *backend = META_BACKEND (native);
|
2018-07-12 09:01:55 -04:00
|
|
|
ClutterStage *stage = CLUTTER_STAGE (meta_backend_get_stage (backend));
|
2017-03-10 03:29:11 -05:00
|
|
|
MetaMonitorManager *monitor_manager =
|
|
|
|
meta_backend_get_monitor_manager (backend);
|
2020-12-17 16:12:41 -05:00
|
|
|
MetaMonitorManagerNative *monitor_manager_native =
|
|
|
|
META_MONITOR_MANAGER_NATIVE (monitor_manager);
|
2017-03-10 00:55:33 -05:00
|
|
|
MetaIdleMonitor *idle_monitor;
|
2020-05-26 16:11:06 -04:00
|
|
|
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
|
2019-09-25 17:04:25 -04:00
|
|
|
MetaSeatNative *seat =
|
|
|
|
META_SEAT_NATIVE (clutter_backend_get_default_seat (clutter_backend));
|
clutter: Paint views with individual frame clocks
Replace the default master clock with multiple frame clocks, each
driving its own stage view. As each stage view represents one CRTC, this
means we draw each CRTC with its own designated frame clock,
disconnected from all the others.
For example this means we when using the native backend will never need
to wait for one monitor to vsync before painting another, so e.g. having
a 144 Hz monitor next to a 60 Hz monitor, things including both Wayland
and X11 applications and shell UI will be able to render at the
corresponding monitor refresh rate.
This also changes a warning about missed frames when sending
_NETWM_FRAME_TIMINGS messages to a debug log entry, as it's expected
that we'll start missing frames e.g. when a X11 window (via Xwayland) is
exclusively within a stage view that was not painted, while another one
was, still increasing the global frame clock.
Addititonally, this also requires the X11 window actor to schedule
timeouts for _NET_WM_FRAME_DRAWN/_NET_WM_FRAME_TIMINGS event emitting,
if the actor wasn't on any stage views, as now we'll only get the frame
callbacks on actors when they actually were painted, while in the past,
we'd invoke that vfunc when anything was painted.
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/903
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1285
2020-05-29 18:27:56 -04:00
|
|
|
MetaRenderer *renderer = meta_backend_get_renderer (backend);
|
2020-11-21 06:52:45 -05:00
|
|
|
MetaInputSettings *input_settings;
|
2017-03-10 00:55:33 -05:00
|
|
|
|
2019-08-27 06:11:07 -04:00
|
|
|
COGL_TRACE_BEGIN_SCOPED (MetaBackendNativeResume,
|
|
|
|
"Backend (resume)");
|
|
|
|
|
2020-12-17 16:12:41 -05:00
|
|
|
meta_monitor_manager_native_resume (monitor_manager_native);
|
2020-12-15 16:42:55 -05:00
|
|
|
meta_kms_resume (native->kms);
|
2017-03-10 00:55:33 -05:00
|
|
|
|
2019-01-11 09:35:42 -05:00
|
|
|
connect_udev_device_added_handler (native);
|
|
|
|
|
2019-09-25 17:04:25 -04:00
|
|
|
meta_seat_native_reclaim_devices (seat);
|
clutter: Paint views with individual frame clocks
Replace the default master clock with multiple frame clocks, each
driving its own stage view. As each stage view represents one CRTC, this
means we draw each CRTC with its own designated frame clock,
disconnected from all the others.
For example this means we when using the native backend will never need
to wait for one monitor to vsync before painting another, so e.g. having
a 144 Hz monitor next to a 60 Hz monitor, things including both Wayland
and X11 applications and shell UI will be able to render at the
corresponding monitor refresh rate.
This also changes a warning about missed frames when sending
_NETWM_FRAME_TIMINGS messages to a debug log entry, as it's expected
that we'll start missing frames e.g. when a X11 window (via Xwayland) is
exclusively within a stage view that was not painted, while another one
was, still increasing the global frame clock.
Addititonally, this also requires the X11 window actor to schedule
timeouts for _NET_WM_FRAME_DRAWN/_NET_WM_FRAME_TIMINGS event emitting,
if the actor wasn't on any stage views, as now we'll only get the frame
callbacks on actors when they actually were painted, while in the past,
we'd invoke that vfunc when anything was painted.
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/903
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1285
2020-05-29 18:27:56 -04:00
|
|
|
meta_renderer_resume (renderer);
|
2017-03-10 00:55:33 -05:00
|
|
|
|
2018-07-12 09:01:55 -04:00
|
|
|
clutter_actor_queue_redraw (CLUTTER_ACTOR (stage));
|
2017-03-10 00:55:33 -05:00
|
|
|
|
2020-01-30 15:53:31 -05:00
|
|
|
idle_monitor = meta_idle_monitor_get_core ();
|
2018-03-20 05:59:04 -04:00
|
|
|
meta_idle_monitor_reset_idletime (idle_monitor);
|
2019-05-23 11:55:20 -04:00
|
|
|
|
2020-11-21 06:52:45 -05:00
|
|
|
input_settings = meta_backend_get_input_settings (backend);
|
|
|
|
meta_input_settings_maybe_restore_numlock_state (input_settings);
|
2019-08-28 03:55:16 -04:00
|
|
|
|
2019-10-02 07:42:51 -04:00
|
|
|
clutter_seat_ensure_a11y_state (CLUTTER_SEAT (seat));
|
2017-03-10 00:55:33 -05:00
|
|
|
}
|