xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Demon King <kdmxen@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: what the meaning of the per cpu variable cpu_core_mask and cpu_sibling_mask?
Date: Sat, 23 Mar 2013 04:17:29 +0100	[thread overview]
Message-ID: <1364008649.23963.24.camel@Abyss> (raw)
In-Reply-To: <CAH+sev=sK5i3m8xq=TGatgJaJGYC3jAq9DfQr8UGd08CXmuesw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 599 bytes --]

On gio, 2013-03-21 at 21:49 +0800, Demon King wrote:
> Thank you very much !
> 
> Thanks to your tools, I now understand how to trace some variable in
> the source code.
>
cscope is also your friend:

cd <xen-source-tree>
cscope -R

And for everything else:

man cscope
http://cscope.sourceforge.net/

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2013-03-23  3:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21  9:53 what the meaning of the per cpu variable cpu_core_mask and cpu_sibling_mask? Demon King
2013-03-21 12:12 ` George Dunlap
2013-03-21 13:49   ` Demon King
2013-03-21 14:26     ` George Dunlap
2013-03-23  3:17     ` Dario Faggioli [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=1364008649.23963.24.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=kdmxen@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).