xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Rapolu <nrapolu@purdue.edu>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL)
Date: Thu, 15 Apr 2010 12:46:01 -0400	[thread overview]
Message-ID: <4BC742C9.7060100@purdue.edu> (raw)
In-Reply-To: <4BC71A63.90302@eu.citrix.com>

Hello George,

I am trying to get linux "perf" tool work with Xen(Virtualize PMU to 
measure hardware events from inside guests).
I have the following options :

   1. allowing the guest kernel to see the PMU hardware features via
      cpuid, and then doing whatever is necessary to make them work as
      expected (by instruction emulation, etc), or
   2. keeping them hidden, but adding a new Xen interface and the
      appropriate Linux-side code to detect that interface and use it


Does Xenalyze have any code relevant to this ? Can you think of any 
directions in this regard ?

Thanks,
Naresh Rapolu.


George Dunlap wrote:
> I have not measured cache / TLB misses with this workload yet.  In the 
> past I've instrumented the scheduler trace records in Xen to include 
> performance counters such as instructions executed and cache / tlb 
> misses, and then used xenalyze 
> (http://xenbits.xensource.com/ext/xenalyze.hg) to analyze them.  But 
> the functionality for both capture and analysis was never standardized 
> or added to mainline.
>
> I'd be happy to help point you in the right direction if you're 
> interested in investing in that approach. :-)
>
> -George
>
> Naresh Rapolu wrote:
>> Hello George,
>>
>> How did you measure  Cache/ TLB misses etc while using/profiling this 
>> new scheduler ?  Any tool that you`ve used which works with Xen ?
>>
>> Thanks,
>> Naresh Rapolu.
>> PhD Student, Computer Science,
>> Purdue University.
>>
>> George Dunlap wrote:
>>  
>>> This patch series introduces the credit2 scheduler.  The first two 
>>> patches
>>> introduce changes necessary to allow the credit2 shared runqueue 
>>> functionality
>>> to work properly; the last two implement the functionality itself.
>>>
>>> The scheduler is still in the experimental phase.  There's lots of 
>>> opportunity to contribute with independent lines of development; email
>>> George Dunlap <george.dunlap@eu.citrix.com> or check out the wiki page
>>> http://wiki.xensource.com/xenwiki/Credit2_Scheduler_Development for 
>>> ideas
>>> and status updates.
>>>
>>> 19 files changed, 1453 insertions(+), 21 deletions(-)
>>> tools/libxc/Makefile                      |    1 
>>> tools/libxc/xc_csched2.c                  |   50 +
>>> tools/libxc/xenctrl.h                     |    8 
>>> tools/python/xen/lowlevel/xc/xc.c         |   58 +
>>> tools/python/xen/xend/XendAPI.py          |    3 
>>> tools/python/xen/xend/XendDomain.py       |   54 +
>>> tools/python/xen/xend/XendDomainInfo.py   |    4 
>>> tools/python/xen/xend/XendNode.py         |    4 
>>> tools/python/xen/xend/XendVMMetrics.py    |    1 
>>> tools/python/xen/xend/server/SrvDomain.py |   14 
>>> tools/python/xen/xm/main.py               |   82 ++
>>> xen/arch/ia64/vmx/vmmu.c                  |    6 
>>> xen/common/Makefile                       |    1 
>>> xen/common/sched_credit.c                 |    8 
>>> xen/common/sched_credit2.c                | 1125 
>>> +++++++++++++++++++++++++++++
>>> xen/common/schedule.c                     |   22 
>>> xen/include/public/domctl.h               |    4 
>>> xen/include/public/trace.h                |    1 
>>> xen/include/xen/sched-if.h                |   28
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>       
>>
>>   
>

  reply	other threads:[~2010-04-15 16:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 10:26 [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL) George Dunlap
2010-04-14 10:26 ` [PATCH 1 of 5] credit2: Add context_saved scheduler callback George Dunlap
2010-04-14 10:26 ` [PATCH 2 of 5] credit2: Flexible cpu-to-schedule-spinlock mappings George Dunlap
2010-04-14 10:26 ` [PATCH 3 of 5] credit2: Add a scheduler-specific schedule trace class George Dunlap
2010-04-14 10:26 ` [PATCH 4 of 5] credit2: Add credit2 scheduler to hypervisor George Dunlap
2010-04-14 10:26 ` [PATCH 5 of 5] credit2: Add toolstack options to control credit2 scheduler parameters George Dunlap
     [not found] ` <7db7f696-1f0b-44d0-8f7b-eea1be5167dd@default>
2010-04-14 14:29   ` [PATCH 0 of 5] Add credit2 scheduler (EXPERIMENTAL) George Dunlap
2010-04-14 14:52     ` Keir Fraser
2010-04-14 15:59       ` Dan Magenheimer
2010-04-14 16:23         ` Keir Fraser
2010-04-14 16:31           ` Dulloor
2010-04-14 16:36             ` Keir Fraser
2010-04-14 17:04               ` Dan Magenheimer
2010-04-14 16:46           ` Dan Magenheimer
2010-04-15 20:11     ` Dan Magenheimer
     [not found] ` <4BC664E1.7090304@purdue.edu>
2010-04-15 13:53   ` George Dunlap
2010-04-15 16:46     ` Naresh Rapolu [this message]
2010-04-15 17:33       ` Dulloor
2010-04-15 18:57         ` Naresh Rapolu
     [not found] ` <h2x940bcfd21004140841kcdffe330xff5d749d43392fe3@mail.gmail.com>
2010-04-15 14:17   ` George Dunlap
2010-04-17 20:29     ` Dulloor

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=4BC742C9.7060100@purdue.edu \
    --to=nrapolu@purdue.edu \
    --cc=george.dunlap@eu.citrix.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 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).