From mboxrd@z Thu Jan 1 00:00:00 1970 From: Digimer Subject: Re: [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) Date: Fri, 19 Nov 2010 12:08:30 -0500 Message-ID: <4CE6AF0E.30108@alteeve.com> References: <20101118200025.GH2754@reaktio.net> <20101118203902.GL2754@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20101118203902.GL2754@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Rudi Ahlers , xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 11/18/2010 03:39 PM, Pasi K=E4rkk=E4inen wrote: > Note the kernel reference .config has debugging stuff enabled, > so that will slow down dom0. > > -- Pasi With regard to this; I've been hoping to create a set of updated KVM vs. Xen benchmarks as=20 I've seen this asked for of late and existing data is >3 years old. I would like to get the kernel setup relatively similarly to how it will=20 be setup if/when an RPM is provided for RHEL 6. These are the DEBUG entries I found in .config from your tutorial. Which=20 are reasonable to set to n/m or just comment out? Did I miss anything=20 else I should change? Again, I'm not looking to optimize, just to get=20 closer to what the final generally available kernel will have. CONFIG_XEN_DEBUG_FS=3Dy CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=3Dy CONFIG_SLUB_DEBUG=3Dy CONFIG_HAVE_DMA_API_DEBUG=3Dy CONFIG_X86_DEBUGCTLMSR=3Dy CONFIG_PM_DEBUG=3Dy CONFIG_CPU_FREQ_DEBUG=3Dy CONFIG_CFG80211_DEBUGFS=3Dy CONFIG_MAC80211_DEBUGFS=3Dy CONFIG_DEBUG_DEVRES=3Dy CONFIG_DM_DEBUG=3Dy CONFIG_FIREWIRE_OHCI_DEBUG=3Dy CONFIG_MLX4_DEBUG=3Dy CONFIG_LIBERTAS_DEBUG=3Dy CONFIG_ATH5K_DEBUG=3Dy CONFIG_IWLWIFI_DEBUG=3Dy CONFIG_IWLWIFI_DEBUGFS=3Dy CONFIG_RT2X00_LIB_DEBUGFS=3Dy CONFIG_SND_DEBUG=3Dy CONFIG_SND_PCM_XRUN_DEBUG=3Dy CONFIG_INFINIBAND_MTHCA_DEBUG=3Dy CONFIG_INFINIBAND_IPOIB_DEBUG=3Dy CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=3Dy CONFIG_JBD2_DEBUG=3Dy CONFIG_DLM_DEBUG=3Dy CONFIG_DEBUG_FS=3Dy CONFIG_DEBUG_KERNEL=3Dy CONFIG_DEBUG_SHIRQ=3Dy CONFIG_SCHED_DEBUG=3Dy CONFIG_DEBUG_OBJECTS=3Dy CONFIG_DEBUG_OBJECTS_FREE=3Dy CONFIG_DEBUG_OBJECTS_TIMERS=3Dy CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=3D1 CONFIG_SLUB_DEBUG_ON=3Dy CONFIG_DEBUG_RT_MUTEXES=3Dy CONFIG_DEBUG_PI_LIST=3Dy CONFIG_DEBUG_SPINLOCK=3Dy CONFIG_DEBUG_MUTEXES=3Dy CONFIG_DEBUG_LOCK_ALLOC=3Dy CONFIG_DEBUG_SPINLOCK_SLEEP=3Dy CONFIG_DEBUG_BUGVERBOSE=3Dy CONFIG_DEBUG_INFO=3Dy CONFIG_DEBUG_VM=3Dy CONFIG_DEBUG_WRITECOUNT=3Dy CONFIG_DEBUG_MEMORY_INIT=3Dy CONFIG_DEBUG_LIST=3Dy CONFIG_DEBUG_SG=3Dy CONFIG_DEBUG_NOTIFIERS=3Dy CONFIG_FAULT_INJECTION_DEBUG_FS=3Dy CONFIG_DYNAMIC_DEBUG=3Dy CONFIG_DMA_API_DEBUG=3Dy CONFIG_DEBUG_STACKOVERFLOW=3Dy CONFIG_DEBUG_STACK_USAGE=3Dy CONFIG_DEBUG_RODATA=3Dy CONFIG_DEBUG_RODATA_TEST=3Dy CONFIG_DEBUG_NX_TEST=3Dm CONFIG_DEBUG_BOOT_PARAMS=3Dy CONFIG_KEYS_DEBUG_PROC_KEYS=3Dy I realize a bunch of these are for hardware that has little or nothing=20 to do with Xen. Thanks for any feedback. --=20 Digimer E-Mail: digimer@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org