From: Michael Ellerman <mpe@ellerman.id.au>
To: Frederic Weisbecker <frederic@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Joel Fernandes <joel.opensrc@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Chris Zankel <chris@zankel.net>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will.deacon@arm.com>, Rich Felker <dalias@libc.org>,
Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [PATCH 04/12] powerpc: Implement hw_breakpoint_arch_parse()
Date: Thu, 24 May 2018 12:01:52 +1000 [thread overview]
Message-ID: <87fu2hstf3.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1526697950-7091-5-git-send-email-frederic@kernel.org>
Frederic Weisbecker <frederic@kernel.org> writes:
> diff --git a/arch/powerpc/kernel/hw_breakpoint.c b/arch/powerpc/kernel/hw_breakpoint.c
> index 348cac9..fba6527 100644
> --- a/arch/powerpc/kernel/hw_breakpoint.c
> +++ b/arch/powerpc/kernel/hw_breakpoint.c
> @@ -139,30 +139,31 @@ int arch_bp_generic_fields(int type, int *gen_bp_type)
> /*
> * Validate the arch-specific HW Breakpoint register settings
> */
> -int arch_validate_hwbkpt_settings(struct perf_event *bp)
> +int hw_breakpoint_arch_parse(struct perf_event *bp,
> + struct perf_event_attr *attr,
> + struct arch_hw_breakpoint *hw)
I think the semantics here are that we are reading from bp/attr and
writing to hw?
If so would some sprinkling of const on the first two parameters help
make that clearer?
> {
> int ret = -EINVAL, length_max;
> - struct arch_hw_breakpoint *info = counter_arch_bp(bp);
>
> if (!bp)
> return ret;
>
> - info->type = HW_BRK_TYPE_TRANSLATE;
> - if (bp->attr.bp_type & HW_BREAKPOINT_R)
> - info->type |= HW_BRK_TYPE_READ;
> - if (bp->attr.bp_type & HW_BREAKPOINT_W)
> - info->type |= HW_BRK_TYPE_WRITE;
> - if (info->type == HW_BRK_TYPE_TRANSLATE)
> + hw->type = HW_BRK_TYPE_TRANSLATE;
> + if (attr->bp_type & HW_BREAKPOINT_R)
> + hw->type |= HW_BRK_TYPE_READ;
> + if (attr->bp_type & HW_BREAKPOINT_W)
> + hw->type |= HW_BRK_TYPE_WRITE;
> + if (hw->type == HW_BRK_TYPE_TRANSLATE)
> /* must set alteast read or write */
> return ret;
> - if (!(bp->attr.exclude_user))
> - info->type |= HW_BRK_TYPE_USER;
> - if (!(bp->attr.exclude_kernel))
> - info->type |= HW_BRK_TYPE_KERNEL;
> - if (!(bp->attr.exclude_hv))
> - info->type |= HW_BRK_TYPE_HYP;
> - info->address = bp->attr.bp_addr;
> - info->len = bp->attr.bp_len;
> + if (!attr->exclude_user)
> + hw->type |= HW_BRK_TYPE_USER;
> + if (!attr->exclude_kernel)
> + hw->type |= HW_BRK_TYPE_KERNEL;
> + if (!attr->exclude_hv)
> + hw->type |= HW_BRK_TYPE_HYP;
> + hw->address = attr->bp_addr;
> + hw->len = attr->bp_len;
All looks right to me.
> /*
> * Since breakpoint length can be a maximum of HW_BREAKPOINT_LEN(8)
> @@ -176,12 +177,12 @@ int arch_validate_hwbkpt_settings(struct perf_event *bp)
> if (cpu_has_feature(CPU_FTR_DAWR)) {
> length_max = 512 ; /* 64 doublewords */
> /* DAWR region can't cross 512 boundary */
> - if ((bp->attr.bp_addr >> 10) !=
> - ((bp->attr.bp_addr + bp->attr.bp_len - 1) >> 10))
> + if ((attr->bp_addr >> 10) !=
> + ((attr->bp_addr + attr->bp_len - 1) >> 10))
> return -EINVAL;
This will conflict with my next branch, but it should be easy enough to
resolve.
> }
> - if (info->len >
> - (length_max - (info->address & HW_BREAKPOINT_ALIGN)))
> + if (hw->len >
> + (length_max - (hw->address & HW_BREAKPOINT_ALIGN)))
> return -EINVAL;
> return 0;
> }
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
cheers
next prev parent reply other threads:[~2018-05-24 2:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 2:45 [PATCH 00/12] breakpoint: Rework arch validation v2 Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 01/12] perf/breakpoint: Split attribute parse and commit Frederic Weisbecker
2018-05-24 1:56 ` Michael Ellerman
2018-05-25 13:58 ` Frederic Weisbecker
2018-05-28 11:29 ` Michael Ellerman
2018-05-19 2:45 ` [PATCH 02/12] perf/breakpoint: Pass arch breakpoint struct to arch_check_bp_in_kernelspace() Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 03/12] x86: Implement hw_breakpoint_arch_parse() Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 04/12] powerpc: " Frederic Weisbecker
2018-05-24 2:01 ` Michael Ellerman [this message]
2018-05-25 14:05 ` Frederic Weisbecker
2018-05-28 11:31 ` Michael Ellerman
2018-06-01 14:46 ` Frederic Weisbecker
2018-06-05 11:06 ` Michael Ellerman
2018-05-19 2:45 ` [PATCH 05/12] arm: " Frederic Weisbecker
2018-05-25 12:18 ` Mark Rutland
2018-05-19 2:45 ` [PATCH 06/12] arm64: " Frederic Weisbecker
2018-05-23 15:23 ` Will Deacon
2018-05-25 12:18 ` Mark Rutland
2018-05-19 2:45 ` [PATCH 07/12] sh: Remove "struct arch_hw_breakpoint::name" unused field Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 08/12] sh: Implement hw_breakpoint_arch_parse() Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 09/12] xtensa: " Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 10/12] perf/breakpoint: Remove default hw_breakpoint_arch_parse() Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 11/12] perf/breakpoint: Pass new breakpoint type to modify_breakpoint_slot() Frederic Weisbecker
2018-05-19 2:45 ` [PATCH 12/12] perf/breakpoint: Clean up and consolidate modify_user_hw_breakpoint_check() Frederic Weisbecker
2018-06-01 14:31 [GIT PULL] breakpoint: Rework arch validation v3 Frederic Weisbecker
2018-06-01 14:31 ` [PATCH 04/12] powerpc: Implement hw_breakpoint_arch_parse() Frederic Weisbecker
2018-06-26 2:58 [GIT PULL] breakpoint: Rework arch validation v4 Frederic Weisbecker
2018-06-26 2:58 ` [PATCH 04/12] powerpc: Implement hw_breakpoint_arch_parse() Frederic Weisbecker
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=87fu2hstf3.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=chris@zankel.net \
--cc=dalias@libc.org \
--cc=frederic@kernel.org \
--cc=jcmvbkbc@gmail.com \
--cc=joel.opensrc@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=ysato@users.sourceforge.jp \
/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
Powered by JetHome