1. 29 10月, 2010 1 次提交
  2. 27 10月, 2010 4 次提交
  3. 23 10月, 2010 1 次提交
    • M
      add Packet hub driver for Topcliff Platform controller hub · cf4ece53
      Masayuki Ohtak 提交于
      Packet hub driver of Topcliff PCH
      
      Topcliff PCH is the platform controller hub that is going to be used in
      Intel's upcoming general embedded platform. All IO peripherals in
      Topcliff PCH are actually devices sitting on AMBA bus. Packet hub is
      a special converter device in Topcliff PCH that translate AMBA transactions
      to PCI Express transactions and vice versa. Thus packet hub helps present
      all IO peripherals in Topcliff PCH as PCIE devices to IA system.
      Topcliff PCH has MAC address and Option ROM data.
      These data are in SROM which is connected to PCIE bus.
      Packet hub driver of Topcliff PCH can access MAC address and Option ROM data in
      SROM via sysfs interface.
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      cf4ece53
  4. 06 10月, 2010 1 次提交
  5. 23 9月, 2010 1 次提交
  6. 10 8月, 2010 3 次提交
  7. 26 7月, 2010 1 次提交
  8. 25 5月, 2010 1 次提交
  9. 25 4月, 2010 1 次提交
    • D
      VMware Balloon driver · 453dc659
      Dmitry Torokhov 提交于
      This is a standalone version of VMware Balloon driver.  Ballooning is a
      technique that allows hypervisor dynamically limit the amount of memory
      available to the guest (with guest cooperation).  In the overcommit
      scenario, when hypervisor set detects that it needs to shuffle some
      memory, it instructs the driver to allocate certain number of pages, and
      the underlying memory gets returned to the hypervisor.  Later hypervisor
      may return memory to the guest by reattaching memory to the pageframes and
      instructing the driver to "deflate" balloon.
      
      We are submitting a standalone driver because KVM maintainer (Avi Kivity)
      expressed opinion (rightly) that our transport does not fit well into
      virtqueue paradigm and thus it does not make much sense to integrate with
      virtio.
      
      There were also some concerns whether current ballooning technique is the
      right thing.  If there appears a better framework to achieve this we are
      prepared to evaluate and switch to using it, but in the meantime we'd like
      to get this driver upstream.
      
      We want to get the driver accepted in distributions so that users do not
      have to deal with an out-of-tree module and many distributions have
      "upstream first" requirement.
      
      The driver has been shipping for a number of years and users running on
      VMware platform will have it installed as part of VMware Tools even if it
      will not come from a distribution, thus there should not be additional
      risk in pulling the driver into mainline.  The driver will only activate
      if host is VMware so everyone else should not be affected at all.
      Signed-off-by: NDmitry Torokhov <dtor@vmware.com>
      Cc: Avi Kivity <avi@redhat.com>
      Cc: Jeremy Fitzhardinge <jeremy@goop.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      453dc659
  10. 07 4月, 2010 1 次提交
  11. 14 3月, 2010 1 次提交
  12. 16 12月, 2009 3 次提交
  13. 07 12月, 2009 1 次提交
  14. 20 10月, 2009 1 次提交
  15. 31 7月, 2009 1 次提交
  16. 14 6月, 2009 1 次提交
  17. 01 4月, 2009 1 次提交
  18. 27 1月, 2009 2 次提交
  19. 17 1月, 2009 1 次提交
  20. 09 1月, 2009 1 次提交
  21. 19 12月, 2008 2 次提交
  22. 13 11月, 2008 2 次提交
  23. 24 9月, 2008 1 次提交
  24. 31 7月, 2008 1 次提交
  25. 26 7月, 2008 1 次提交
  26. 22 7月, 2008 1 次提交
    • D
      HP iLO driver · 89bcb05d
      David Altobelli 提交于
      A driver for the HP iLO/iLO2 management processor, which allows userspace
      programs to query the management processor.  Programs can open a channel
      to the device (/dev/hpilo/dXccbN), and use this to send/receive queries.  
      The O_EXCL open flag is used to indicate that a particular channel cannot
      be shared between processes.  This driver will replace various packages
      HP has shipped, including hprsm and hp-ilo.
      Signed-off-by: NDavid Altobelli <david.altobelli@hp.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      89bcb05d
  27. 17 7月, 2008 1 次提交
    • C
      misc,acpi,backlight: compal Laptop Extras · 5411552c
      Cezary Jackiewicz 提交于
      This is driver for Compal Laptop: FL90/IFL90, based on MSI driver.
      
      This driver exports a few files in /sys/devices/platform/compal-laptop/:
       lcd_level - screen brightness: contains a single integer in the range 0..7 (rw)
       wlan - wlan subsystem state: contains 0 or 1 (rw)
       bluetooth - bluetooth subsystem state: contains 0 or 1 (rw)
       raw - raw value taken from embedded controller register (ro)
      
      In addition to these platform device attributes the driver registers itself
      in the Linux backlight control subsystem and is available to userspace under
      /sys/class/backlight/compal-laptop/.
      Signed-off-by: NCezary Jackiewicz <cezary.jackiewicz@gmail.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Alexey Starikovskiy <aystarik@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      5411552c
  28. 29 4月, 2008 1 次提交
  29. 23 4月, 2008 1 次提交
  30. 18 4月, 2008 1 次提交
    • J
      kgdb: add kgdb internal test suite · e8d31c20
      Jason Wessel 提交于
      This patch adds regression tests for testing the kgdb core and arch
      specific implementation.
      
      The kgdb test suite is designed to be built into the kernel and not as
      a module because it uses a number of low level kernel and kgdb
      primitives which should not be exported externally.
      
      The kgdb test suite is designed as a KGDB I/O module which
      simulates the communications that a debugger would have with kgdb.
      The tests are broken up in to a line by line and referenced here as
      a "get" which is kgdb requesting input and "put" which is kgdb
      sending a response.
      
      The kgdb suite can be invoked from the kernel command line
      arguments system or executed dynamically at run time.  The test
      suite uses the variable "kgdbts" to obtain the information about
      which tests to run and to configure the verbosity level.  The
      following are the various characters you can use with the kgdbts=
      line:
      
      When using the "kgdbts=" you only choose one of the following core
      test types:
      A = Run all the core tests silently
      V1 = Run all the core tests with minimal output
      V2 = Run all the core tests in debug mode
      
      You can also specify optional tests:
      N## = Go to sleep with interrupts of for ## seconds
            to test the HW NMI watchdog
      F## = Break at do_fork for ## iterations
      S## = Break at sys_open for ## iterations
      
      NOTE: that the do_fork and sys_open tests are mutually exclusive.
      
      To invoke the kgdb test suite from boot you use a kernel start
      argument as follows:
      	kgdbts=V1 kgdbwait
      Or if you wanted to perform the NMI test for 6 seconds and do_fork
      test for 100 forks, you could use:
      	kgdbts=V1N6F100 kgdbwait
      
      The test suite can also be invoked at run time with:
      echo kgdbts=V1N6F100 > /sys/module/kgdbts/parameters/kgdbts
      Or as another example:
      echo kgdbts=V2 > /sys/module/kgdbts/parameters/kgdbts
      
      When developing a new kgdb arch specific implementation or
      using these tests for the purpose of regression testing,
      several invocations are required.
      
      1) Boot with the test suite enabled by using the kernel arguments
            "kgdbts=V1F100 kgdbwait"
         ## If kgdb arch specific implementation has NMI use
            "kgdbts=V1N6F100
      
      2) After the system boot run the basic test.
      echo kgdbts=V1 > /sys/module/kgdbts/parameters/kgdbts
      
      3) Run the concurrency tests.  It is best to use n+1
         while loops where n is the number of cpus you have
         in your system.  The example below uses only two
         loops.
      
      ## This tests break points on sys_open
      while [ 1 ] ; do find / > /dev/null 2>&1 ; done &
      while [ 1 ] ; do find / > /dev/null 2>&1 ; done &
      echo kgdbts=V1S10000 > /sys/module/kgdbts/parameters/kgdbts
      fg # and hit control-c
      fg # and hit control-c
      ## This tests break points on do_fork
      while [ 1 ] ; do date > /dev/null ; done &
      while [ 1 ] ; do date > /dev/null ; done &
      echo kgdbts=V1F1000 > /sys/module/kgdbts/parameters/kgdbts
      fg # and hit control-c
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      e8d31c20