Announcement

Collapse
No announcement yet.

Intel & AMD Send Out New Patches For Linux Cgroup Support For GPUs

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Intel & AMD Send Out New Patches For Linux Cgroup Support For GPUs

    Phoronix: Intel & AMD Send Out New Patches For Linux Cgroup Support For GPUs

    Separate patch series sent out on Wednesday by Intel and AMD Linux developers are continuing work on prepping cgroup infrastructure support around graphics processors...

    http://www.phoronix.com/scan.php?pag...oups-GPUs-2019

  • #2
    this does seem interesting, I wonder if it can be enabled by default - to help secure normal desktops even more? especially paired with wayland and flatpak

    Comment


    • #3
      Originally posted by boxie View Post
      this does seem interesting, I wonder if it can be enabled by default - to help secure normal desktops even more? especially paired with wayland and flatpak
      how would this help secure anything? this is for limiting gpu usage, this could be used to make an scheduler for example

      Comment


      • #4
        Originally posted by davidbepo View Post

        how would this help secure anything? this is for limiting gpu usage, this could be used to make an scheduler for example
        the same way that cgroups prevents unauthorised access to other apps memory?

        Comment


        • #5
          Originally posted by boxie View Post

          the same way that cgroups prevents unauthorised access to other apps memory?
          This shouldn't be possible, regardless of the presence or absence of cgroup

          Comment


          • #6
            Originally posted by Stefem View Post

            This shouldn't be possible, regardless of the presence or absence of cgroup
            Well, i'm no expert on GPU allocations but in theory with wayland at least should be possible to put some barrier to only allow certain process to successfully upload command streams to the GPU with cgroups.

            Also cgroups could control by default(without compositor fine-tuning) that no other session can send/query/sniff command streams to/from the GPU as well, so something like an attacker process running as a different u/gid could not capture your screen, for example.

            i'm not too sure if this could be applied to DMA allocations since i don't know if those pass through the CS or are a separate infrastructure

            Comment


            • #7
              SR IOV in the consumer space is a big deal. Full bare metal performance virtualization. One gpu for multiple OS's- that kinda thing.

              https://youtu.be/ziXaS7fu4M8

              Comment


              • #8
                Would be awesome to limit CPU and GPU this to measure performance/scalability of a 3D engines.

                Comment

                Working...
                X