1. 01 7月, 2015 7 次提交
  2. 26 6月, 2015 20 次提交
  3. 23 6月, 2015 1 次提交
  4. 22 6月, 2015 1 次提交
  5. 16 6月, 2015 2 次提交
    • L
      kconfig: add xenconfig defconfig helper · 6c668505
      Luis R. Rodriguez 提交于
      This lets you build a kernel which can support xen dom0
      or xen guests on i386, x86-64 and arm64 by just using:
      
         make xenconfig
      
      You can start from an allnoconfig and then switch to xenconfig.
      This also splits out the options which are available currently
      to be built with x86 and 'make ARCH=arm64' under a shared config.
      
      Technically xen supports a dom0 kernel and also a guest
      kernel configuration but upon review with the xen team
      since we don't have many dom0 options its best to just
      combine these two into one.
      
      A few generic notes: we enable both of these:
      
      CONFIG_INET=y
      CONFIG_BINFMT_ELF=y
      
      although technically not required given you likely will
      end up with a pretty useless system otherwise.
      
      A few architectural differences worth noting:
      
      $ make allnoconfig; make xenconfig > /dev/null ; \
      	grep XEN .config > 64-bit-config
      $ make ARCH=i386 allnoconfig; make ARCH=i386 xenconfig > /dev/null; \
      	grep XEN .config > 32-bit-config
      $ make ARCH=arm64 allnoconfig; make ARCH=arm64 xenconfig > /dev/null; \
      	grep XEN .config > arm64-config
      
      Since the options are already split up with a generic config and
      architecture specific configs you anything on the x86 configs
      are known to only work right now on x86. For instance arm64 doesn't
      support MEMORY_HOTPLUG yet as such although we try to enabe it
      generically arm64 doesn't have it yet, so we leave the xen
      specific kconfig option XEN_BALLOON_MEMORY_HOTPLUG on x86's config
      file to set expecations correctly.
      
      Then on x86 we have differences between i386 and x86-64. The difference
      between 64-bit-config and 32-bit-config is you don't get XEN_MCE_LOG as
      this is only supported on 64-bit. You also do not get on i386
      XEN_BALLOON_MEMORY_HOTPLUG, there does not seem to be any technical
      reasons to not allow this but I gave up after a few attempts.
      
      Cc: Josh Triplett <josh@joshtriplett.org>
      Cc: Borislav Petkov <bp@suse.de>
      Cc: Pekka Enberg <penberg@kernel.org>
      Cc: David Rientjes <rientjes@google.com>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: Randy Dunlap <rdunlap@infradead.org>
      Cc: penberg@kernel.org
      Cc: levinsasha928@gmail.com
      Cc: mtosatti@redhat.com
      Cc: fengguang.wu@intel.com
      Cc: David Vrabel <david.vrabel@citrix.com>
      Cc: Ian Campbell <Ian.Campbell@citrix.com>
      Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Cc: xen-devel@lists.xenproject.org
      Acked-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Acked-by: NJulien Grall <julien.grall@linaro.org>
      Acked-by: NMichal Marek <mmarek@suse.cz>
      Acked-by: NDavid Rientjes <rientjes@google.com>
      Reviewed-by: NJosh Triplett <josh@joshtriplett.org>
      Signed-off-by: NLuis R. Rodriguez <mcgrof@suse.com>
      Signed-off-by: NDavid Vrabel <david.vrabel@citrix.com>
      6c668505
    • L
      kconfig: clarify kvmconfig is for kvm · 9bcd776d
      Luis R. Rodriguez 提交于
      We'll be adding options for xen as well.
      
      Cc: Josh Triplett <josh@joshtriplett.org>
      Cc: Borislav Petkov <bp@suse.de>
      Cc: Pekka Enberg <penberg@kernel.org>
      Cc: David Rientjes <rientjes@google.com>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: Randy Dunlap <rdunlap@infradead.org>
      Cc: penberg@kernel.org
      Cc: levinsasha928@gmail.com
      Cc: mtosatti@redhat.com
      Cc: fengguang.wu@intel.com
      Cc: David Vrabel <david.vrabel@citrix.com>
      Cc: Ian Campbell <Ian.Campbell@citrix.com>
      Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Cc: xen-devel@lists.xenproject.org
      Reviewed-by: NJosh Triplett <josh@joshtriplett.org>
      Acked-by: NDavid Rientjes <rientjes@google.com>
      Acked-by: NBorislav Petkov <bp@suse.de>
      Acked-by: NMichal Marek <mmarek@suse.cz>
      Signed-off-by: NLuis R. Rodriguez <mcgrof@suse.com>
      Signed-off-by: NDavid Vrabel <david.vrabel@citrix.com>
      9bcd776d
  6. 11 6月, 2015 1 次提交
  7. 04 6月, 2015 1 次提交
    • I
      x86/asm/entry: Move the arch/x86/syscalls/ definitions to arch/x86/entry/syscalls/ · 1f57d5d8
      Ingo Molnar 提交于
      The build time generated syscall definitions are entry code related, move
      them into the arch/x86/entry/ directory.
      
      Cc: Borislav Petkov <bp@alien8.de>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Andy Lutomirski <luto@amacapital.net>
      Cc: Denys Vlasenko <dvlasenk@redhat.com>
      Cc: Brian Gerst <brgerst@gmail.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NIngo Molnar <mingo@kernel.org>
      1f57d5d8
  8. 31 5月, 2015 1 次提交
  9. 29 5月, 2015 1 次提交
  10. 25 5月, 2015 3 次提交
  11. 14 5月, 2015 1 次提交
    • H
      usb: add bus type for USB ULPI · 289fcff4
      Heikki Krogerus 提交于
      UTMI+ Low Pin Interface (ULPI) is a commonly used PHY
      interface for USB 2.0. The ULPI specification describes a
      standard set of registers which the vendors can extend for
      their specific needs. ULPI PHYs provide often functions
      such as charger detection and ADP sensing and probing.
      
      There are two major issues that the bus type is meant to
      tackle:
      
      Firstly, ULPI registers are accessed from the controller.
      The bus provides convenient method for the controller
      drivers to share that access with the actual PHY drivers.
      
      Secondly, there are already platforms that assume ULPI PHYs
      are runtime detected, such as many Intel Baytrail based
      platforms. They do not provide any kind of hardware
      description for the ULPI PHYs like separate ACPI device
      object that could be used to enumerate a device from.
      Signed-off-by: NHeikki Krogerus <heikki.krogerus@linux.intel.com>
      Acked-by: NDavid Cohen <david.a.cohen@linux.intel.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      289fcff4
  12. 30 4月, 2015 1 次提交