[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180828143953.GL22309@kernel.org>
Date: Tue, 28 Aug 2018 11:39:53 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Oleg Nesterov <oleg@...hat.com>, Jiri Olsa <jolsa@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
David Ahern <dsahern@...il.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Milind Chabbi <chabbi.milind@...il.com>,
Frederic Weisbecker <frederic@...nel.org>
Subject: Re: [PATCH 4/5] perf/hw_breakpoint: Set breakpoint as disabled in
modify_user_hw_breakpoint error path
Em Tue, Aug 28, 2018 at 04:38:23PM +0200, Jiri Olsa escreveu:
> On Tue, Aug 28, 2018 at 11:29:14AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Aug 09, 2018 at 06:30:15PM +0200, Jiri Olsa escreveu:
> > > On Thu, Aug 09, 2018 at 04:17:13PM +0200, Oleg Nesterov wrote:
> > > > On 08/09, Jiri Olsa wrote:
> > > > > - if (err)
> > > > > + if (err) {
> > > > > + bp->attr.disabled = 1;
> > > > > return err;
> > > >
> > > > Yes, but on the second thought... Can't we simply do
> >
> > <SNIP>
> >
> > > > instead of this and the next patch?
> >
> > <SNIP>
> >
> > > yep, seems good.. will send new version
> >
> > Ok, but this is just for 4/5 and 5/5, right?
>
> I resent v4 yesterday with final changes/acks, in here:
>
> 7186 r Aug 27 Jiri Olsa (1.6K) [PATCHv4 0/5] perf/hw_breakpoint: Fix breakpoint modify
Ok, will search that, sorry for the noise :-)
- Arnaldo
Powered by blists - more mailing lists