Skip to content
Snippets Groups Projects
  1. Dec 02, 2021
  2. Dec 01, 2021
  3. Nov 30, 2021
  4. Nov 29, 2021
  5. Nov 26, 2021
  6. Nov 25, 2021
  7. Nov 23, 2021
  8. Nov 17, 2021
  9. Nov 16, 2021
  10. Nov 15, 2021
  11. Nov 14, 2021
    • Paul Moore's avatar
      net,lsm,selinux: revert the security_sctp_assoc_established() hook · 1aa3b220
      Paul Moore authored
      
      This patch reverts two prior patches, e7310c94
      ("security: implement sctp_assoc_established hook in selinux") and
      7c2ef024 ("security: add sctp_assoc_established hook"), which
      create the security_sctp_assoc_established() LSM hook and provide a
      SELinux implementation.  Unfortunately these two patches were merged
      without proper review (the Reviewed-by and Tested-by tags from
      Richard Haines were for previous revisions of these patches that
      were significantly different) and there are outstanding objections
      from the SELinux maintainers regarding these patches.
      
      Work is currently ongoing to correct the problems identified in the
      reverted patches, as well as others that have come up during review,
      but it is unclear at this point in time when that work will be ready
      for inclusion in the mainline kernel.  In the interest of not keeping
      objectionable code in the kernel for multiple weeks, and potentially
      a kernel release, we are reverting the two problematic patches.
      
      Signed-off-by: default avatarPaul Moore <paul@paul-moore.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      1aa3b220
  12. Nov 12, 2021
  13. Nov 11, 2021
    • Alistair Popple's avatar
      mm/migrate.c: remove MIGRATE_PFN_LOCKED · ab09243a
      Alistair Popple authored
      MIGRATE_PFN_LOCKED is used to indicate to migrate_vma_prepare() that a
      source page was already locked during migrate_vma_collect().  If it
      wasn't then the a second attempt is made to lock the page.  However if
      the first attempt failed it's unlikely a second attempt will succeed,
      and the retry adds complexity.  So clean this up by removing the retry
      and MIGRATE_PFN_LOCKED flag.
      
      Destination pages are also meant to have the MIGRATE_PFN_LOCKED flag
      set, but nothing actually checks that.
      
      Link: https://lkml.kernel.org/r/20211025041608.289017-1-apopple@nvidia.com
      
      
      Signed-off-by: default avatarAlistair Popple <apopple@nvidia.com>
      Reviewed-by: default avatarRalph Campbell <rcampbell@nvidia.com>
      Acked-by: default avatarFelix Kuehling <Felix.Kuehling@amd.com>
      Cc: Alex Deucher <alexander.deucher@amd.com>
      Cc: Jerome Glisse <jglisse@redhat.com>
      Cc: John Hubbard <jhubbard@nvidia.com>
      Cc: Zi Yan <ziy@nvidia.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Ben Skeggs <bskeggs@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      ab09243a
    • Peter Gonda's avatar
      KVM: SEV: Add support for SEV intra host migration · b5663931
      Peter Gonda authored
      
      For SEV to work with intra host migration, contents of the SEV info struct
      such as the ASID (used to index the encryption key in the AMD SP) and
      the list of memory regions need to be transferred to the target VM.
      This change adds a commands for a target VMM to get a source SEV VM's sev
      info.
      
      Signed-off-by: default avatarPeter Gonda <pgonda@google.com>
      Suggested-by: default avatarSean Christopherson <seanjc@google.com>
      Reviewed-by: default avatarMarc Orr <marcorr@google.com>
      Cc: Marc Orr <marcorr@google.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Sean Christopherson <seanjc@google.com>
      Cc: David Rientjes <rientjes@google.com>
      Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
      Cc: Brijesh Singh <brijesh.singh@amd.com>
      Cc: Tom Lendacky <thomas.lendacky@amd.com>
      Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
      Cc: Wanpeng Li <wanpengli@tencent.com>
      Cc: Jim Mattson <jmattson@google.com>
      Cc: Joerg Roedel <joro@8bytes.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Borislav Petkov <bp@alien8.de>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: kvm@vger.kernel.org
      Cc: linux-kernel@vger.kernel.org
      Message-Id: <20211021174303.385706-3-pgonda@google.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      b5663931
  14. Nov 10, 2021
    • Lukasz Luba's avatar
      Documentation: power: Describe 'advanced' and 'simple' EM models · 08374410
      Lukasz Luba authored
      
      The Energy Model (EM) can be registered in two ways:
      
       1) Using a helper function, which under the hood relies on OPP framework
          and DT entry in CPU node: 'dynamic-power-coefficient'. This is
          a 'simple' EM because it's tied to the math formula:
          Power = dynamic-power-coefficient * V^2 * f
      
       2) Using em_dev_register_perf_domain() API function with a driver
          custom callback which provides power for each performance state.
      
          This is 'advanced' EM, since it can better reflect real power
          measurements for each performance state. It's not limited to any
          math formula and can better reflect real physics of the device.
      
      Add description of these two methods to the documentation, so developers
      could choose the suitable registration method (option).
      
      Signed-off-by: default avatarLukasz Luba <lukasz.luba@arm.com>
      [ rjw: Changelog edits ]
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      08374410
Loading