From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
mikey@neuling.org, mpe@ellerman.id.au
Cc: mingo@kernel.org, miltonm@us.ibm.com, paulus@samba.org,
jniethe5@gmail.com, linux-kernel@vger.kernel.org,
fweisbec@gmail.com, naveen.n.rao@linux.vnet.ibm.com,
rogealve@br.ibm.com, linuxppc-dev@lists.ozlabs.org,
oleg@redhat.com, pedromfc@br.ibm.com, jolsa@kernel.org,
npiggin@gmail.com, peterz@infradead.org, christophe.leroy@c-s.fr
Subject: Re: [PATCH v5 00/10] powerpc/watchpoint: Enable 2nd DAWR on baremetal and powervm
Date: Mon, 27 Jul 2020 17:26:54 +1000 (AEST) [thread overview]
Message-ID: <159583477476.602200.17205445120834427421.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200723090813.303838-1-ravi.bangoria@linux.ibm.com>
On Thu, 23 Jul 2020 14:38:03 +0530, Ravi Bangoria wrote:
> Last series[1] was to add basic infrastructure support for more than
> one watchpoint on Book3S powerpc. This series actually enables the 2nd
> DAWR for baremetal and powervm. Kvm guest is still not supported.
>
> v4: https://lore.kernel.org/r/20200717040958.70561-1-ravi.bangoria@linux.ibm.com
>
> v4->v5:
> - Using hardcoded values instead of macros HBP_NUM_ONE and HBP_NUM_TWO.
> Comment above HBP_NUM_MAX changed to explain it's value.
> - Included CPU_FTR_DAWR1 into CPU_FTRS_POWER10
> - Using generic function feat_enable() instead of
> feat_enable_debug_facilities_v31() to enable CPU_FTR_DAWR1.
> - ISA still includes 512B boundary in match criteria. But that's a
> documentation mistake. Mentioned about this in the last patch.
> - Rebased to powerpc/next
> - Added Jordan's Reviewed-by/Tested-by tags
>
> [...]
Applied to powerpc/next.
[01/10] powerpc/watchpoint: Fix 512 byte boundary limit
https://git.kernel.org/powerpc/c/3190ecbfeeb2ab17778887ce3fa964615d6460fd
[02/10] powerpc/watchpoint: Fix DAWR exception constraint
https://git.kernel.org/powerpc/c/f6780ce619f8daa285760302d56e95892087bd1f
[03/10] powerpc/watchpoint: Fix DAWR exception for CACHEOP
https://git.kernel.org/powerpc/c/f3c832f1350bcf1e6906113ee3168066f4235dbe
[04/10] powerpc/watchpoint: Enable watchpoint functionality on power10 guest
https://git.kernel.org/powerpc/c/8f460a8175e6d85537d581734e9fa7ef97036b1a
[05/10] powerpc/dt_cpu_ftrs: Add feature for 2nd DAWR
https://git.kernel.org/powerpc/c/dc1cedca54704d336c333b5398daaf13b23e391b
[06/10] powerpc/watchpoint: Set CPU_FTR_DAWR1 based on pa-features bit
https://git.kernel.org/powerpc/c/8f45ca3f8b87c4810674fbfe65de6d041ee0baee
[07/10] powerpc/watchpoint: Rename current H_SET_MODE DAWR macro
https://git.kernel.org/powerpc/c/6f3fe297f95134e9b2386dae0067bf530e1ddca0
[08/10] powerpc/watchpoint: Guest support for 2nd DAWR hcall
https://git.kernel.org/powerpc/c/03f3e54abd95061ea11bdb4eedbe3cab6553704f
[09/10] powerpc/watchpoint: Return available watchpoints dynamically
https://git.kernel.org/powerpc/c/deb2bd9bcc8428d4b65b6ba640ba8b57c1b20b17
[10/10] powerpc/watchpoint: Remove 512 byte boundary
https://git.kernel.org/powerpc/c/3f31e49dc4588d396023028791e36c23235e1334
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
mikey@neuling.org, mpe@ellerman.id.au
Cc: christophe.leroy@c-s.fr, miltonm@us.ibm.com, rogealve@br.ibm.com,
peterz@infradead.org, fweisbec@gmail.com,
linux-kernel@vger.kernel.org, npiggin@gmail.com, oleg@redhat.com,
paulus@samba.org, jolsa@kernel.org, jniethe5@gmail.com,
pedromfc@br.ibm.com, naveen.n.rao@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org, mingo@kernel.org
Subject: Re: [PATCH v5 00/10] powerpc/watchpoint: Enable 2nd DAWR on baremetal and powervm
Date: Mon, 27 Jul 2020 17:26:54 +1000 (AEST) [thread overview]
Message-ID: <159583477476.602200.17205445120834427421.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200723090813.303838-1-ravi.bangoria@linux.ibm.com>
On Thu, 23 Jul 2020 14:38:03 +0530, Ravi Bangoria wrote:
> Last series[1] was to add basic infrastructure support for more than
> one watchpoint on Book3S powerpc. This series actually enables the 2nd
> DAWR for baremetal and powervm. Kvm guest is still not supported.
>
> v4: https://lore.kernel.org/r/20200717040958.70561-1-ravi.bangoria@linux.ibm.com
>
> v4->v5:
> - Using hardcoded values instead of macros HBP_NUM_ONE and HBP_NUM_TWO.
> Comment above HBP_NUM_MAX changed to explain it's value.
> - Included CPU_FTR_DAWR1 into CPU_FTRS_POWER10
> - Using generic function feat_enable() instead of
> feat_enable_debug_facilities_v31() to enable CPU_FTR_DAWR1.
> - ISA still includes 512B boundary in match criteria. But that's a
> documentation mistake. Mentioned about this in the last patch.
> - Rebased to powerpc/next
> - Added Jordan's Reviewed-by/Tested-by tags
>
> [...]
Applied to powerpc/next.
[01/10] powerpc/watchpoint: Fix 512 byte boundary limit
https://git.kernel.org/powerpc/c/3190ecbfeeb2ab17778887ce3fa964615d6460fd
[02/10] powerpc/watchpoint: Fix DAWR exception constraint
https://git.kernel.org/powerpc/c/f6780ce619f8daa285760302d56e95892087bd1f
[03/10] powerpc/watchpoint: Fix DAWR exception for CACHEOP
https://git.kernel.org/powerpc/c/f3c832f1350bcf1e6906113ee3168066f4235dbe
[04/10] powerpc/watchpoint: Enable watchpoint functionality on power10 guest
https://git.kernel.org/powerpc/c/8f460a8175e6d85537d581734e9fa7ef97036b1a
[05/10] powerpc/dt_cpu_ftrs: Add feature for 2nd DAWR
https://git.kernel.org/powerpc/c/dc1cedca54704d336c333b5398daaf13b23e391b
[06/10] powerpc/watchpoint: Set CPU_FTR_DAWR1 based on pa-features bit
https://git.kernel.org/powerpc/c/8f45ca3f8b87c4810674fbfe65de6d041ee0baee
[07/10] powerpc/watchpoint: Rename current H_SET_MODE DAWR macro
https://git.kernel.org/powerpc/c/6f3fe297f95134e9b2386dae0067bf530e1ddca0
[08/10] powerpc/watchpoint: Guest support for 2nd DAWR hcall
https://git.kernel.org/powerpc/c/03f3e54abd95061ea11bdb4eedbe3cab6553704f
[09/10] powerpc/watchpoint: Return available watchpoints dynamically
https://git.kernel.org/powerpc/c/deb2bd9bcc8428d4b65b6ba640ba8b57c1b20b17
[10/10] powerpc/watchpoint: Remove 512 byte boundary
https://git.kernel.org/powerpc/c/3f31e49dc4588d396023028791e36c23235e1334
cheers
next prev parent reply other threads:[~2020-07-27 7:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 9:08 [PATCH v5 00/10] powerpc/watchpoint: Enable 2nd DAWR on baremetal and powervm Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 01/10] powerpc/watchpoint: Fix 512 byte boundary limit Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 02/10] powerpc/watchpoint: Fix DAWR exception constraint Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 03/10] powerpc/watchpoint: Fix DAWR exception for CACHEOP Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 04/10] powerpc/watchpoint: Enable watchpoint functionality on power10 guest Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 05/10] powerpc/dt_cpu_ftrs: Add feature for 2nd DAWR Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 06/10] powerpc/watchpoint: Set CPU_FTR_DAWR1 based on pa-features bit Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 07/10] powerpc/watchpoint: Rename current H_SET_MODE DAWR macro Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 08/10] powerpc/watchpoint: Guest support for 2nd DAWR hcall Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 09/10] powerpc/watchpoint: Return available watchpoints dynamically Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-23 9:08 ` [PATCH v5 10/10] powerpc/watchpoint: Remove 512 byte boundary Ravi Bangoria
2020-07-23 9:08 ` Ravi Bangoria
2020-07-27 7:26 ` Michael Ellerman [this message]
2020-07-27 7:26 ` [PATCH v5 00/10] powerpc/watchpoint: Enable 2nd DAWR on baremetal and powervm Michael Ellerman
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=159583477476.602200.17205445120834427421.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=christophe.leroy@c-s.fr \
--cc=fweisbec@gmail.com \
--cc=jniethe5@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=miltonm@us.ibm.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=paulus@samba.org \
--cc=pedromfc@br.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=rogealve@br.ibm.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.