“787316b411ae9190b6224796034f10080a098fc9”上不存在“drivers/video/fbdev/Kconfig”
  1. 03 11月, 2017 1 次提交
    • K
      ia64: Convert timers to use timer_setup() · 2c513d4f
      Kees Cook 提交于
      In preparation for unconditionally passing the struct timer_list pointer to
      all timer callbacks, switch to using the new timer_setup() and from_timer()
      to pass the timer pointer explicitly.
      
      One less trivial change was removing the repeated casting for callers
      of bte_error_handler() by fixing its function declaration and adding a
      small wrapper for the timer callback instead.
      
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Fenghua Yu <fenghua.yu@intel.com>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Joe Perches <joe@perches.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
      Cc: linux-ia64@vger.kernel.org
      Signed-off-by: NKees Cook <keescook@chromium.org>
      2c513d4f
  2. 13 7月, 2017 1 次提交
  3. 02 3月, 2017 3 次提交
  4. 30 9月, 2016 1 次提交
  5. 20 9月, 2016 1 次提交
  6. 03 8月, 2016 1 次提交
  7. 03 5月, 2016 1 次提交
    • A
      ia64: Remove superfluous SMP function call · e298c499
      Anna-Maria Gleixner 提交于
      Since commit 3b9d6da6 ("cpu/hotplug: Fix rollback during error-out
      in __cpu_disable()") it is ensured that callbacks of CPU_ONLINE and
      CPU_DOWN_PREPARE are processed on the hotplugged CPU. Due to this SMP
      function calls are no longer required.
      
      Replace smp_call_function_single() with a direct call to
      ia64_mca_cmc_vector_adjust(). The function itselfs handles disable and
      enable interrupts, therefore the smp_call_function_single() calling
      convention is not preserved.
      
      Cc: Fenghua Yu <fenghua.yu@intel.com>
      Cc: linux-ia64@vger.kernel.org
      Signed-off-by: NAnna-Maria Gleixner <anna-maria@linutronix.de>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      e298c499
  8. 16 6月, 2015 1 次提交
  9. 05 3月, 2015 1 次提交
  10. 27 8月, 2014 1 次提交
    • C
      ia64: Replace __get_cpu_var uses · 6065a244
      Christoph Lameter 提交于
      __get_cpu_var() is used for multiple purposes in the kernel source. One of
      them is address calculation via the form &__get_cpu_var(x).  This calculates
      the address for the instance of the percpu variable of the current processor
      based on an offset.
      
      Other use cases are for storing and retrieving data from the current
      processors percpu area.  __get_cpu_var() can be used as an lvalue when
      writing data or on the right side of an assignment.
      
      __get_cpu_var() is defined as :
      
      #define __get_cpu_var(var) (*this_cpu_ptr(&(var)))
      
      __get_cpu_var() always only does an address determination. However, store
      and retrieve operations could use a segment prefix (or global register on
      other platforms) to avoid the address calculation.
      
      this_cpu_write() and this_cpu_read() can directly take an offset into a
      percpu area and use optimized assembly code to read and write per cpu
      variables.
      
      This patch converts __get_cpu_var into either an explicit address
      calculation using this_cpu_ptr() or into a use of this_cpu operations that
      use the offset.  Thereby address calculations are avoided and less registers
      are used when code is generated.
      
      At the end of the patch set all uses of __get_cpu_var have been removed so
      the macro is removed too.
      
      The patch set includes passes over all arches as well. Once these operations
      are used throughout then specialized macros can be defined in non -x86
      arches as well in order to optimize per cpu access by f.e.  using a global
      register that may be set to the per cpu base.
      
      Transformations done to __get_cpu_var()
      
      1. Determine the address of the percpu instance of the current processor.
      
      	DEFINE_PER_CPU(int, y);
      	int *x = &__get_cpu_var(y);
      
          Converts to
      
      	int *x = this_cpu_ptr(&y);
      
      2. Same as #1 but this time an array structure is involved.
      
      	DEFINE_PER_CPU(int, y[20]);
      	int *x = __get_cpu_var(y);
      
          Converts to
      
      	int *x = this_cpu_ptr(y);
      
      3. Retrieve the content of the current processors instance of a per cpu
      variable.
      
      	DEFINE_PER_CPU(int, y);
      	int x = __get_cpu_var(y)
      
         Converts to
      
      	int x = __this_cpu_read(y);
      
      4. Retrieve the content of a percpu struct
      
      	DEFINE_PER_CPU(struct mystruct, y);
      	struct mystruct x = __get_cpu_var(y);
      
         Converts to
      
      	memcpy(&x, this_cpu_ptr(&y), sizeof(x));
      
      5. Assignment to a per cpu variable
      
      	DEFINE_PER_CPU(int, y)
      	__get_cpu_var(y) = x;
      
         Converts to
      
      	__this_cpu_write(y, x);
      
      6. Increment/Decrement etc of a per cpu variable
      
      	DEFINE_PER_CPU(int, y);
      	__get_cpu_var(y)++
      
         Converts to
      
      	__this_cpu_inc(y)
      
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Fenghua Yu <fenghua.yu@intel.com>
      Cc: linux-ia64@vger.kernel.org
      Signed-off-by: NChristoph Lameter <cl@linux.com>
      Signed-off-by: NTejun Heo <tj@kernel.org>
      6065a244
  11. 29 3月, 2014 1 次提交
  12. 05 3月, 2014 1 次提交
  13. 25 6月, 2013 1 次提交
    • P
      [IA64] Delete __cpuinit usage from all ia64 users · ccce9bb8
      Paul Gortmaker 提交于
      The __cpuinit type of throwaway sections might have made sense
      some time ago when RAM was more constrained, but now the savings
      do not offset the cost and complications.  For example, the fix in
      commit 5e427ec2 ("x86: Fix bit corruption at CPU resume time")
      is a good example of the nasty type of bugs that can be created
      with improper use of the various __init prefixes.
      
      After a discussion on LKML[1] it was decided that cpuinit should go
      the way of devinit and be phased out.  Once all the users are gone,
      we can then finally remove the macros themselves from linux/init.h.
      
      This removes all the ia64 uses of the __cpuinit macros.
      
      [1] https://lkml.org/lkml/2013/5/20/589Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      ccce9bb8
  14. 03 4月, 2013 1 次提交
    • T
      Fix initialization of CMCI/CMCP interrupts · d303e9e9
      Tony Luck 提交于
      Back 2010 during a revamp of the irq code some initializations
      were moved from ia64_mca_init() to ia64_mca_late_init() in
      
      	commit c75f2aa1
      	Cannot use register_percpu_irq() from ia64_mca_init()
      
      But this was hideously wrong. First of all these initializations
      are now down far too late. Specifically after all the other cpus
      have been brought up and initialized their own CMC vectors from
      smp_callin(). Also ia64_mca_late_init() may be called from any cpu
      so the line:
      	ia64_mca_cmc_vector_setup();       /* Setup vector on BSP */
      is generally not executed on the BSP, and so the CMC vector isn't
      setup at all on that processor.
      
      Make use of the arch_early_irq_init() hook to get this code executed
      at just the right moment: not too early, not too late.
      Reported-by: NFred Hartnett <fred.hartnett@hp.com>
      Tested-by: NFred Hartnett <fred.hartnett@hp.com>
      Cc: stable@kernel.org # v2.6.37+
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      d303e9e9
  15. 29 3月, 2012 2 次提交
  16. 09 2月, 2012 1 次提交
  17. 29 3月, 2011 1 次提交
  18. 03 3月, 2011 1 次提交
    • J
      [IA64] mca.c: Fix cast from integer to pointer warning · c1d036c4
      Jeff Mahoney 提交于
      ia64_mca_cpu_init has a void *data local variable that is assigned
      the value from either __get_free_pages() or mca_bootmem(). The problem
      is that __get_free_pages returns an unsigned long and mca_bootmem, via
      alloc_bootmem(), returns a void *. format_mca_init_stack takes the void *,
      and it's also used with __pa(), but that casts it to long anyway.
      
      This results in the following build warning:
      
      arch/ia64/kernel/mca.c:1898: warning: assignment makes pointer from
      integer without a cast
      
      Cast the return of __get_free_pages to a void * to avoid
      the warning.
      Signed-off-by: NJeff Mahoney <jeffm@suse.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      c1d036c4
  19. 25 2月, 2011 1 次提交
  20. 08 10月, 2010 1 次提交
  21. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  22. 08 1月, 2010 1 次提交
    • T
      [IA64] __per_cpu_idtrs[] is a memory hog · 6c57a332
      Tony Luck 提交于
      __per_cpu_idtrs is statically allocated ... on CONFIG_NR_CPUS=4096
      systems it hogs 16MB of memory. This is way too much for a quite
      probably unused facility (only KVM uses dynamic TR registers).
      
      Change to an array of pointers, and allocate entries as needed on
      a per cpu basis.  Change the name too as the __per_cpu_ prefix is
      confusing (this isn't a classic <linux/percpu.h> type object).
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      6c57a332
  23. 15 12月, 2009 1 次提交
    • T
      [IA64] Save I-resources to ia64_sal_os_state · 9ee27c76
      Takao Indoh 提交于
      This is a patch related to this discussion.
      http://www.spinics.net/lists/linux-ia64/msg07605.html
      
      When INIT is sent, ip/psr/pfs register is stored to the I-resources
      (iip/ipsr/ifs registers), and they are copied in the min-state save
      area(pmsa_{iip,ipsr,ifs}).
      
      Therefore, in creating pt_regs at ia64_mca_modify_original_stack(),
      cr_{iip,ipsr,ifs} should be derived from pmsa_{iip,ipsr,ifs}. But
      current code copies pmsa_{xip,xpsr,xfs} to cr_{iip,ipsr,ifs}
      when PSR.ic is 0.
      
      finish_pt_regs(struct pt_regs *regs, const pal_min_state_area_t *ms,
                      unsigned long *nat)
      {
      (snip)
              if (ia64_psr(regs)->ic) {
                      regs->cr_iip = ms->pmsa_iip;
                      regs->cr_ipsr = ms->pmsa_ipsr;
                      regs->cr_ifs = ms->pmsa_ifs;
              } else {
                      regs->cr_iip = ms->pmsa_xip;
                      regs->cr_ipsr = ms->pmsa_xpsr;
                      regs->cr_ifs = ms->pmsa_xfs;
              }
      
      It's ok when PSR.ic is not 0. But when PSR.ic is 0, this could be
      a problem when we investigate kernel as the value of regs->cr_iip does
      not point to where INIT really interrupted.
      
      At first I tried to change finish_pt_regs() so that it uses always
      pmsa_{iip,ipsr,ifs} for cr_{iip,ipsr,ifs}, but Keith Owens pointed out
      it could cause another problem if I change it.
      
      >The only problem I can think of is an MCA/INIT
      >arriving while code like SAVE_MIN or SAVE_REST is executing.  Back
      >tracing at that point using pmsa_iip is going to be a problem, you have
      >no idea what state the registers or stack are in.
      
      I confirmed he was right, so I decided to keep it as-is and to
      save pmsa_{iip,ipsr,ifs} to ia64_sal_os_state for debugging.
      
      An attached patch is just adding new members into ia64_sal_os_state to
      save pmsa_{iip,ipsr,ifs}.
      Signed-off-by: NTakao Indoh <indou.takao@jp.fujitsu.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      9ee27c76
  24. 14 10月, 2009 1 次提交
  25. 15 9月, 2009 1 次提交
    • H
      [IA64] kdump: Short path to freeze CPUs · 0cced40e
      Hidetoshi Seto 提交于
      Setting monarch_cpu = -1 to let slaves frozen might not work, because
      there might be slaves being late, not entered the rendezvous yet.
      Such slaves might be caught in while (monarch_cpu == -1) loop.
      
      Use kdump_in_progress instead of monarch_cpus to break INIT rendezvous
      and let all slaves enter DIE_INIT_SLAVE_LEAVE smoothly.
      
      And monarch no longer need to manage rendezvous if once kdump_in_progress
      is set, catch the monarch in DIE_INIT_MONARCH_ENTER then.
      Signed-off-by: NHidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
      Cc: Vivek Goyal <vgoyal@redhat.com>
      Cc: Haren Myneni <hbabu@us.ibm.com>
      Cc: kexec@lists.infradead.org
      Acked-by: NFenghua Yu <fenghua.yu@intel.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      0cced40e
  26. 18 6月, 2009 1 次提交
    • M
      [IA64] Convert ia64 to use int-ll64.h · e088a4ad
      Matthew Wilcox 提交于
      It is generally agreed that it would be beneficial for u64 to be an
      unsigned long long on all architectures.  ia64 (in common with several
      other 64-bit architectures) currently uses unsigned long.  Migrating
      piecemeal is too painful; this giant patch fixes all compilation warnings
      and errors that come as a result of switching to use int-ll64.h.
      
      Note that userspace will still see __u64 defined as unsigned long.  This
      is important as it affects C++ name mangling.
      
      [Updated by Tony Luck to change efi.h:efi_freemem_callback_t to use
       u64 for start/end rather than unsigned long]
      Signed-off-by: NMatthew Wilcox <willy@linux.intel.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      e088a4ad
  27. 17 6月, 2009 1 次提交
  28. 16 6月, 2009 1 次提交
  29. 16 3月, 2009 1 次提交
  30. 21 11月, 2008 1 次提交
  31. 26 6月, 2008 2 次提交
  32. 22 4月, 2008 2 次提交
  33. 10 4月, 2008 2 次提交
  34. 04 4月, 2008 1 次提交