All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Amitabha Roy <amitabha.roy@gmail.com>
Cc: Xen developers mailing list <xen-devel@lists.xensource.com>,
	"Santos, Jose Renato G" <joserenato.santos@hp.com>
Subject: Re: [PATCH] Add callgraph support to Xenoprofile
Date: Thu, 07 Jun 2007 10:30:38 +0100	[thread overview]
Message-ID: <C28D8ECE.103A3%keir@xensource.com> (raw)
In-Reply-To: <cf9d85500706070220x2be9afb4r949b22fd59bf2c26@mail.gmail.com>

On 7/6/07 10:20, "Amitabha Roy" <amitabha.roy@gmail.com> wrote:

> Coding style is likely because I've preserved the formatting of the
> original files (esp. of backtrace.c from Linux for simple diffs).
> There isnt a consistent style across the files that I could follow.

Linux-derived files follow Linux style (this will apply to many of the files
under arch/x86/oprofile). Xen-specific files follow Xen style as in e.g.,
page_alloc.c, xmalloc.c, xenoprof.c).

If any of the files you edit don't follow this, please fix them first, and
send a separate patch as a prerequisite for your own.

> CONFIG_FRAME_POINTER gets used in config/StdGNU.mk.
> I simply followed whatever was done for XEN_TARGET_X86_PAE. However
> unlike the PAE case I haven't ensured that frame pointers are turned
> on both in the kernel and Xen. If you want I can move all the frame
> pointer related stuff into xen/Rules.mk.

Yes, please. Call the option frame_pointer, in line with other Xen-specific
options which are also lower case.

 -- Keir

  reply	other threads:[~2007-06-07  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07  3:34 [PATCH] Add callgraph support to Xenoprofile Amitabha Roy
2007-06-07  9:01 ` Keir Fraser
2007-06-07  9:20   ` Amitabha Roy
2007-06-07  9:30     ` Keir Fraser [this message]
2007-06-07 11:45       ` Amitabha Roy
2007-06-07 11:46         ` Amitabha Roy

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=C28D8ECE.103A3%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=amitabha.roy@gmail.com \
    --cc=joserenato.santos@hp.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.