All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: John Garry <john.garry@huawei.com>
Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>,
	will.deacon@arm.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, anurup.m@huawei.com,
	tanxiaojun@huawei.com, xuwei5@hisilicon.com,
	sanil.kumar@hisilicon.com, gabriele.paoloni@huawei.com,
	shiju.jose@huawei.com, huangdaode@hisilicon.com,
	linuxarm@huawei.com, shyju.pv@huawei.com, anurupvasu@gmail.com
Subject: Re: [PATCH v8 6/9] drivers: perf: hisi: Add support for Hisilicon Djtag driver
Date: Fri, 9 Jun 2017 17:45:53 +0100	[thread overview]
Message-ID: <20170609164553.GB3043@leverpostej> (raw)
In-Reply-To: <e120463d-2936-90ec-8aad-f0f7be558054@huawei.com>

On Fri, Jun 09, 2017 at 05:09:25PM +0100, John Garry wrote:
> At this point, we would rather concentrate on our new chipset, which
> is based on same perf HW architecture (so much code reuse), but uses
> directly mapped registers and *no djtag* - in this, most of the
> upstream effort from all parties is not wasted.

FWIW, I suspect the MMIO-based PMU is going to have a smoother path
upstream, assuming it's not shared with other agents (and we don't have
another locking scheme to contend with).

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 6/9] drivers: perf: hisi: Add support for Hisilicon Djtag driver
Date: Fri, 9 Jun 2017 17:45:53 +0100	[thread overview]
Message-ID: <20170609164553.GB3043@leverpostej> (raw)
In-Reply-To: <e120463d-2936-90ec-8aad-f0f7be558054@huawei.com>

On Fri, Jun 09, 2017 at 05:09:25PM +0100, John Garry wrote:
> At this point, we would rather concentrate on our new chipset, which
> is based on same perf HW architecture (so much code reuse), but uses
> directly mapped registers and *no djtag* - in this, most of the
> upstream effort from all parties is not wasted.

FWIW, I suspect the MMIO-based PMU is going to have a smoother path
upstream, assuming it's not shared with other agents (and we don't have
another locking scheme to contend with).

Thanks,
Mark.

  reply	other threads:[~2017-06-09 16:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 12:48 [PATCH v8 6/9] drivers: perf: hisi: Add support for Hisilicon Djtag driver Shaokun Zhang
2017-05-22 12:48 ` Shaokun Zhang
2017-06-08 16:35 ` Mark Rutland
2017-06-08 16:35   ` Mark Rutland
2017-06-09 14:18   ` John Garry
2017-06-09 14:18     ` John Garry
2017-06-09 14:30     ` Will Deacon
2017-06-09 14:30       ` Will Deacon
2017-06-09 15:10       ` John Garry
2017-06-09 15:10         ` John Garry
2017-06-14 10:06         ` Will Deacon
2017-06-14 10:06           ` Will Deacon
2017-06-14 10:42           ` Mark Rutland
2017-06-14 10:42             ` Mark Rutland
2017-06-14 10:50             ` Mark Rutland
2017-06-14 10:50               ` Mark Rutland
2017-06-14 11:01             ` Will Deacon
2017-06-14 11:01               ` Will Deacon
2017-06-14 11:35               ` John Garry
2017-06-14 11:35                 ` John Garry
2017-06-14 11:40                 ` Will Deacon
2017-06-14 11:40                   ` Will Deacon
2017-06-14 11:59                   ` John Garry
2017-06-14 11:59                     ` John Garry
2017-06-14 10:48           ` Russell King - ARM Linux
2017-06-14 10:48             ` Russell King - ARM Linux
2017-06-14 11:06             ` Will Deacon
2017-06-14 11:06               ` Will Deacon
2017-06-09 15:44     ` Mark Rutland
2017-06-09 15:44       ` Mark Rutland
2017-06-09 16:09       ` John Garry
2017-06-09 16:09         ` John Garry
2017-06-09 16:45         ` Mark Rutland [this message]
2017-06-09 16:45           ` Mark Rutland
2017-06-14  8:11   ` Zhangshaokun
2017-06-14  8:11     ` Zhangshaokun

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=20170609164553.GB3043@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=anurup.m@huawei.com \
    --cc=anurupvasu@gmail.com \
    --cc=gabriele.paoloni@huawei.com \
    --cc=huangdaode@hisilicon.com \
    --cc=john.garry@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=sanil.kumar@hisilicon.com \
    --cc=shiju.jose@huawei.com \
    --cc=shyju.pv@huawei.com \
    --cc=tanxiaojun@huawei.com \
    --cc=will.deacon@arm.com \
    --cc=xuwei5@hisilicon.com \
    --cc=zhangshaokun@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.