1. 13 5月, 2015 2 次提交
  2. 23 1月, 2015 1 次提交
  3. 22 1月, 2015 1 次提交
    • M
      s390: add SMT support · 10ad34bc
      Martin Schwidefsky 提交于
      The multi-threading facility is introduced with the z13 processor family.
      This patch adds code to detect the multi-threading facility. With the
      facility enabled each core will surface multiple hardware threads to the
      system. Each hardware threads looks like a normal CPU to the operating
      system with all its registers and properties.
      
      The SCLP interface reports the SMT topology indirectly via the maximum
      thread id. Each reported CPU in the result of a read-scp-information
      is a core representing a number of hardware threads.
      
      To reflect the reduced CPU capacity if two hardware threads run on a
      single core the MT utilization counter set is used to normalize the
      raw cputime obtained by the CPU timer deltas. This scaled cputime is
      reported via the taskstats interface. The normal /proc/stat numbers
      are based on the raw cputime and are not affected by the normalization.
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      10ad34bc
  4. 08 1月, 2015 1 次提交
  5. 16 5月, 2014 1 次提交
  6. 22 4月, 2014 1 次提交
  7. 17 3月, 2014 1 次提交
  8. 24 1月, 2014 1 次提交
  9. 16 12月, 2013 1 次提交
  10. 02 12月, 2013 1 次提交
  11. 15 11月, 2013 2 次提交
  12. 12 9月, 2013 1 次提交
  13. 14 2月, 2013 1 次提交
    • M
      s390/mm: implement software dirty bits · abf09bed
      Martin Schwidefsky 提交于
      The s390 architecture is unique in respect to dirty page detection,
      it uses the change bit in the per-page storage key to track page
      modifications. All other architectures track dirty bits by means
      of page table entries. This property of s390 has caused numerous
      problems in the past, e.g. see git commit ef5d437f
      "mm: fix XFS oops due to dirty pages without buffers on s390".
      
      To avoid future issues in regard to per-page dirty bits convert
      s390 to a fault based software dirty bit detection mechanism. All
      user page table entries which are marked as clean will be hardware
      read-only, even if the pte is supposed to be writable. A write by
      the user process will trigger a protection fault which will cause
      the user pte to be marked as dirty and the hardware read-only bit
      is removed.
      
      With this change the dirty bit in the storage key is irrelevant
      for Linux as a host, but the storage key is still required for
      KVM guests. The effect is that page_test_and_clear_dirty and the
      related code can be removed. The referenced bit in the storage
      key is still used by the page_test_and_clear_young primitive to
      provide page age information.
      
      For page cache pages of mappings with mapping_cap_account_dirty
      there will not be any change in behavior as the dirty bit tracking
      already uses read-only ptes to control the amount of dirty pages.
      Only for swap cache pages and pages of mappings without
      mapping_cap_account_dirty there can be additional protection faults.
      To avoid an excessive number of additional faults the mk_pte
      primitive checks for PageDirty if the pgprot value allows for writes
      and pre-dirties the pte. That avoids all additional faults for
      tmpfs and shmem pages until these pages are added to the swap cache.
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      abf09bed
  14. 01 12月, 2012 1 次提交
    • J
      s390/pci: PCI hotplug support via SCLP · 7441b062
      Jan Glauber 提交于
      Add SCLP PCI configure/deconfigure and implement a PCI hotplug
      controller (s390_pci_hpc). The hotplug controller creates a slot
      for every PCI function in stand-by or configured state. The PCI
      functions are named after the PCI function ID (fid). By writing to
      the power attribute in /sys/bus/pci/slots/<fid>/power the PCI function
      is moved to stand-by or configured state. If moved to the configured
      state the device is automatically scanned by the s390 PCI layer.
      Signed-off-by: NJan Glauber <jang@linux.vnet.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      7441b062
  15. 20 7月, 2012 1 次提交
    • H
      s390/comments: unify copyright messages and remove file names · a53c8fab
      Heiko Carstens 提交于
      Remove the file name from the comment at top of many files. In most
      cases the file name was wrong anyway, so it's rather pointless.
      
      Also unify the IBM copyright statement. We did have a lot of sightly
      different statements and wanted to change them one after another
      whenever a file gets touched. However that never happened. Instead
      people start to take the old/"wrong" statements to use as a template
      for new files.
      So unify all of them in one go.
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      a53c8fab
  16. 14 6月, 2012 1 次提交
  17. 18 5月, 2012 1 次提交
  18. 02 8月, 2008 1 次提交
  19. 14 7月, 2008 1 次提交
  20. 26 1月, 2008 2 次提交
    • H
      [S390] Get rid of additional_cpus kernel parameter. · 48483b32
      Heiko Carstens 提交于
      It caused only a lot of confusion. From now on cpu hotplug of up to
      NR_CPUS will work by default. If somebody wants to limit that then
      the possible_cpus parameter can be used.
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      48483b32
    • H
      [S390] Standby cpu activation/deactivation. · 08d07968
      Heiko Carstens 提交于
      Add a new interface so that cpus can be put into standby state and
      configured state.
      Only offline cpus can be put into standby state or configured state.
      For that the new percpu sysfs attribute "configure" must be used.
      To put a cpu in standby state a "0" must be written to the attribute.
      In order to switch it into configured state a "1" must be written to
      the attribute.
      Only cpus in configured state can be brought online.
      In addition this patch introduces a static mapping of physical to
      logical cpus. As a result only the sysfs directories of present cpus
      will be created. To scan for new cpus the new sysfs attribute "rescan"
      must be used.
      Writing to /sys/devices/system/cpu/rescan will trigger a rescan of
      cpus and will create directories for new cpus.
      
      On IPL only configured cpus will be used. And on reboot/shutdown all
      cpus will remain in their current state (configured/standby).
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      08d07968
  21. 10 7月, 2007 2 次提交
  22. 27 4月, 2007 2 次提交
  23. 06 2月, 2007 1 次提交