From: Chuck Ebbert <76306.1226@compuserve.com>
To: Stephane Eranian <eranian@frankl.hpl.hp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Chuck Ebbert <76306.1226@compuserve.com>
Subject: Re: [PATCH 7/11] perfmon2 patch for review: modified i386 files
Date: Fri, 12 May 2006 21:30:04 -0400 [thread overview]
Message-ID: <200605122132_MC3-1-BFA1-E625@compuserve.com> (raw)
In-Reply-To: <200605121633.k4CGXmKd027348@frankl.hpl.hp.com>
On Fri, 12 May 2006 09:33:48 -0700, Stephane Eranian wrote:
<snip>
> --- linux-2.6.17-rc4.orig/arch/i386/kernel/entry.S 2006-05-12 03:16:09.000000000 -0700
> +++ linux-2.6.17-rc4/arch/i386/kernel/entry.S 2006-05-12 03:18:52.000000000 -0700
> @@ -436,6 +436,16 @@
> /* The include is where all of the SMP etc. interrupts come from */
> #include "entry_arch.h"
>
> +#if defined(CONFIG_X86_LOCAL_APIC) && defined(CONFIG_PERFMON)
> +ENTRY(pmu_interrupt)
> + pushl $LOCAL_PERFMON_VECTOR-256
> + SAVE_ALL
> + pushl %esp
> + call pfm_intr_handler
> + addl $4, %esp
> + jmp ret_from_intr
> +#endif
> +
> ENTRY(divide_error)
> pushl $0 # no error code
> pushl $do_divide_error
You should rename pfm_intr_handler to smp_pmu_interrupt (yes, it's not
really SMP but other functions have that problem too, e.g.
smp_error_interrupt) and make it fastcall, then you can do:
BUILD_INTERRUPT(pmu_interrupt, LOCAL_PERFMON_VECTOR)
instead of open-coding it. Then the Xen patch that extends the interrupt
vector range won't have to change to accommodate your patch.
You should also probably move the BUILD_INTERRUPT() into entry_arch.h
with the rest of them.
--
Chuck
"The x86 isn't all that complex -- it just doesn't make a lot of sense."
-- Mike Johnson
next reply other threads:[~2006-05-13 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 1:30 Chuck Ebbert [this message]
2006-05-13 16:53 ` Stephane Eranian
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 16:33 Stephane Eranian
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=200605122132_MC3-1-BFA1-E625@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=eranian@frankl.hpl.hp.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®