1. 10 3月, 2022 1 次提交
  2. 01 2月, 2022 1 次提交
  3. 03 12月, 2021 2 次提交
  4. 05 10月, 2021 1 次提交
  5. 22 9月, 2021 1 次提交
  6. 20 8月, 2021 1 次提交
  7. 29 7月, 2021 1 次提交
  8. 13 5月, 2021 1 次提交
    • C
      docs: typo fixes in Documentation/ABI/ · 3e42d1de
      Carlos Bilbao 提交于
      Fix the following typos in the Documentation/ABI/ directory:
      
      - In file obsolete/sysfs-cpuidle, change "obselete" for "obsolete".
      
      - In file removed/sysfs-kernel-uids, change "propotional" for "proportional".
      
      - In directory stable/, fix the following words: "associtated" for "associated",
        "hexidecimal" for "hexadecimal", "vlue" for "value", "csed" for "caused" and
        "wrtie" for "write". This updates a total of five files.
      
      - In directory testing/, fix the following words: "subystem" for "subsystem",
        "isochrnous" for "isochronous", "Desctiptors" for "Descriptors", "picutre" for
        "picture", "capture" for "capture", "occured" for "ocurred", "connnected" for
        "connected","agressively" for "aggressively","manufacturee" for "manufacturer"
        and "transaction" for "transaction", "malformatted" for "incorrectly formated"
        ,"internel" for "internal", "writtento" for "written to", "specificed" for
        "specified", "beyound" for "beyond", "Symetric" for "Symmetric". This updates
        a total of eleven files.
      Signed-off-by: NCarlos Bilbao <bilbao@vt.edu>
      Reviewed-by: NRandy Dunlap <rdunlap@infradead.org>
      Reviewed-by: NMauro Carvalho Chehab <mchehab+huawei@kernel.org>
      Link: https://lore.kernel.org/r/5710038.lOV4Wx5bFT@iron-maidenSigned-off-by: NJonathan Corbet <corbet@lwn.net>
      3e42d1de
  9. 04 5月, 2021 1 次提交
  10. 16 12月, 2020 1 次提交
  11. 30 10月, 2020 2 次提交
  12. 19 5月, 2020 1 次提交
  13. 30 4月, 2020 1 次提交
  14. 20 4月, 2020 1 次提交
    • M
      x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation · 7e5b3c26
      Mark Gross 提交于
      SRBDS is an MDS-like speculative side channel that can leak bits from the
      random number generator (RNG) across cores and threads. New microcode
      serializes the processor access during the execution of RDRAND and
      RDSEED. This ensures that the shared buffer is overwritten before it is
      released for reuse.
      
      While it is present on all affected CPU models, the microcode mitigation
      is not needed on models that enumerate ARCH_CAPABILITIES[MDS_NO] in the
      cases where TSX is not supported or has been disabled with TSX_CTRL.
      
      The mitigation is activated by default on affected processors and it
      increases latency for RDRAND and RDSEED instructions. Among other
      effects this will reduce throughput from /dev/urandom.
      
      * Enable administrator to configure the mitigation off when desired using
        either mitigations=off or srbds=off.
      
      * Export vulnerability status via sysfs
      
      * Rename file-scoped macros to apply for non-whitelist table initializations.
      
       [ bp: Massage,
         - s/VULNBL_INTEL_STEPPING/VULNBL_INTEL_STEPPINGS/g,
         - do not read arch cap MSR a second time in tsx_fused_off() - just pass it in,
         - flip check in cpu_set_bug_bits() to save an indentation level,
         - reflow comments.
         jpoimboe: s/Mitigated/Mitigation/ in user-visible strings
         tglx: Dropped the fused off magic for now
       ]
      Signed-off-by: NMark Gross <mgross@linux.intel.com>
      Signed-off-by: NBorislav Petkov <bp@suse.de>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Reviewed-by: NTony Luck <tony.luck@intel.com>
      Reviewed-by: NPawan Gupta <pawan.kumar.gupta@linux.intel.com>
      Reviewed-by: NJosh Poimboeuf <jpoimboe@redhat.com>
      Tested-by: NNeelima Krishnan <neelima.krishnan@intel.com>
      7e5b3c26
  15. 27 12月, 2019 1 次提交
    • R
      cpuidle: Allow idle states to be disabled by default · 75a80267
      Rafael J. Wysocki 提交于
      In certain situations it may be useful to prevent some idle states
      from being used by default while allowing user space to enable them
      later on.
      
      For this purpose, introduce a new state flag, CPUIDLE_FLAG_OFF, to
      mark idle states that should be disabled by default, make the core
      set CPUIDLE_STATE_DISABLED_BY_USER for those states at the
      initialization time and add a new state attribute in sysfs,
      "default_status", to inform user space of the initial status of
      the given idle state ("disabled" if CPUIDLE_FLAG_OFF is set for it,
      "enabled" otherwise).
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      75a80267
  16. 04 11月, 2019 1 次提交
  17. 28 10月, 2019 1 次提交
  18. 30 8月, 2019 1 次提交
  19. 15 7月, 2019 1 次提交
  20. 24 6月, 2019 1 次提交
  21. 09 6月, 2019 1 次提交
  22. 08 4月, 2019 1 次提交
  23. 02 4月, 2019 1 次提交
  24. 07 3月, 2019 3 次提交
  25. 13 12月, 2018 1 次提交
  26. 13 7月, 2018 1 次提交
    • J
      x86/bugs, kvm: Introduce boot-time control of L1TF mitigations · d90a7a0e
      Jiri Kosina 提交于
      Introduce the 'l1tf=' kernel command line option to allow for boot-time
      switching of mitigation that is used on processors affected by L1TF.
      
      The possible values are:
      
        full
      	Provides all available mitigations for the L1TF vulnerability. Disables
      	SMT and enables all mitigations in the hypervisors. SMT control via
      	/sys/devices/system/cpu/smt/control is still possible after boot.
      	Hypervisors will issue a warning when the first VM is started in
      	a potentially insecure configuration, i.e. SMT enabled or L1D flush
      	disabled.
      
        full,force
      	Same as 'full', but disables SMT control. Implies the 'nosmt=force'
      	command line option. sysfs control of SMT and the hypervisor flush
      	control is disabled.
      
        flush
      	Leaves SMT enabled and enables the conditional hypervisor mitigation.
      	Hypervisors will issue a warning when the first VM is started in a
      	potentially insecure configuration, i.e. SMT enabled or L1D flush
      	disabled.
      
        flush,nosmt
      	Disables SMT and enables the conditional hypervisor mitigation. SMT
      	control via /sys/devices/system/cpu/smt/control is still possible
      	after boot. If SMT is reenabled or flushing disabled at runtime
      	hypervisors will issue a warning.
      
        flush,nowarn
      	Same as 'flush', but hypervisors will not warn when
      	a VM is started in a potentially insecure configuration.
      
        off
      	Disables hypervisor mitigations and doesn't emit any warnings.
      
      Default is 'flush'.
      
      Let KVM adhere to these semantics, which means:
      
        - 'lt1f=full,force'	: Performe L1D flushes. No runtime control
          			  possible.
      
        - 'l1tf=full'
        - 'l1tf-flush'
        - 'l1tf=flush,nosmt'	: Perform L1D flushes and warn on VM start if
      			  SMT has been runtime enabled or L1D flushing
      			  has been run-time enabled
      			  
        - 'l1tf=flush,nowarn'	: Perform L1D flushes and no warnings are emitted.
        
        - 'l1tf=off'		: L1D flushes are not performed and no warnings
      			  are emitted.
      
      KVM can always override the L1D flushing behavior using its 'vmentry_l1d_flush'
      module parameter except when lt1f=full,force is set.
      
      This makes KVM's private 'nosmt' option redundant, and as it is a bit
      non-systematic anyway (this is something to control globally, not on
      hypervisor level), remove that option.
      
      Add the missing Documentation entry for the l1tf vulnerability sysfs file
      while at it.
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Tested-by: NJiri Kosina <jkosina@suse.cz>
      Reviewed-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Reviewed-by: NJosh Poimboeuf <jpoimboe@redhat.com>
      Link: https://lkml.kernel.org/r/20180713142323.202758176@linutronix.de
      d90a7a0e
  27. 21 6月, 2018 1 次提交
    • T
      cpu/hotplug: Provide knobs to control SMT · 05736e4a
      Thomas Gleixner 提交于
      Provide a command line and a sysfs knob to control SMT.
      
      The command line options are:
      
       'nosmt':	Enumerate secondary threads, but do not online them
       		
       'nosmt=force': Ignore secondary threads completely during enumeration
       		via MP table and ACPI/MADT.
      
      The sysfs control file has the following states (read/write):
      
       'on':		 SMT is enabled. Secondary threads can be freely onlined
       'off':		 SMT is disabled. Secondary threads, even if enumerated
       		 cannot be onlined
       'forceoff':	 SMT is permanentely disabled. Writes to the control
       		 file are rejected.
       'notsupported': SMT is not supported by the CPU
      
      The command line option 'nosmt' sets the sysfs control to 'off'. This
      can be changed to 'on' to reenable SMT during runtime.
      
      The command line option 'nosmt=force' sets the sysfs control to
      'forceoff'. This cannot be changed during runtime.
      
      When SMT is 'on' and the control file is changed to 'off' then all online
      secondary threads are offlined and attempts to online a secondary thread
      later on are rejected.
      
      When SMT is 'off' and the control file is changed to 'on' then secondary
      threads can be onlined again. The 'off' -> 'on' transition does not
      automatically online the secondary threads.
      
      When the control file is set to 'forceoff', the behaviour is the same as
      setting it to 'off', but the operation is irreversible and later writes to
      the control file are rejected.
      
      When the control status is 'notsupported' then writes to the control file
      are rejected.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Reviewed-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Acked-by: NIngo Molnar <mingo@kernel.org>
      05736e4a
  28. 16 6月, 2018 1 次提交
  29. 03 5月, 2018 1 次提交
  30. 29 3月, 2018 1 次提交
    • R
      PM: cpuidle/suspend: Add s2idle usage and time state attributes · 64bdff69
      Rafael J. Wysocki 提交于
      Add a new attribute group called "s2idle" under the sysfs directory
      of each cpuidle state that supports the ->enter_s2idle callback
      and put two new attributes, "usage" and "time", into that group to
      represent the number of times the given state was requested for
      suspend-to-idle and the total time spent in suspend-to-idle after
      requesting that state, respectively.
      
      That will allow diagnostic information related to suspend-to-idle
      to be collected without enabling advanced debug features and
      analyzing dmesg output.
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      64bdff69
  31. 12 2月, 2018 1 次提交
  32. 09 1月, 2018 1 次提交
  33. 08 1月, 2018 1 次提交
  34. 13 10月, 2017 1 次提交
  35. 09 4月, 2017 1 次提交
  36. 27 10月, 2016 1 次提交