On Tue, May 28, 2019 at 08:51:26AM -0600, Mathieu Poirier wrote:
> Good day,
>
> On Tue, May 28, 2019 at 01:19:24PM +0800, Leo Yan wrote:
> > Hi Suzuki,
> >
> > On Wed, May 22, 2019 at 11:34:33AM +0100, Suzuki K Poulose wrote:
> > > This series adds the support for CoreSight devices on ACPI based
Hi Mathieu,
On 28/05/2019 18:36, Mathieu Poirier wrote:
On Tue, 28 May 2019 at 11:32, Mathieu Poirier
wrote:
...
I have applied this set.
Thanks.
As Leo pointed out it would be interesting to update the documentation
in "Documentation/trace/coresight.txt".
I am on it, will send it
On Tue, 28 May 2019 at 11:32, Mathieu Poirier
wrote:
>
> On Wed, 22 May 2019 at 04:35, Suzuki K Poulose wrote:
> >
> > This series adds the support for CoreSight devices on ACPI based
> > platforms. The device connections are encoded as _DSD graph property[0],
> > with CoreSight specific extensio
On Wed, 22 May 2019 at 04:35, Suzuki K Poulose wrote:
>
> This series adds the support for CoreSight devices on ACPI based
> platforms. The device connections are encoded as _DSD graph property[0],
> with CoreSight specific extensions to indicate the direction of data
> flow as described in [1]. C
Good day,
On Tue, May 28, 2019 at 01:19:24PM +0800, Leo Yan wrote:
> Hi Suzuki,
>
> On Wed, May 22, 2019 at 11:34:33AM +0100, Suzuki K Poulose wrote:
> > This series adds the support for CoreSight devices on ACPI based
> > platforms. The device connections are encoded as _DSD graph property[0],
>
Hi Suzuki, Mathieu,
On Tue, May 28, 2019 at 01:19:24PM +0800, Leo Yan wrote:
[...]
> After I applied this patch set, I found all device names under
> '/sys/bus/event_source/devices/cs_etm/sinks/' have been changed as
> below on my DB410c board:
> # ls /sys/bus/event_source/devices/cs_etm/sinks/
Hi Suzuki,
On Wed, May 22, 2019 at 11:34:33AM +0100, Suzuki K Poulose wrote:
> This series adds the support for CoreSight devices on ACPI based
> platforms. The device connections are encoded as _DSD graph property[0],
> with CoreSight specific extensions to indicate the direction of data
> flow a
Hi Suzuki, Leo
On Thu, 23 May 2019 at 16:32, Suzuki K Poulose wrote:
>
> Hi Leo,
>
> On 23/05/2019 15:32, Leo Yan wrote:
> > Hi Suzuki,
> >
> > On Wed, May 22, 2019 at 11:34:33AM +0100, Suzuki K Poulose wrote:
> >
> > [...]
> >
> >> Changes since v2:
> >> - Drop the patches exposing device link
Hi Suzuki,
On Thu, May 23, 2019 at 04:31:54PM +0100, Suzuki K Poulose wrote:
[...]
> > When you send out the new patch for exposing device connection, please
> > loop me so that I can base on it for perf testing related works.
>
> Sure, will do.
Thanks a lot!
> As such, the perf testing shoul
Hi Leo,
On 23/05/2019 15:32, Leo Yan wrote:
Hi Suzuki,
On Wed, May 22, 2019 at 11:34:33AM +0100, Suzuki K Poulose wrote:
[...]
Changes since v2:
- Drop the patches exposing device links via sysfs, to be posted as separate
series.
Thanks for sharing the git tree linkage in another ema
Hi Suzuki,
On Wed, May 22, 2019 at 11:34:33AM +0100, Suzuki K Poulose wrote:
[...]
> Changes since v2:
> - Drop the patches exposing device links via sysfs, to be posted as separate
>series.
Thanks for sharing the git tree linkage in another email. Just want
to confirm, since patch set v3
On 22/05/2019 11:34, Suzuki K Poulose wrote:
This series adds the support for CoreSight devices on ACPI based
platforms. The device connections are encoded as _DSD graph property[0],
with CoreSight specific extensions to indicate the direction of data
flow as described in [1]. Components attac
This series adds the support for CoreSight devices on ACPI based
platforms. The device connections are encoded as _DSD graph property[0],
with CoreSight specific extensions to indicate the direction of data
flow as described in [1]. Components attached to CPUs are listed
as child devices of the cor
13 matches
Mail list logo
