From: Ben Sanda <Ben.Sanda@dornerworks.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Paul Sujkov <psujkov@gmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/6] Flask: Support for ARM xentrace
Date: Mon, 28 Mar 2016 15:52:25 +0000 [thread overview]
Message-ID: <A2A949C387F3A54C9B4DAC2DCD2E9A85E3335CD6@Quimby.dw.local> (raw)
In-Reply-To: <20160325192732.GA14689@char.us.oracle.com>
Konrad,
> Modified to provide support for xentrace on the ARM platform. Added
> flask credential to allow dom0 dom_xen mapping and write access for
> trace buffers.
>>
>> So .. what does that mean?
>>
>> Is that something xentrace requests? Why is this ARM specific?
>> Looking at xsm_sysctl and how the trace is setup it checks for
>> XEN__TBUFCONTROL?
I need to bring in Paul for this conversation. The Flask modifications
were originally made by him so I'm not sure on their exact purpose
or derivation.
Paul: Can you provide any insight as to the changes to the Flask code?
Thanks,
Ben
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-28 15:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:51 [PATCH 0/6] xentrace/xenalyze support on ARM Benjamin Sanda
2016-03-16 20:51 ` [PATCH 1/6] Flask: Support for ARM xentrace Benjamin Sanda
2016-03-17 14:56 ` Julien Grall
2016-03-17 15:03 ` Julien Grall
2016-03-25 19:27 ` Konrad Rzeszutek Wilk
2016-03-28 15:52 ` Ben Sanda [this message]
2016-03-16 20:51 ` [PATCH 2/6] xenalyze: Support for ARM platform Benjamin Sanda
2016-03-16 20:59 ` Andrew Cooper
2016-03-17 10:39 ` George Dunlap
2016-03-16 20:51 ` [PATCH 3/6] xentrace: P2M lookup suport " Benjamin Sanda
2016-03-17 16:21 ` Julien Grall
2016-03-28 18:55 ` Ben Sanda
2016-03-30 18:38 ` Julien Grall
2016-03-16 20:51 ` [PATCH 4/6] xentrace: ARM platform DOMID_XEN mapping support Benjamin Sanda
2016-03-17 15:53 ` Julien Grall
2016-03-16 20:51 ` [PATCH 5/6] xentrace: Trace buffer support for ARM platform Benjamin Sanda
2016-03-16 20:51 ` [PATCH 6/6] xentrace: ARM platform timestamp support Benjamin Sanda
2016-03-25 19:31 ` Konrad Rzeszutek Wilk
2016-03-31 16:38 ` Stefano Stabellini
2016-03-31 16:44 ` Ben Sanda
2016-04-01 13:05 ` Stefano Stabellini
2016-03-17 15:00 ` [PATCH 0/6] xentrace/xenalyze support on ARM Julien Grall
2016-03-17 16:50 ` Ben Sanda
2016-03-17 17:01 ` Julien Grall
2016-03-17 17:04 ` Ben Sanda
2016-03-18 17:12 ` Wei Liu
2016-03-17 17:23 ` George Dunlap
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=A2A949C387F3A54C9B4DAC2DCD2E9A85E3335CD6@Quimby.dw.local \
--to=ben.sanda@dornerworks.com \
--cc=konrad.wilk@oracle.com \
--cc=psujkov@gmail.com \
--cc=xen-devel@lists.xenproject.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).