On Fri, Jul 17, 2015 at 04:47:26PM +0100, Mark Rutland wrote:
> On Fri, Jul 17, 2015 at 04:03:36PM +0100, Liang, Kan wrote:
> > >
> > > On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
> > > > From: Kan Liang
> > > >
> > > > Using is_hardware_event to replace
On Fri, Jul 17, 2015 at 04:03:36PM +0100, Liang, Kan wrote:
> >
> > On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
> > > From: Kan Liang
> > >
> > > Using is_hardware_event to replace !is_software_event to indicate a
> > > hardware event.
> >
> > Why...?
>
> First, the
>
> On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > Using is_hardware_event to replace !is_software_event to indicate a
> > hardware event.
>
> Why...?
First, the comments of is_software_event is not correct.
0 or !is_software_event is not for
On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
> From: Kan Liang
>
> Using is_hardware_event to replace !is_software_event to indicate a
> hardware event.
Why...?
For an uncore event e, is_hardware_event(e) != !is_software_event(e), so
this will be a change of
On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
From: Kan Liang kan.li...@intel.com
Using is_hardware_event to replace !is_software_event to indicate a
hardware event.
Why...?
First, the comments of is_software_event is not correct.
0 or !is_software_event is
On Fri, Jul 17, 2015 at 04:47:26PM +0100, Mark Rutland wrote:
On Fri, Jul 17, 2015 at 04:03:36PM +0100, Liang, Kan wrote:
On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
From: Kan Liang kan.li...@intel.com
Using is_hardware_event to replace
On Fri, Jul 17, 2015 at 04:03:36PM +0100, Liang, Kan wrote:
On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
From: Kan Liang kan.li...@intel.com
Using is_hardware_event to replace !is_software_event to indicate a
hardware event.
Why...?
First, the
On Thu, Jul 16, 2015 at 09:33:45PM +0100, kan.li...@intel.com wrote:
From: Kan Liang kan.li...@intel.com
Using is_hardware_event to replace !is_software_event to indicate a
hardware event.
Why...?
For an uncore event e, is_hardware_event(e) != !is_software_event(e), so
this will be a change
From: Kan Liang
Using is_hardware_event to replace !is_software_event to indicate a
hardware event.
Signed-off-by: Kan Liang
---
include/linux/perf_event.h | 7 ++-
kernel/events/core.c | 6 +++---
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git
From: Kan Liang kan.li...@intel.com
Using is_hardware_event to replace !is_software_event to indicate a
hardware event.
Signed-off-by: Kan Liang kan.li...@intel.com
---
include/linux/perf_event.h | 7 ++-
kernel/events/core.c | 6 +++---
2 files changed, 9 insertions(+), 4
10 matches
Mail list logo