Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 861221 Details for
Bug 1062669
PARTNER[SGI] kabi whitelist request
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Improved symbol descriptions for symbols from arch/x86
ArchPost (text/plain), 3.66 KB, created by
George Beshers
on 2014-02-10 03:05:08 UTC
(
hide
)
Description:
Improved symbol descriptions for symbols from arch/x86
Filename:
MIME Type:
Creator:
George Beshers
Created:
2014-02-10 03:05:08 UTC
Size:
3.66 KB
patch
obsolete
>########## arch/x86/kernel/apic/apic.c >(x86_cpu_to_apicid) > >Used by the gru to concert a CPU number to thread0 of >a hyperthread core. This does assume the low apicid >bit is for HT. > >The React module also uses apicid to send IPI's through >the UV hub chip. > >(apic) > >+1 on whitelisting this, we do need it to be external >because some diagnostics use apic_read and apic_write. > >########## arch/x86/kernel/apic/x2apic_uv_x.c >(__uv_hub_info) >(sn_rtc_cycles_per_second) >(is_uv_system) >(uv_blade_info) >(uv_cpu_to_blade) >(uv_node_to_blade) >(uv_possible_blades) > >These are all UV specific symbols asking to whitelist >(graylist?) as its unlikely anyone else will change >them; we would only do so to fix a serious bug. > >########## arch/x86/kernel/cpu/common.c >(current_task) > >Used in get_current() which is then used to define "current" >which is used to get per-task data (pid, tgid, comm, etc.). > >(kernel_stack) > >Used indirectly through the macro DEFINE_PER_CPU() >since we frequently need per cpu data. > >########## arch/x86/kernel/paravirt.c >(pv_irq_ops) >(pv_mmu_ops) >(pv_cpu_ops) >(paravirt_ticketlocks_enabled) >(pv_lock_ops) > >These symbols are required so that SGI modules play >nice with paravirt in the kernel; yes we are trying >to make guest OS more Numa aware. > > >########## arch/x86/kernel/setup.c >(boot_cpu_data) > >This struct is used by sync_core() which is >defined in arch/x86/include/asm/processor.h; >sync_core() is needed to guarantee data consistency. > >It is also used to get the number of physical >address bits available. and the pgprot_noncached() >macro in <asm/pgtable.h>. > >########## arch/x86/kernel/setup_percpu.c >(cpu_number) > >This is used by raw_smp_processor_id() macro declared in >arch/x86/include/asm/smp.h; raw_smp_processor_id() is called >directly to avoid the debug info generated by smp_processor_id() >should CONFIG_DEBUG_PREEMPT be set and the thread not be pinned >to this CPU. > >(this_cpu_off) > >Used by PER_CPU() macro which is required to access per_cpu >data. > >########## arch/x86/kernel/smpboot.c >(cpu_info) > >Used by hwperf in preparing results, particularly >important if a UV system contains a mixture of cpus >in different blades. > >(cpu_sibling_map) > >This is used by the Gru to work around cases where >the IRQs on CPU0 are exhausted by the DMAR. DMAR >assignments happen very early during boot before >other CPUs have been started. > >######### arch/x86/kernel/tsc.c >(cpu_khz) > >This read_mostly value is used by hwperf when >cpufreq_quick_get() returns 0. > >(tsc_khz) > >This are read_mostly values is used by the GRU to compute >the GRU_OPERATION_TIMEOUT for detecting hung instructions. > >########## arch/x86/kernel/x8664_ksyms_64.c >(_copy_to_user) >(__fentry__) >(__get_user_2) >(phys_base) >(__put_user_2) >(__put_user_4) >(__put_user_8) > >These are all used for moving data to-from user space. >Usage is coupled with system calls. > >########## arch/x86/lib/usercopy_32.c >(_copy_from_user) > >This is also used for moving data from user space; most >of the time this is data pointed to by a system call parameter. > >########## arch/x86/mm/ioremap.c >(ioremap_nocache) >(iounmap) > >These are used for IOC4 needing to own the MMIO memory range >for the registers the IOC4 chip implements. > >########## arch/x86/mm/numa.c >(node_data) >(__node_distance) >(node_to_cpumask_map) > >These are standard for working with NUMA hardware like UV. > >########## arch/x86/um/delay.c >(__const_udelay) > >This is used by the Frame Rate Scheduler to schedule >threads at precise intervals. > >########## >(sn_coherency_id) >(sn_partition_id) >(sn_region_size) >(uv_bios_call) >(uv_type) >(uv_setup_irq) >(uv_teardown_irq) > >These are all UV specific symbols we are asking to whitelist >(graylist?) as its unlikely anyone else will change >them; we would only do so to fix a serious bug.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1062669
:
860715
|
861221
|
861222
|
861371
|
862952
|
871236