From: David Miller <davem@davemloft.net>
To: namhyung@gmail.com
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 08:59:37 -0700 (PDT) [thread overview]
Message-ID: <20101025.085937.226775583.davem@davemloft.net> (raw)
In-Reply-To: <1288021958-3130-2-git-send-email-namhyung@gmail.com>
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.
next prev parent reply other threads:[~2010-10-25 15:59 UTC|newest]
Thread overview: 14+ 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 ` [PATCH 2/3] sparc32: remove CONFIG_HAVE_PERF_EVENTS option Namhyung Kim
2010-10-25 15:59 ` David Miller [this message]
2010-10-25 16:31 ` Namhyung Kim
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 16:00 ` David Miller
2010-10-25 16:07 ` Namhyung Kim
2010-10-25 16:09 ` David Miller
2010-10-25 16:11 ` Sam Ravnborg
2010-10-25 18:53 ` David Miller
2010-10-25 19:41 ` Sam Ravnborg
2010-10-26 7:14 ` Daniel Hellstrom
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=20101025.085937.226775583.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome