From mboxrd@z Thu Jan 1 00:00:00 1970 From: INAKOSHI Hiroya Subject: Re: [PATCH] xentrace event mask for memory management class Date: Thu, 31 Aug 2006 09:26:55 +0900 Message-ID: <44F62CCF.1070501@jp.fujitsu.com> References: <44E543E2.5050906@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <44E543E2.5050906@jp.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi, The patch for xentrace I posted has not been applied yet. This patch is just for correcting a typo, as Mark said, and is harmless. Please apply. Thanks. Hiroya. INAKOSHI Hiroya wrote: > Since TRC_MEM is defined as 0x000af000 in xen/include/public/trace.h, > TRC_MEM = TRC_SCHED | TRC_VMX. I feel strange about this. I do not > think scheduling is a part of memory management. Am I right? > > If not, please tell me the background TRC_MEM is defined as TRC_SCHED > | TRC_VMX. If so, please apply this patch. > > This patch defines TRC_MEM as an independent event mask. In addition, > xentrace accepts '-e mem' option so that it puts memory management > events in trace buffers. The manual page (xentrace.8) is also > modified accordingly. > > Tested by compiling on x86 and ia64, booting Dom0 and DomU, taking a > xentrace log with '-e mem' option. > > Signed-off-by: Hiroya INAKOSHI > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel -- 富士通株式会社　プラットフォーム技術開発本部　仮想システム開発統括部 稲越宏弥