From: Pablo Llopis <pllopis@arcos.inf.uc3m.es>
To: Wei Liu <wei.liu2@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Crash/trace when starting oprofile
Date: Wed, 28 Mar 2012 22:59:45 +0200 [thread overview]
Message-ID: <CAL08nMG=JjD7ffW9xBAnL54B-fv-EZ6aZULrjpSOLcdENRFUsA@mail.gmail.com> (raw)
In-Reply-To: <1332949412.2485.109.camel@leeds.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
Thank you, I will try Michael's patches on a vanilla 3.0 or 3.2 kernel and
report back.
However, on first sight the patches enable profiling on unprivileged guests
(although the author calls it passive profiling, which as far as I know is
the opposite), and I am trying to do unprivileged dom0 profiling. Lets hope
this helps!
On Wed, Mar 28, 2012 at 5:43 PM, Wei Liu
<wei.liu2@citrix.com<javascript:_e({}, 'cvml',
'wei.liu2@citrix.com');>
> wrote:
> On Wed, 2012-03-28 at 15:55 +0100, Pablo Llopis wrote:
> > Hello Xen developers,
> >
> >
> > I sent a similar message to xen-users about a week ago, did not obtain
> > any response and only now realized that I should have sent this here
> > instead (http://xenoprof.sourceforge.net/ says to write to this list).
> > Apologies if you see this message twice.
> >
>
> There are some patches floating around on xen-devel:
>
> http://marc.info/?l=xen-devel&m=132779518918042&w=2
> http://marc.info/?l=xen-devel&m=132708552318073&w=2
>
>
>
> Wei.
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1667 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-03-28 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 14:55 Crash/trace when starting oprofile Pablo Llopis
2012-03-28 15:43 ` Wei Liu
2012-03-28 20:59 ` Pablo Llopis [this message]
2012-04-02 21:53 ` Pablo Llopis
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='CAL08nMG=JjD7ffW9xBAnL54B-fv-EZ6aZULrjpSOLcdENRFUsA@mail.gmail.com' \
--to=pllopis@arcos.inf.uc3m.es \
--cc=wei.liu2@citrix.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).