* Athlon 64 X2 cpuinfo oddities
@ 2006-01-09 20:18 Jesper Juhl
2006-01-09 20:29 ` Dave Dillow
` (2 more replies)
0 siblings, 3 replies; 20+ messages in thread
From: Jesper Juhl @ 2006-01-09 20:18 UTC (permalink / raw)
To: LKML List
I recently bought a Dual Core AMD Athlon 64 X2 4400+ CPU and dropped a
2.6.15 kernel on the box and it runs very nice, but /proc/cpuinfo
shows a few things that seem slightly odd to me (haven't tried earlier
kernels on this so I don't know if cpuinfo looked different
previously).
It may be that it's absolutely correct and not odd at all, but I
thought I'd just ask :)
Here's what cat /proc/cpuinfo shows :
juhl@dragon:~$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 35
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping : 2
cpu MHz : 2200.260
cache size : 1024 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
bogomips : 4403.36
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 35
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping : 2
cpu MHz : 2200.260
cache size : 1024 KB
physical id : 127
siblings : 1
core id : 1
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
bogomips : 4399.53
So, what's odd with that?
Well, first of all you'll notice that the second core shows a
"physical id" of 127 while the first core shows an id of 0. Shouldn't
the second core be id 1, just like the "core id" fields are 0 & 1?
Second thing I find slightly odd is the lack of "sse3" in the "flags" list.
I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3?
Is it a case of:
a) Me being wrong, not all Athlon 64 X2's feature SSE3?
b) The CPU actually featuring SSE3 but Linux not taking advantage of it?
c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo
doesn't show that fact?
d) Something else?
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Athlon 64 X2 cpuinfo oddities 2006-01-09 20:18 Athlon 64 X2 cpuinfo oddities Jesper Juhl @ 2006-01-09 20:29 ` Dave Dillow 2006-01-09 22:49 ` Jesper Juhl 2006-01-09 21:10 ` Rafael J. Wysocki 2006-01-10 1:49 ` Andi Kleen 2 siblings, 1 reply; 20+ messages in thread From: Dave Dillow @ 2006-01-09 20:29 UTC (permalink / raw) To: Jesper Juhl; +Cc: LKML List On Mon, 2006-01-09 at 21:18 +0100, Jesper Juhl wrote: > Second thing I find slightly odd is the lack of "sse3" in the "flags" list. > I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3? > Is it a case of: > a) Me being wrong, not all Athlon 64 X2's feature SSE3? > b) The CPU actually featuring SSE3 but Linux not taking advantage of it? > c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo > doesn't show that fact? > d) Something else? Can't help you with the rest, but SSE3 is called "pni" in cpuinfo for historical reasons, IIRC. -- Dave Dillow <dave@thedillows.org> ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-09 20:29 ` Dave Dillow @ 2006-01-09 22:49 ` Jesper Juhl 0 siblings, 0 replies; 20+ messages in thread From: Jesper Juhl @ 2006-01-09 22:49 UTC (permalink / raw) To: Dave Dillow; +Cc: LKML List On 1/9/06, Dave Dillow <dave@thedillows.org> wrote: > On Mon, 2006-01-09 at 21:18 +0100, Jesper Juhl wrote: > > Second thing I find slightly odd is the lack of "sse3" in the "flags" list. > > I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3? > > Is it a case of: > > a) Me being wrong, not all Athlon 64 X2's feature SSE3? > > b) The CPU actually featuring SSE3 but Linux not taking advantage of it? > > c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo > > doesn't show that fact? > > d) Something else? > > Can't help you with the rest, but SSE3 is called "pni" in cpuinfo for > historical reasons, IIRC. Ahh yes, PNI as in Prescot New Instructions - right? Hmm, someone really ought to rename that to sse3 these days. -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-09 20:18 Athlon 64 X2 cpuinfo oddities Jesper Juhl 2006-01-09 20:29 ` Dave Dillow @ 2006-01-09 21:10 ` Rafael J. Wysocki 2006-01-09 22:32 ` Edmondo Tommasina 2006-01-10 1:49 ` Andi Kleen 2 siblings, 1 reply; 20+ messages in thread From: Rafael J. Wysocki @ 2006-01-09 21:10 UTC (permalink / raw) To: Jesper Juhl; +Cc: LKML List, Discuss x86-64 Hi, On Monday, 9 January 2006 21:18, Jesper Juhl wrote: > I recently bought a Dual Core AMD Athlon 64 X2 4400+ CPU and dropped a > 2.6.15 kernel on the box and it runs very nice, but /proc/cpuinfo > shows a few things that seem slightly odd to me (haven't tried earlier > kernels on this so I don't know if cpuinfo looked different > previously). > It may be that it's absolutely correct and not odd at all, but I > thought I'd just ask :) > > Here's what cat /proc/cpuinfo shows : > > juhl@dragon:~$ cat /proc/cpuinfo > processor : 0 > vendor_id : AuthenticAMD > cpu family : 15 > model : 35 > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ > stepping : 2 > cpu MHz : 2200.260 > cache size : 1024 KB > physical id : 0 > siblings : 1 > core id : 0 > cpu cores : 1 > fdiv_bug : no > hlt_bug : no > f00f_bug : no > coma_bug : no > fpu : yes > fpu_exception : yes > cpuid level : 1 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy > bogomips : 4403.36 > > processor : 1 > vendor_id : AuthenticAMD > cpu family : 15 > model : 35 > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ > stepping : 2 > cpu MHz : 2200.260 > cache size : 1024 KB > physical id : 127 > siblings : 1 > core id : 1 > cpu cores : 1 > fdiv_bug : no > hlt_bug : no > f00f_bug : no > coma_bug : no > fpu : yes > fpu_exception : yes > cpuid level : 1 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy > bogomips : 4399.53 > > > So, what's odd with that? > > Well, first of all you'll notice that the second core shows a > "physical id" of 127 while the first core shows an id of 0. Shouldn't > the second core be id 1, just like the "core id" fields are 0 & 1? FWIW, I'm running 2.6.15 on Athlon X2 4200 and the second core's physical id is 0 (ie. same as of the frist one), the number of siblings for each core is 2, and the "cpu cores" value is 2 as well (yours is 1, apparently ;-)). Greetings, Rafael ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-09 21:10 ` Rafael J. Wysocki @ 2006-01-09 22:32 ` Edmondo Tommasina 2006-01-09 22:41 ` Jesper Juhl 0 siblings, 1 reply; 20+ messages in thread From: Edmondo Tommasina @ 2006-01-09 22:32 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Jesper Juhl, LKML List, Discuss x86-64 On Monday 09-January-2006 22:10, Rafael J. Wysocki wrote: > Hi, > > On Monday, 9 January 2006 21:18, Jesper Juhl wrote: > > I recently bought a Dual Core AMD Athlon 64 X2 4400+ CPU and dropped a > > 2.6.15 kernel on the box and it runs very nice, but /proc/cpuinfo > > shows a few things that seem slightly odd to me (haven't tried earlier > > kernels on this so I don't know if cpuinfo looked different > > previously). > > It may be that it's absolutely correct and not odd at all, but I > > thought I'd just ask :) > > > > Here's what cat /proc/cpuinfo shows : > > > > juhl@dragon:~$ cat /proc/cpuinfo > > processor : 0 > > vendor_id : AuthenticAMD > > cpu family : 15 > > model : 35 > > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ > > stepping : 2 > > cpu MHz : 2200.260 > > cache size : 1024 KB > > physical id : 0 > > siblings : 1 > > core id : 0 > > cpu cores : 1 > > fdiv_bug : no > > hlt_bug : no > > f00f_bug : no > > coma_bug : no > > fpu : yes > > fpu_exception : yes > > cpuid level : 1 > > wp : yes > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > > fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy > > bogomips : 4403.36 > > > > processor : 1 > > vendor_id : AuthenticAMD > > cpu family : 15 > > model : 35 > > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ > > stepping : 2 > > cpu MHz : 2200.260 > > cache size : 1024 KB > > physical id : 127 > > siblings : 1 > > core id : 1 > > cpu cores : 1 > > fdiv_bug : no > > hlt_bug : no > > f00f_bug : no > > coma_bug : no > > fpu : yes > > fpu_exception : yes > > cpuid level : 1 > > wp : yes > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > > fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy > > bogomips : 4399.53 > > > > > > So, what's odd with that? > > > > Well, first of all you'll notice that the second core shows a > > "physical id" of 127 while the first core shows an id of 0. Shouldn't > > the second core be id 1, just like the "core id" fields are 0 & 1? > > FWIW, I'm running 2.6.15 on Athlon X2 4200 and the second core's > physical id is 0 (ie. same as of the frist one), the number of siblings > for each core is 2, and the "cpu cores" value is 2 as well (yours is 1, > apparently ;-)). Same here. cpu cores is 2. Random try: Do you have CONFIG_NR_CPUS=2 in your config? edmondo@balrog ~ $ uname -a Linux balrog 2.6.15 #1 SMP Tue Jan 3 19:44:52 CET 2006 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD GNU/Linux edmondo@balrog ~ $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 35 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ stepping : 2 cpu MHz : 1005.170 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips : 2012.38 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 35 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ stepping : 2 cpu MHz : 1005.170 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy bogomips : 2012.38 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp ciao edmondo ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-09 22:32 ` Edmondo Tommasina @ 2006-01-09 22:41 ` Jesper Juhl 2006-01-09 22:49 ` Edmondo Tommasina 0 siblings, 1 reply; 20+ messages in thread From: Jesper Juhl @ 2006-01-09 22:41 UTC (permalink / raw) To: Edmondo Tommasina; +Cc: Rafael J. Wysocki, LKML List, Discuss x86-64 On 1/9/06, Edmondo Tommasina <edmondo@eriadon.com> wrote: > On Monday 09-January-2006 22:10, Rafael J. Wysocki wrote: > > Hi, > > > > Same here. cpu cores is 2. > > Random try: Do you have CONFIG_NR_CPUS=2 in your config? > Yup. $ zcat /proc/config.gz | grep NR_CPUS CONFIG_NR_CPUS=2 -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-09 22:41 ` Jesper Juhl @ 2006-01-09 22:49 ` Edmondo Tommasina 0 siblings, 0 replies; 20+ messages in thread From: Edmondo Tommasina @ 2006-01-09 22:49 UTC (permalink / raw) To: Jesper Juhl; +Cc: Rafael J. Wysocki, LKML List, Discuss x86-64 [-- Attachment #1: Type: text/plain, Size: 428 bytes --] On Monday 09-January-2006 23:41, Jesper Juhl wrote: > On 1/9/06, Edmondo Tommasina <edmondo@eriadon.com> wrote: > > On Monday 09-January-2006 22:10, Rafael J. Wysocki wrote: > > > Hi, > > > > > > > Same here. cpu cores is 2. > > > > Random try: Do you have CONFIG_NR_CPUS=2 in your config? > > > Yup. > > $ zcat /proc/config.gz | grep NR_CPUS > CONFIG_NR_CPUS=2 Ok :-) Attached my .config. Maybe it's usefull. ciao edmondo [-- Attachment #2: .config --] [-- Type: text/plain, Size: 29955 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.15 # Tue Jan 3 19:42:39 2006 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y # CONFIG_IKCONFIG_PROC is not set # CONFIG_CPUSETS is not set CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Block layer # # CONFIG_LBD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y # CONFIG_IOSCHED_AS is not set CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y CONFIG_SCHED_SMT=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y CONFIG_NUMA=y CONFIG_K8_NUMA=y CONFIG_X86_64_ACPI_NUMA=y # CONFIG_NUMA_EMU is not set CONFIG_ARCH_DISCONTIGMEM_ENABLE=y CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y # CONFIG_FLATMEM_MANUAL is not set CONFIG_DISCONTIGMEM_MANUAL=y # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_DISCONTIGMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_NEED_MULTIPLE_NODES=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y CONFIG_NR_CPUS=2 # CONFIG_HOTPLUG_CPU is not set CONFIG_HPET_TIMER=y CONFIG_X86_PM_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_GART_IOMMU=y CONFIG_SWIOTLB=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_X86_MCE_AMD=y CONFIG_PHYSICAL_START=0x100000 # CONFIG_KEXEC is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y CONFIG_PM_LEGACY=y CONFIG_PM_DEBUG=y # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y # CONFIG_ACPI_VIDEO is not set # CONFIG_ACPI_HOTKEY is not set CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set CONFIG_ACPI_TOSHIBA=y CONFIG_ACPI_BLACKLIST_YEAR=2001 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y # CONFIG_ACPI_CONTAINER is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y # CONFIG_CPU_FREQ_STAT_DETAILS is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set # # CPUFreq processor drivers # CONFIG_X86_POWERNOW_K8=y CONFIG_X86_POWERNOW_K8_ACPI=y # CONFIG_X86_SPEEDSTEP_CENTRINO is not set # CONFIG_X86_ACPI_CPUFREQ is not set # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_UNORDERED_IO=y CONFIG_PCIEPORTBUS=y CONFIG_PCI_MSI=y # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_DEBUG is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y CONFIG_COMPAT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_UID16=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_BIC=y CONFIG_IPV6=y # CONFIG_IPV6_PRIVACY is not set # CONFIG_INET6_AH is not set # CONFIG_INET6_ESP is not set # CONFIG_INET6_IPCOMP is not set # CONFIG_INET6_TUNNEL is not set # CONFIG_IPV6_TUNNEL is not set # CONFIG_NETFILTER is not set # # DCCP Configuration (EXPERIMENTAL) # # CONFIG_IP_DCCP is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_IEEE80211 is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Connector - unified userspace <-> kernelspace linker # # CONFIG_CONNECTOR is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m # CONFIG_PARPORT_PC is not set # CONFIG_PARPORT_GSC is not set # CONFIG_PARPORT_1284 is not set # # Plug and Play support # CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_PNPACPI=y # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_IDE_TASK_IOCTL is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_IDEPNP is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_IDEPCI_SHARE_IRQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set # CONFIG_BLK_DEV_GENERIC is not set # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set CONFIG_BLK_DEV_AMD74XX=y # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set CONFIG_BLK_DEV_PDC202XX_NEW=y # CONFIG_PDC202XX_FORCE is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set # CONFIG_IDE_ARM is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_HD is not set # # SCSI device support # # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y # CONFIG_SCSI_PROC_FS is not set # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set # CONFIG_BLK_DEV_SR is not set CONFIG_CHR_DEV_SG=m # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # # SCSI Transport Attributes # CONFIG_SCSI_SPI_ATTRS=y # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # CONFIG_SCSI_SAS_ATTRS is not set # # SCSI low-level drivers # # CONFIG_ISCSI_TCP is not set # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set CONFIG_SCSI_AIC79XX=y CONFIG_AIC79XX_CMDS_PER_DEVICE=32 CONFIG_AIC79XX_RESET_DELAY_MS=4000 # CONFIG_AIC79XX_ENABLE_RD_STRM is not set # CONFIG_AIC79XX_DEBUG_ENABLE is not set CONFIG_AIC79XX_DEBUG_MASK=0 # CONFIG_AIC79XX_REG_PRETTY_PRINT is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set CONFIG_SCSI_SATA=y # CONFIG_SCSI_SATA_AHCI is not set # CONFIG_SCSI_SATA_SVW is not set CONFIG_SCSI_ATA_PIIX=y # CONFIG_SCSI_SATA_MV is not set # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_PDC_ADMA is not set # CONFIG_SCSI_SATA_QSTOR is not set # CONFIG_SCSI_SATA_PROMISE is not set # CONFIG_SCSI_SATA_SX4 is not set # CONFIG_SCSI_SATA_SIL is not set # CONFIG_SCSI_SATA_SIL24 is not set # CONFIG_SCSI_SATA_SIS is not set # CONFIG_SCSI_SATA_ULI is not set CONFIG_SCSI_SATA_VIA=y # CONFIG_SCSI_SATA_VITESSE is not set CONFIG_SCSI_SATA_INTEL_COMBINED=y # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_PPA is not set # CONFIG_SCSI_IMM is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_FC is not set # CONFIG_SCSI_QLOGIC_1280 is not set CONFIG_SCSI_QLA2XXX=y # CONFIG_SCSI_QLA21XX is not set # CONFIG_SCSI_QLA22XX is not set # CONFIG_SCSI_QLA2300 is not set # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_QLA6312 is not set # CONFIG_SCSI_QLA24XX is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_DEBUG is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # CONFIG_FUSION_SPI is not set # CONFIG_FUSION_FC is not set # CONFIG_FUSION_SAS is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set CONFIG_TUN=y # CONFIG_NET_SB1000 is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # PHY device support # # CONFIG_PHYLIB is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set # CONFIG_CASSINI is not set # CONFIG_NET_VENDOR_3COM is not set # # Tulip family network device support # # CONFIG_NET_TULIP is not set # CONFIG_HP100 is not set CONFIG_NET_PCI=y # CONFIG_PCNET32 is not set # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_B44 is not set CONFIG_FORCEDETH=m # CONFIG_DGRS is not set # CONFIG_EEPRO100 is not set # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set # CONFIG_NE2K_PCI is not set # CONFIG_8139CP is not set # CONFIG_8139TOO is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_VIA_RHINE is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_E1000 is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SIS190 is not set CONFIG_SKGE=m # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set # CONFIG_TIGON3 is not set # CONFIG_BNX2 is not set # # Ethernet (10000 Mbit) # # CONFIG_CHELSIO_T1 is not set # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PLIP is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PARKBD is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y # CONFIG_SERIAL_8250_ACPI is not set CONFIG_SERIAL_8250_NR_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # CONFIG_PRINTER is not set # CONFIG_PPDEV is not set # CONFIG_TIPAR is not set # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set CONFIG_RTC=y # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # CONFIG_AGP=y CONFIG_AGP_AMD64=y # CONFIG_AGP_INTEL is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set CONFIG_HPET=y # CONFIG_HPET_RTC_IRQ is not set CONFIG_HPET_MMAP=y # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set # # I2C support # CONFIG_I2C=y CONFIG_I2C_CHARDEV=m # # I2C Algorithms # # CONFIG_I2C_ALGOBIT is not set # CONFIG_I2C_ALGOPCF is not set # CONFIG_I2C_ALGOPCA is not set # # I2C Hardware Bus support # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set # CONFIG_I2C_I801 is not set # CONFIG_I2C_I810 is not set # CONFIG_I2C_PIIX4 is not set CONFIG_I2C_ISA=m CONFIG_I2C_NFORCE2=m # CONFIG_I2C_PARPORT is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_PROSAVAGE is not set # CONFIG_I2C_SAVAGE4 is not set # CONFIG_SCx200_ACB is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_STUB is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # CONFIG_I2C_VOODOO3 is not set # CONFIG_I2C_PCA_ISA is not set # # Miscellaneous I2C Chip support # # CONFIG_SENSORS_DS1337 is not set # CONFIG_SENSORS_DS1374 is not set CONFIG_SENSORS_EEPROM=m # CONFIG_SENSORS_PCF8574 is not set # CONFIG_SENSORS_PCA9539 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_RTC8564 is not set # CONFIG_SENSORS_MAX6875 is not set # CONFIG_RTC_X1205_I2C is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # CONFIG_HWMON=m CONFIG_HWMON_VID=m # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83L785TS is not set CONFIG_SENSORS_W83627HF=m # CONFIG_SENSORS_W83627EHF is not set # CONFIG_SENSORS_HDAPS is not set # CONFIG_HWMON_DEBUG_CHIP is not set # # Misc devices # # CONFIG_IBM_ASM is not set # # Multimedia Capabilities Port drivers # # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # # CONFIG_FB is not set CONFIG_VIDEO_SELECT=y # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y # # Sound # CONFIG_SOUND=m # # Advanced Linux Sound Architecture # CONFIG_SND=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_AC97_BUS=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_SEQUENCER=m # CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m # CONFIG_SND_SEQUENCER_OSS is not set # CONFIG_SND_RTCTIMER is not set # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set # # Generic devices # # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set # # PCI devices # # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_HDSP is not set # CONFIG_SND_HDSPM is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_YMFPCI is not set # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_ENS1370 is not set # CONFIG_SND_ENS1371 is not set # CONFIG_SND_ES1938 is not set # CONFIG_SND_ES1968 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_FM801 is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set CONFIG_SND_INTEL8X0=m # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_HDA_INTEL is not set # # USB devices # # CONFIG_SND_USB_AUDIO is not set # CONFIG_SND_USB_USX2Y is not set # # Open Sound System # # CONFIG_SOUND_PRIME is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_BANDWIDTH is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_SUSPEND is not set # CONFIG_USB_OTG is not set # # USB Host Controller Drivers # CONFIG_USB_EHCI_HCD=y # CONFIG_USB_EHCI_SPLIT_ISO is not set # CONFIG_USB_EHCI_ROOT_HUB_TT is not set # CONFIG_USB_ISP116X_HCD is not set CONFIG_USB_OHCI_HCD=y # CONFIG_USB_OHCI_BIG_ENDIAN is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=y # CONFIG_USB_SL811_HCD is not set # # USB Device Class drivers # # CONFIG_OBSOLETE_OSS_USB_DRIVER is not set # CONFIG_USB_ACM is not set CONFIG_USB_PRINTER=y # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # may also be needed; see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_DPCM is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # # USB Input Devices # CONFIG_USB_HID=y CONFIG_USB_HIDINPUT=y # CONFIG_HID_FF is not set # CONFIG_USB_HIDDEV is not set # CONFIG_USB_AIPTEK is not set # CONFIG_USB_WACOM is not set # CONFIG_USB_ACECAD is not set # CONFIG_USB_KBTAB is not set # CONFIG_USB_POWERMATE is not set # CONFIG_USB_MTOUCH is not set # CONFIG_USB_ITMTOUCH is not set # CONFIG_USB_EGALAX is not set # CONFIG_USB_YEALINK is not set # CONFIG_USB_XPAD is not set # CONFIG_USB_ATI_REMOTE is not set # CONFIG_USB_KEYSPAN_REMOTE is not set # CONFIG_USB_APPLETOUCH is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB Multimedia devices # # CONFIG_USB_DABUSB is not set # # Video4Linux support is needed for USB Multimedia device support # # # USB Network Adapters # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_USBNET is not set CONFIG_USB_MON=y # # USB port drivers # # CONFIG_USB_USS720 is not set # # USB Serial Converter support # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_AUERSWALD is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGETKIT is not set # CONFIG_USB_PHIDGETSERVO is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TEST is not set # # USB DSL modem support # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # SN Devices # # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_DELL_RBU is not set CONFIG_DCDBAS=m # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y # CONFIG_EXT2_FS_SECURITY is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_REISERFS_FS_XATTR is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y CONFIG_AUTOFS_FS=y # CONFIG_AUTOFS4_FS is not set # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y # CONFIG_ZISOFS is not set CONFIG_UDF_FS=y CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y CONFIG_MSDOS_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_RELAYFS_FS is not set # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set # CONFIG_NFS_V4 is not set # CONFIG_NFS_DIRECTIO is not set CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V3_ACL is not set # CONFIG_NFSD_V4 is not set CONFIG_NFSD_TCP=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y # CONFIG_RPCSEC_GSS_KRB5 is not set # CONFIG_RPCSEC_GSS_SPKM3 is not set CONFIG_SMB_FS=m # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_XATTR is not set # CONFIG_CIFS_EXPERIMENTAL is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # CONFIG_9P_FS is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set CONFIG_NLS_CODEPAGE_850=y # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set CONFIG_NLS_ISO8859_15=y # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set CONFIG_NLS_UTF8=y # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_INFO is not set CONFIG_DEBUG_FS=y # CONFIG_DEBUG_VM is not set # CONFIG_FRAME_POINTER is not set # CONFIG_RCU_TORTURE_TEST is not set CONFIG_INIT_DEBUG=y # CONFIG_IOMMU_DEBUG is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # # CONFIG_CRYPTO is not set # # Hardware crypto devices # # # Library routines # CONFIG_CRC_CCITT=m # CONFIG_CRC16 is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-09 20:18 Athlon 64 X2 cpuinfo oddities Jesper Juhl 2006-01-09 20:29 ` Dave Dillow 2006-01-09 21:10 ` Rafael J. Wysocki @ 2006-01-10 1:49 ` Andi Kleen 2006-01-10 2:12 ` Jesper Juhl 2006-02-13 2:53 ` Brandon Low 2 siblings, 2 replies; 20+ messages in thread From: Andi Kleen @ 2006-01-10 1:49 UTC (permalink / raw) To: Jesper Juhl; +Cc: linux-kernel Jesper Juhl <jesper.juhl@gmail.com> writes: > > Well, first of all you'll notice that the second core shows a > "physical id" of 127 while the first core shows an id of 0. Shouldn't > the second core be id 1, just like the "core id" fields are 0 & 1? In theory it could be an uninitialized phys_proc_id (0xff >> 1), but it could be also the BIOS just setting the local APIC of CPU 1 to 0xff for some reason. If you add a printk("PHYSCPU %d %x\n", smp_processor_id(), phys_proc_id[smp_processor_id()]) at the end of arch/x86_64/kernel/setup.c:early_identify_cpu() what does dmesg | grep PHYSCPU output? > > Second thing I find slightly odd is the lack of "sse3" in the "flags" list. > I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3? > Is it a case of: > a) Me being wrong, not all Athlon 64 X2's feature SSE3? > b) The CPU actually featuring SSE3 but Linux not taking advantage of it? > c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo > doesn't show that fact? > d) Something else? It's called pni (prescott new instructions) for historical reasons. We added the bit too early before Intel's marketing department could make up its mind fully, so Linux is stuck with the old codename. -Andi ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-10 1:49 ` Andi Kleen @ 2006-01-10 2:12 ` Jesper Juhl 2006-01-10 2:36 ` Andi Kleen 2006-02-13 2:53 ` Brandon Low 1 sibling, 1 reply; 20+ messages in thread From: Jesper Juhl @ 2006-01-10 2:12 UTC (permalink / raw) To: Andi Kleen; +Cc: linux-kernel On 10 Jan 2006 02:49:13 +0100, Andi Kleen <ak@suse.de> wrote: > Jesper Juhl <jesper.juhl@gmail.com> writes: > > > > Well, first of all you'll notice that the second core shows a > > "physical id" of 127 while the first core shows an id of 0. Shouldn't > > the second core be id 1, just like the "core id" fields are 0 & 1? > > In theory it could be an uninitialized phys_proc_id (0xff >> 1), > but it could be also the BIOS just setting the local APIC of CPU 1 > to 0xff for some reason. > > If you add a printk("PHYSCPU %d %x\n", smp_processor_id(), phys_proc_id[smp_processor_id()]) > at the end of arch/x86_64/kernel/setup.c:early_identify_cpu() what does > dmesg | grep PHYSCPU output? > Not a thing since I'm using arch/i386 here (32bit distribution (Slackware), just building a 32bit kernel optimized for K8). But, I stuck that printk into identify_cpu() in arch/i386/kernel/cpu/common.c instead, and this is what I get : $ dmesg | grep PHYSCPU [ 30.323965] PHYSCPU 0 0 [ 30.402588] PHYSCPU 1 7f > > > > Second thing I find slightly odd is the lack of "sse3" in the "flags" list. > > I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3? > > Is it a case of: > > a) Me being wrong, not all Athlon 64 X2's feature SSE3? > > b) The CPU actually featuring SSE3 but Linux not taking advantage of it? > > c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo > > doesn't show that fact? > > d) Something else? > > It's called pni (prescott new instructions) for historical reasons. We added > the bit too early before Intel's marketing department could make up its > mind fully, so Linux is stuck with the old codename. > Does anything actually parse the /proc/cpuinfo flags field? are we really stuck with it? Ohh well, no big deal. -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-10 2:12 ` Jesper Juhl @ 2006-01-10 2:36 ` Andi Kleen 2006-01-10 9:29 ` Jesper Juhl 0 siblings, 1 reply; 20+ messages in thread From: Andi Kleen @ 2006-01-10 2:36 UTC (permalink / raw) To: Jesper Juhl; +Cc: linux-kernel On Tuesday 10 January 2006 03:12, Jesper Juhl wrote: > On 10 Jan 2006 02:49:13 +0100, Andi Kleen <ak@suse.de> wrote: > > Jesper Juhl <jesper.juhl@gmail.com> writes: > > > > > > Well, first of all you'll notice that the second core shows a > > > "physical id" of 127 while the first core shows an id of 0. Shouldn't > > > the second core be id 1, just like the "core id" fields are 0 & 1? > > > > In theory it could be an uninitialized phys_proc_id (0xff >> 1), > > but it could be also the BIOS just setting the local APIC of CPU 1 > > to 0xff for some reason. > > > > If you add a printk("PHYSCPU %d %x\n", smp_processor_id(), phys_proc_id[smp_processor_id()]) > > at the end of arch/x86_64/kernel/setup.c:early_identify_cpu() what does > > dmesg | grep PHYSCPU output? > > > Not a thing since I'm using arch/i386 here (32bit distribution > (Slackware), just building a 32bit kernel optimized for K8). Ah - how legacy. > But, I stuck that printk into identify_cpu() in > arch/i386/kernel/cpu/common.c instead, and this is what I get : > $ dmesg | grep PHYSCPU > [ 30.323965] PHYSCPU 0 0 > [ 30.402588] PHYSCPU 1 7f Hmm it looks like the phys_proc_id initialization is at the wrong place in 32bit. early_cpu_detect is only called on the BP, not on the AP. early_intel_workaround is also there incorrectly. Might be a mismerge - it should be one function below. The appended patch should help, but it's untested. > > > > > > > Second thing I find slightly odd is the lack of "sse3" in the "flags" list. > > > I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3? > > > Is it a case of: > > > a) Me being wrong, not all Athlon 64 X2's feature SSE3? > > > b) The CPU actually featuring SSE3 but Linux not taking advantage of it? > > > c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo > > > doesn't show that fact? > > > d) Something else? > > > > It's called pni (prescott new instructions) for historical reasons. We added > > the bit too early before Intel's marketing department could make up its > > mind fully, so Linux is stuck with the old codename. > > > Does anything actually parse the /proc/cpuinfo flags field? are we > really stuck with it? Do you really want to find out by a report from a rightfully annoyed user? I considered at some point to print sse3 in addition to pni, but then it seemed like too much bloat for only a cosmetical issue. Maybe if it becomes a popular FAQ, but it isn't that far yet. (I can just see the headlines for such a patch - "Linux 2.6.20 finally adding SSE3 support") -Andi i386: Move phys_proc_id/early intel workaround to correct function. early_cpu_detect only runs on the BP, but this code needs to run on all CPUs. Looks like a mismerge somewhere. Also add a warning comment. Signed-off-by: Andi Kleen <ak@suse.de> Index: linux/arch/i386/kernel/cpu/common.c =================================================================== --- linux.orig/arch/i386/kernel/cpu/common.c +++ linux/arch/i386/kernel/cpu/common.c @@ -204,7 +204,10 @@ static int __devinit have_cpuid_p(void) /* Do minimum CPU detection early. Fields really needed: vendor, cpuid_level, family, model, mask, cache alignment. - The others are not touched to avoid unwanted side effects. */ + The others are not touched to avoid unwanted side effects. + + WARNING: this function is only called on the BP. Don't add code here + that is supposed to run on all CPUs. */ static void __init early_cpu_detect(void) { struct cpuinfo_x86 *c = &boot_cpu_data; @@ -236,12 +239,6 @@ static void __init early_cpu_detect(void if (cap0 & (1<<19)) c->x86_cache_alignment = ((misc >> 8) & 0xff) * 8; } - - early_intel_workaround(c); - -#ifdef CONFIG_X86_HT - phys_proc_id[smp_processor_id()] = (cpuid_ebx(1) >> 24) & 0xff; -#endif } void __devinit generic_identify(struct cpuinfo_x86 * c) @@ -289,6 +286,12 @@ void __devinit generic_identify(struct c get_model_name(c); /* Default name */ } } + + early_intel_workaround(c); + +#ifdef CONFIG_X86_HT + phys_proc_id[smp_processor_id()] = (cpuid_ebx(1) >> 24) & 0xff; +#endif } static void __devinit squash_the_stupid_serial_number(struct cpuinfo_x86 *c) ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-10 2:36 ` Andi Kleen @ 2006-01-10 9:29 ` Jesper Juhl 2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad 0 siblings, 1 reply; 20+ messages in thread From: Jesper Juhl @ 2006-01-10 9:29 UTC (permalink / raw) To: Andi Kleen; +Cc: linux-kernel On 1/10/06, Andi Kleen <ak@suse.de> wrote: > On Tuesday 10 January 2006 03:12, Jesper Juhl wrote: > > On 10 Jan 2006 02:49:13 +0100, Andi Kleen <ak@suse.de> wrote: > > > Jesper Juhl <jesper.juhl@gmail.com> writes: > > > > > > > > Well, first of all you'll notice that the second core shows a > > > > "physical id" of 127 while the first core shows an id of 0. Shouldn't > > > > the second core be id 1, just like the "core id" fields are 0 & 1? > > > > > > In theory it could be an uninitialized phys_proc_id (0xff >> 1), > > > but it could be also the BIOS just setting the local APIC of CPU 1 > > > to 0xff for some reason. > > > > > > If you add a printk("PHYSCPU %d %x\n", smp_processor_id(), phys_proc_id[smp_processor_id()]) > > > at the end of arch/x86_64/kernel/setup.c:early_identify_cpu() what does > > > dmesg | grep PHYSCPU output? > > > > > Not a thing since I'm using arch/i386 here (32bit distribution > > (Slackware), just building a 32bit kernel optimized for K8). > > Ah - how legacy. > Yeah, but since my distro of choice is 32bit only and I don't much feel like porting it myself or using an unofficial port (slamd64) I'm sticking with a 32bit userspace. And as long as userspace is pure 32bit there doesn't seem to be much point in building a 64bit kernel. And I only have 2GB of RAM, so I don't have a use for the larger 64bit address space. I also don't run any apps that do a lot of math on >32bit numbers, so there's not much gain there either. I guess I would bennefit from the extra GPR's, but then I would at the same time loose a bit by all pointers being 64bit - both lose some disk space due to larger binaries and I'd have increased memory use and less efficient L1/L2 cache use. I don't think there would actually be much gain for me in switching to a 64bit kernel with a 64bit userspace atm. But if I'm wrong I'd of course love to hear about it :) > > But, I stuck that printk into identify_cpu() in > > arch/i386/kernel/cpu/common.c instead, and this is what I get : > > $ dmesg | grep PHYSCPU > > [ 30.323965] PHYSCPU 0 0 > > [ 30.402588] PHYSCPU 1 7f > > Hmm it looks like the phys_proc_id initialization is at the wrong > place in 32bit. early_cpu_detect is only called on the BP, not > on the AP. early_intel_workaround is also there incorrectly. > Might be a mismerge - it should be one function below. > > The appended patch should help, but it's untested. > It does help. Thank you Andi. Guess this should be merged. $ dmesg | grep PHYSCPU [ 34.202835] PHYSCPU 0 0 [ 34.281459] PHYSCPU 1 0 $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 35 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ stepping : 2 cpu MHz : 2200.150 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy ts fid vid ttp bogomips : 4401.86 processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 35 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ stepping : 2 cpu MHz : 2200.150 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy ts fid vid ttp bogomips : 4399.53 > > > > > > > > > > Second thing I find slightly odd is the lack of "sse3" in the "flags" list. > > > > I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3? > > > > Is it a case of: > > > > a) Me being wrong, not all Athlon 64 X2's feature SSE3? > > > > b) The CPU actually featuring SSE3 but Linux not taking advantage of it? > > > > c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo > > > > doesn't show that fact? > > > > d) Something else? > > > > > > It's called pni (prescott new instructions) for historical reasons. We added > > > the bit too early before Intel's marketing department could make up its > > > mind fully, so Linux is stuck with the old codename. > > > > > Does anything actually parse the /proc/cpuinfo flags field? are we > > really stuck with it? > > Do you really want to find out by a report from a rightfully annoyed user? No, not really. Guess you are right, it could potentially break userspace to change it now - better not to. > I considered at some point to print sse3 in addition to pni, but then > it seemed like too much bloat for only a cosmetical issue. Maybe if it > becomes a popular FAQ, but it isn't that far yet. > Right, it's fine as 'pni' for now. > (I can just see the headlines for such a patch - > "Linux 2.6.20 finally adding SSE3 support") > Hehe. > -Andi > -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html ^ permalink raw reply [flat|nested] 20+ messages in thread
* 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities 2006-01-10 9:29 ` Jesper Juhl @ 2006-01-10 20:23 ` Jeffrey Hundstad 2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang ` (2 more replies) 0 siblings, 3 replies; 20+ messages in thread From: Jeffrey Hundstad @ 2006-01-10 20:23 UTC (permalink / raw) To: Jesper Juhl; +Cc: Andi Kleen, linux-kernel Jesper Juhl wrote: >On 1/10/06, Andi Kleen <ak@suse.de> wrote: > > >>On Tuesday 10 January 2006 03:12, Jesper Juhl wrote: >> >> ... >>Ah - how legacy. >> >> >> >Yeah, but since my distro of choice is 32bit only and I don't much >feel like porting it myself or using an unofficial port (slamd64) I'm >sticking with a 32bit userspace. And as long as userspace is pure >32bit there doesn't seem to be much point in building a 64bit kernel. >And I only have 2GB of RAM, so I don't have a use for the larger 64bit >address space. >I also don't run any apps that do a lot of math on >32bit numbers, so >there's not much gain there either. >I guess I would bennefit from the extra GPR's, but then I would at the >same time loose a bit by all pointers being 64bit - both lose some >disk space due to larger binaries and I'd have increased memory use >and less efficient L1/L2 cache use. > >I don't think there would actually be much gain for me in switching to >a 64bit kernel with a 64bit userspace atm. >But if I'm wrong I'd of course love to hear about it :) > > > Has anyone done any actual benchmark tests that show 64-bit vs 32-bit environments/distributions with Athlon64 processors. If so, I love to see the results. I too elected to stick with 32-bit, using the same reasoning/guessing above. -- Jeffrey Hundstad ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities 2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad @ 2006-01-10 20:34 ` David Lang 2006-01-10 20:50 ` Jeffrey Hundstad 2006-01-10 20:55 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities Andi Kleen 2006-01-11 0:15 ` Ken Moffat 2 siblings, 1 reply; 20+ messages in thread From: David Lang @ 2006-01-10 20:34 UTC (permalink / raw) To: Jeffrey Hundstad; +Cc: Jesper Juhl, Andi Kleen, linux-kernel On Tue, 10 Jan 2006, Jeffrey Hundstad wrote: > >> On 1/10/06, Andi Kleen <ak@suse.de> wrote: >> >>> On Tuesday 10 January 2006 03:12, Jesper Juhl wrote: >>> > ... > >>> Ah - how legacy. >>> >>> >> Yeah, but since my distro of choice is 32bit only and I don't much >> feel like porting it myself or using an unofficial port (slamd64) I'm >> sticking with a 32bit userspace. And as long as userspace is pure >> 32bit there doesn't seem to be much point in building a 64bit kernel. >> And I only have 2GB of RAM, so I don't have a use for the larger 64bit >> address space. >> I also don't run any apps that do a lot of math on >32bit numbers, so >> there's not much gain there either. >> I guess I would bennefit from the extra GPR's, but then I would at the >> same time loose a bit by all pointers being 64bit - both lose some >> disk space due to larger binaries and I'd have increased memory use >> and less efficient L1/L2 cache use. >> >> I don't think there would actually be much gain for me in switching to >> a 64bit kernel with a 64bit userspace atm. >> But if I'm wrong I'd of course love to hear about it :) >> >> > > Has anyone done any actual benchmark tests that show 64-bit vs 32-bit > environments/distributions with Athlon64 processors. If so, I love to see > the results. I too elected to stick with 32-bit, using the same > reasoning/guessing above. remember that benchmarks are all dependant on your workload, but on some of my workloads (lots of fork-based network services) I've seen a 50%+ increase by switching from a 32 bit to 64 bit kernel with 32 bit userspace, and a further 50%+ increase by switching to a 64 bit userspace. remember that on amd64 systems 64 bit programs have access to twice as many registers as 32 bit programs. This can be more of a win then the extra pointer size is a loss. David Lang -- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C.A.R. Hoare ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities 2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang @ 2006-01-10 20:50 ` Jeffrey Hundstad 2006-01-10 20:53 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2cpuinfooddities David Lang 0 siblings, 1 reply; 20+ messages in thread From: Jeffrey Hundstad @ 2006-01-10 20:50 UTC (permalink / raw) To: David Lang; +Cc: Jesper Juhl, Andi Kleen, linux-kernel David Lang wrote: > On Tue, 10 Jan 2006, Jeffrey Hundstad wrote: > >> >>> On 1/10/06, Andi Kleen <ak@suse.de> wrote: >>> >>>> On Tuesday 10 January 2006 03:12, Jesper Juhl wrote: >>>> >> ... >> >>>> Ah - how legacy. >>>> >>>> >>> Yeah, but since my distro of choice is 32bit only and I don't much >>> feel like porting it myself or using an unofficial port (slamd64) I'm >>> sticking with a 32bit userspace. And as long as userspace is pure >>> 32bit there doesn't seem to be much point in building a 64bit kernel. >>> And I only have 2GB of RAM, so I don't have a use for the larger 64bit >>> address space. >>> I also don't run any apps that do a lot of math on >32bit numbers, so >>> there's not much gain there either. >>> I guess I would bennefit from the extra GPR's, but then I would at the >>> same time loose a bit by all pointers being 64bit - both lose some >>> disk space due to larger binaries and I'd have increased memory use >>> and less efficient L1/L2 cache use. >>> >>> I don't think there would actually be much gain for me in switching to >>> a 64bit kernel with a 64bit userspace atm. >>> But if I'm wrong I'd of course love to hear about it :) >>> >>> >> >> Has anyone done any actual benchmark tests that show 64-bit vs 32-bit >> environments/distributions with Athlon64 processors. If so, I love >> to see the results. I too elected to stick with 32-bit, using the >> same reasoning/guessing above. > > > remember that benchmarks are all dependant on your workload, but on > some of my workloads (lots of fork-based network services) I've seen a > 50%+ increase by switching from a 32 bit to 64 bit kernel with 32 bit > userspace, and a further 50%+ increase by switching to a 64 bit > userspace. > Thanks for your response. I'm prob. being stupid here... but does "increase" here mean faster or slower? > remember that on amd64 systems 64 bit programs have access to twice as > many registers as 32 bit programs. This can be more of a win then the > extra pointer size is a loss. If you've done other "standard" type of benchmarks between the two please post your results. Also, is there a big hit by using a nearly pure 32-bit environment + the rare 64-bit program when needed? -- Jeffrey Hundstad ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2cpuinfooddities 2006-01-10 20:50 ` Jeffrey Hundstad @ 2006-01-10 20:53 ` David Lang 0 siblings, 0 replies; 20+ messages in thread From: David Lang @ 2006-01-10 20:53 UTC (permalink / raw) To: Jeffrey Hundstad; +Cc: Jesper Juhl, Andi Kleen, linux-kernel On Tue, 10 Jan 2006, Jeffrey Hundstad wrote: > Date: Tue, 10 Jan 2006 14:50:05 -0600 > David Lang wrote: > >> On Tue, 10 Jan 2006, Jeffrey Hundstad wrote: >> >>> >>>> On 1/10/06, Andi Kleen <ak@suse.de> wrote: >>>> >>>>> On Tuesday 10 January 2006 03:12, Jesper Juhl wrote: >>>>> >>> ... >>> >>>>> Ah - how legacy. >>>>> >>>>> >>>> Yeah, but since my distro of choice is 32bit only and I don't much >>>> feel like porting it myself or using an unofficial port (slamd64) I'm >>>> sticking with a 32bit userspace. And as long as userspace is pure >>>> 32bit there doesn't seem to be much point in building a 64bit kernel. >>>> And I only have 2GB of RAM, so I don't have a use for the larger 64bit >>>> address space. >>>> I also don't run any apps that do a lot of math on >32bit numbers, so >>>> there's not much gain there either. >>>> I guess I would bennefit from the extra GPR's, but then I would at the >>>> same time loose a bit by all pointers being 64bit - both lose some >>>> disk space due to larger binaries and I'd have increased memory use >>>> and less efficient L1/L2 cache use. >>>> >>>> I don't think there would actually be much gain for me in switching to >>>> a 64bit kernel with a 64bit userspace atm. >>>> But if I'm wrong I'd of course love to hear about it :) >>>> >>>> >>> >>> Has anyone done any actual benchmark tests that show 64-bit vs 32-bit >>> environments/distributions with Athlon64 processors. If so, I love to see >>> the results. I too elected to stick with 32-bit, using the same >>> reasoning/guessing above. >> >> >> remember that benchmarks are all dependant on your workload, but on some of >> my workloads (lots of fork-based network services) I've seen a 50%+ >> increase by switching from a 32 bit to 64 bit kernel with 32 bit userspace, >> and a further 50%+ increase by switching to a 64 bit userspace. >> > > Thanks for your response. I'm prob. being stupid here... but does "increase" > here mean faster or slower? increase means faster. >> remember that on amd64 systems 64 bit programs have access to twice as many >> registers as 32 bit programs. This can be more of a win then the extra >> pointer size is a loss. > > > If you've done other "standard" type of benchmarks between the two please > post your results. Also, is there a big hit by using a nearly pure 32-bit > environment + the rare 64-bit program when needed? I haven't done other benchmarks myself, but I have seen some database benchmarks (MySQL and Postgres) on the net that showed a doubling of the database performance when going from pure 32 bit to pure 64 bit. I don't see any reason why there would be a direct performance penalty in a mixed environment (other then the fact that you may end up eating up some ram by having 32bit and 64 bit shared libraries loaded at the same time) David Lang -- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C.A.R. Hoare ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities 2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad 2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang @ 2006-01-10 20:55 ` Andi Kleen 2006-01-11 0:15 ` Ken Moffat 2 siblings, 0 replies; 20+ messages in thread From: Andi Kleen @ 2006-01-10 20:55 UTC (permalink / raw) To: Jeffrey Hundstad; +Cc: Jesper Juhl, linux-kernel > Has anyone done any actual benchmark tests that show 64-bit vs 32-bit > environments/distributions with Athlon64 processors. If so, I love to > see the results. I too elected to stick with 32-bit, using the same > reasoning/guessing above. This discussion is totally off topic on this mailing list. Please stop it right now. And if not please take me out of cc. -Andi ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities 2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad 2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang 2006-01-10 20:55 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities Andi Kleen @ 2006-01-11 0:15 ` Ken Moffat 2 siblings, 0 replies; 20+ messages in thread From: Ken Moffat @ 2006-01-11 0:15 UTC (permalink / raw) To: Jeffrey Hundstad; +Cc: Jesper Juhl, Andi Kleen, linux-kernel [-- Attachment #1: Type: TEXT/PLAIN, Size: 838 bytes --] On Tue, 10 Jan 2006, Jeffrey Hundstad wrote: > > Has anyone done any actual benchmark tests that show 64-bit vs 32-bit > environments/distributions with Athlon64 processors. If so, I love to see > the results. I too elected to stick with 32-bit, using the same > reasoning/guessing above. > Some months ago, on a 2GHz San Diego (4000+) I ran some tests using linuxfromscratch with 2.6.11.11, 1 GB PC3200, ext3, 5 runs of each (a) specific oggenc and photo manipulations in parallel 64-bit kernel, total time 246.053 to 257.601 sec, avg 250.022, std dev 4.62415 32-bit kernel, total time 247.572 to 258.963 sec, avg 252.405, std dev 4.22909 pure64, total time 172.942 to 177.532 sec, avg 174.582, std dev 1.90047 At that time, I hadn't built multilib. Ken -- das eine Mal als Tragödie, das andere Mal als Farce ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-01-10 1:49 ` Andi Kleen 2006-01-10 2:12 ` Jesper Juhl @ 2006-02-13 2:53 ` Brandon Low 2006-02-13 3:00 ` Alistair John Strachan 2006-02-13 9:20 ` Andi Kleen 1 sibling, 2 replies; 20+ messages in thread From: Brandon Low @ 2006-02-13 2:53 UTC (permalink / raw) To: Andi Kleen; +Cc: linux-kernel Did the patch that fixes the out of sync cpufreq messages make it into 2.6.15 stable series? I just acquired an athlon 64 x2 system, and was having this: Feb 12 15:33:33 [kernel] powernow-k8: error - out of sync, fix 0xa 0x2, vid 0xa 0xa Feb 12 15:33:59 [kernel] init_special_inode: bogus i_mode (300) Feb 12 15:33:59 [kernel] ReiserFS: hda8: warning: vs-13075: reiserfs_read_locked_inode: dead inode read from disk [283239 150550 0x0 SD]. This is likely to be race with knfsd. Ignore Some filesystem corruptions have occurred as a result. I'm testing 2.6.16-rc2 under the exact same conditions currently, and so far, no errors. Thanks, Brandon Low On Tue, 01/10/06 at 02:49:13 +0100, Andi Kleen wrote: > Jesper Juhl <jesper.juhl@gmail.com> writes: > > > > Well, first of all you'll notice that the second core shows a > > "physical id" of 127 while the first core shows an id of 0. Shouldn't > > the second core be id 1, just like the "core id" fields are 0 & 1? > > In theory it could be an uninitialized phys_proc_id (0xff >> 1), > but it could be also the BIOS just setting the local APIC of CPU 1 > to 0xff for some reason. > > If you add a printk("PHYSCPU %d %x\n", smp_processor_id(), phys_proc_id[smp_processor_id()]) > at the end of arch/x86_64/kernel/setup.c:early_identify_cpu() what does > dmesg | grep PHYSCPU output? > > > > > Second thing I find slightly odd is the lack of "sse3" in the "flags" list. > > I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3? > > Is it a case of: > > a) Me being wrong, not all Athlon 64 X2's feature SSE3? > > b) The CPU actually featuring SSE3 but Linux not taking advantage of it? > > c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo > > doesn't show that fact? > > d) Something else? > > It's called pni (prescott new instructions) for historical reasons. We added > the bit too early before Intel's marketing department could make up its > mind fully, so Linux is stuck with the old codename. > > -Andi > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-02-13 2:53 ` Brandon Low @ 2006-02-13 3:00 ` Alistair John Strachan 2006-02-13 9:20 ` Andi Kleen 1 sibling, 0 replies; 20+ messages in thread From: Alistair John Strachan @ 2006-02-13 3:00 UTC (permalink / raw) To: Brandon Low; +Cc: Andi Kleen, linux-kernel On Monday 13 February 2006 02:53, Brandon Low wrote: > Did the patch that fixes the out of sync cpufreq messages make it into > 2.6.15 stable series? I just acquired an athlon 64 x2 system, and was > having this: My issues with cpufreq were resolved in 2.6.16-rc2, I highly recommend that you try it, or Linus's recently pushed -rc3. -- Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Athlon 64 X2 cpuinfo oddities 2006-02-13 2:53 ` Brandon Low 2006-02-13 3:00 ` Alistair John Strachan @ 2006-02-13 9:20 ` Andi Kleen 1 sibling, 0 replies; 20+ messages in thread From: Andi Kleen @ 2006-02-13 9:20 UTC (permalink / raw) To: Brandon Low; +Cc: linux-kernel On Monday 13 February 2006 03:53, Brandon Low wrote: > Did the patch that fixes the out of sync cpufreq messages make it into > 2.6.15 stable series? I just acquired an athlon 64 x2 system, and was > having this: No it didn't. But thanks for the reminder - i will submit it right now. -Andi ^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2006-02-13 9:26 UTC | newest] Thread overview: 20+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2006-01-09 20:18 Athlon 64 X2 cpuinfo oddities Jesper Juhl 2006-01-09 20:29 ` Dave Dillow 2006-01-09 22:49 ` Jesper Juhl 2006-01-09 21:10 ` Rafael J. Wysocki 2006-01-09 22:32 ` Edmondo Tommasina 2006-01-09 22:41 ` Jesper Juhl 2006-01-09 22:49 ` Edmondo Tommasina 2006-01-10 1:49 ` Andi Kleen 2006-01-10 2:12 ` Jesper Juhl 2006-01-10 2:36 ` Andi Kleen 2006-01-10 9:29 ` Jesper Juhl 2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad 2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang 2006-01-10 20:50 ` Jeffrey Hundstad 2006-01-10 20:53 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2cpuinfooddities David Lang 2006-01-10 20:55 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities Andi Kleen 2006-01-11 0:15 ` Ken Moffat 2006-02-13 2:53 ` Brandon Low 2006-02-13 3:00 ` Alistair John Strachan 2006-02-13 9:20 ` Andi Kleen
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox