All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] sparc32: remove CONFIG_HAVE_PERF_EVENTS option
Date: Mon, 25 Oct 2010 16:31:19 +0000	[thread overview]
Message-ID: <1288024279.1689.23.camel@leonhard> (raw)
In-Reply-To: <20101025.085937.226775583.davem@davemloft.net>

2010-10-25 (ì›”), 08:59 -0700, David Miller:
> From: Namhyung Kim <namhyung@gmail.com>
> Date: Tue, 26 Oct 2010 00:52:37 +0900
> 
> > Remove HAVE_PERF_EVENTS and PERF_USE_VMALLOC under config
> > SPARC because they're under SPARC64 too. Supporting
> > perf_event needs atomic64 operations but AFAIK sparc32
> > doesn't provide them, CMIIW. ;-) Also removes redundant
> > HAVE_IRQ_WORK line.
> > 
> > Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> 
> The generic non-hw perf event stuff builds fine on sparc32,
> please don't remove this unless you have a legitimate build
> failure to report and fix.
> 
> Even if sparc32 doesn't provide atomic64_t support, it very
> easily could do so using include/asm-generic/atomic64.h which
> implements them using spinlocks.

Now I see following build failure without this patch. Maybe some work is
needed to deal with atomic64_t. I'll try to prepare for it soon. Thanks.


  CC      arch/sparc/kernel/setup_32.o
In file included from arch/sparc/include/asm/local64.h:1:0,
                 from include/linux/perf_event.h:465,
                 from include/linux/ftrace_event.h:8,
                 from include/trace/syscall.h:6,
                 from include/linux/syscalls.h:76,
                 from arch/sparc/kernel/setup_32.c:23:
include/asm-generic/local64.h:62:2: error: expected
                            specifier-qualifier-list before 'atomic64_t'
In file included from include/linux/ftrace_event.h:8:0,
                 from include/trace/syscall.h:6,
                 from include/linux/syscalls.h:76,
                 from arch/sparc/kernel/setup_32.c:23:
include/linux/perf_event.h:722:2: error: expected
                            specifier-qualifier-list before 'atomic64_t'
include/linux/perf_event.h: In function 'perf_fetch_caller_regs':
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tstate'
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tpc'
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tnpc'
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tpc'
make[3]: *** [arch/sparc/kernel/setup_32.o] Error 1
make[2]: *** [arch/sparc/kernel] Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2


-- 
Regards,
Namhyung Kim



WARNING: multiple messages have this Message-ID (diff)
From: Namhyung Kim <namhyung@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] sparc32: remove CONFIG_HAVE_PERF_EVENTS option
Date: Tue, 26 Oct 2010 01:31:19 +0900	[thread overview]
Message-ID: <1288024279.1689.23.camel@leonhard> (raw)
In-Reply-To: <20101025.085937.226775583.davem@davemloft.net>

2010-10-25 (월), 08:59 -0700, David Miller:
> From: Namhyung Kim <namhyung@gmail.com>
> Date: Tue, 26 Oct 2010 00:52:37 +0900
> 
> > Remove HAVE_PERF_EVENTS and PERF_USE_VMALLOC under config
> > SPARC because they're under SPARC64 too. Supporting
> > perf_event needs atomic64 operations but AFAIK sparc32
> > doesn't provide them, CMIIW. ;-) Also removes redundant
> > HAVE_IRQ_WORK line.
> > 
> > Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> 
> The generic non-hw perf event stuff builds fine on sparc32,
> please don't remove this unless you have a legitimate build
> failure to report and fix.
> 
> Even if sparc32 doesn't provide atomic64_t support, it very
> easily could do so using include/asm-generic/atomic64.h which
> implements them using spinlocks.

Now I see following build failure without this patch. Maybe some work is
needed to deal with atomic64_t. I'll try to prepare for it soon. Thanks.


  CC      arch/sparc/kernel/setup_32.o
In file included from arch/sparc/include/asm/local64.h:1:0,
                 from include/linux/perf_event.h:465,
                 from include/linux/ftrace_event.h:8,
                 from include/trace/syscall.h:6,
                 from include/linux/syscalls.h:76,
                 from arch/sparc/kernel/setup_32.c:23:
include/asm-generic/local64.h:62:2: error: expected
                            specifier-qualifier-list before 'atomic64_t'
In file included from include/linux/ftrace_event.h:8:0,
                 from include/trace/syscall.h:6,
                 from include/linux/syscalls.h:76,
                 from arch/sparc/kernel/setup_32.c:23:
include/linux/perf_event.h:722:2: error: expected
                            specifier-qualifier-list before 'atomic64_t'
include/linux/perf_event.h: In function 'perf_fetch_caller_regs':
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tstate'
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tpc'
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tnpc'
include/linux/perf_event.h:1004:2: error: 'struct pt_regs' has no member
                                           named 'tpc'
make[3]: *** [arch/sparc/kernel/setup_32.o] Error 1
make[2]: *** [arch/sparc/kernel] Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2


-- 
Regards,
Namhyung Kim



  reply	other threads:[~2010-10-25 16:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 15:52 [PATCH 1/3] sparc: don't #include asm/system.h in asm/jump_label.h Namhyung Kim
2010-10-25 15:52 ` Namhyung Kim
2010-10-25 15:52 ` [PATCH 2/3] sparc32: remove CONFIG_HAVE_PERF_EVENTS option Namhyung Kim
2010-10-25 15:52   ` Namhyung Kim
2010-10-25 15:59   ` David Miller
2010-10-25 15:59     ` David Miller
2010-10-25 16:31     ` Namhyung Kim [this message]
2010-10-25 16:31       ` Namhyung Kim
2010-10-25 18:55       ` David Miller
2010-10-25 18:55         ` David Miller
2010-10-25 15:52 ` [PATCH 3/3] sparc32: fix build failure on CONFIG_SPARC_LEON Namhyung Kim
2010-10-25 15:52   ` Namhyung Kim
2010-10-25 16:00   ` David Miller
2010-10-25 16:00     ` David Miller
2010-10-25 16:07     ` Namhyung Kim
2010-10-25 16:07       ` Namhyung Kim
2010-10-25 16:09       ` David Miller
2010-10-25 16:09         ` David Miller
2010-10-25 16:11     ` Sam Ravnborg
2010-10-25 16:11       ` Sam Ravnborg
2010-10-25 18:53       ` David Miller
2010-10-25 18:53         ` David Miller
2010-10-25 19:41         ` Sam Ravnborg
2010-10-25 19:41           ` Sam Ravnborg
2010-10-26  7:14           ` Daniel Hellstrom
2010-10-26  7:14             ` Daniel Hellstrom
2010-10-25 15:57 ` [PATCH 1/3] sparc: don't #include asm/system.h in David Miller
2010-10-25 15:57   ` [PATCH 1/3] sparc: don't #include asm/system.h in asm/jump_label.h David Miller

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=1288024279.1689.23.camel@leonhard \
    --to=namhyung@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    /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.