From: INAKOSHI Hiroya <inakoshi.hiroya@jp.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xentrace event mask for memory management class
Date: Thu, 31 Aug 2006 09:26:55 +0900 [thread overview]
Message-ID: <44F62CCF.1070501@jp.fujitsu.com> (raw)
In-Reply-To: <44E543E2.5050906@jp.fujitsu.com>
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 <inakoshi.hiroya@jp.fujitsu.com>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
富士通株式会社 プラットフォーム技術開発本部 仮想システム開発統括部
稲越宏弥 <inakoshi.hiroya@jp.fujitsu.com>
prev parent reply other threads:[~2006-08-31 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 4:36 [PATCH] xentrace event mask for memory management class INAKOSHI Hiroya
2006-08-18 12:59 ` Mark Williamson
2006-08-31 0:26 ` INAKOSHI Hiroya [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F62CCF.1070501@jp.fujitsu.com \
--to=inakoshi.hiroya@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.