From: Dean Nelson <dcn@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <Yinghai.lu@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, UV: non-sparse irq based uv_setup_irq()/uv_teardown_irq() functions
Date: Tue, 21 Oct 2008 07:32:43 -0500 [thread overview]
Message-ID: <20081021123243.GA6408@sgi.com> (raw)
In-Reply-To: <20081020183718.GA22271@sgi.com>
On Mon, Oct 20, 2008 at 01:37:18PM -0500, Dean Nelson wrote:
> Provide a means for UV interrupt MMRs to be setup with the message to be sent
> when an MSI-like interrupt is raised.
>
> Signed-off-by: Dean Nelson <dcn@sgi.com>
>
> ---
>
> Ingo,
>
> A version of this patch, based on the sparse irq code, you applied to
> tip/x86/uv. I'm submitting this verision, which is not based on the
> sparse irq code, to replace that patch since the sparse irq code has
> been pulled from linux-next, and I'd like this functionality to get
> into linux 2.6.28.
>
> The differences between the two patches are minimal. The bulk of it
> was to move the code that was added to io_apic.c to io_apic_64.c instead.
> I also made a small change to some of the comments.
>
> Thanks,
> Dean
>
> arch/x86/kernel/Makefile | 2
> arch/x86/kernel/io_apic_64.c | 67 +++++++++++++++++++++++++++++++++
> arch/x86/kernel/uv_irq.c | 79 +++++++++++++++++++++++++++++++++++++++
> include/asm-x86/uv/uv_irq.h | 36 +++++++++++++++++
> 4 files changed, 183 insertions(+), 1 deletion(-)
It turns out that the sparse irq code and the version of this patch based
on that made it into 2.6.28, so...
please ignore this patch.
prev parent reply other threads:[~2008-10-21 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 18:37 [PATCH] x86, UV: non-sparse irq based uv_setup_irq()/uv_teardown_irq() functions Dean Nelson
2008-10-21 12:32 ` Dean Nelson [this message]
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=20081021123243.GA6408@sgi.com \
--to=dcn@sgi.com \
--cc=Yinghai.lu@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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