From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH] serialize assign_irq_vector() use of static variables
Date: Wed, 26 Apr 2006 08:53:38 -0700 [thread overview]
Message-ID: <20060426085338.c1cd6b94.rdunlap@xenotime.net> (raw)
In-Reply-To: <444F9AD9.76E4.0078.0@novell.com>
On Wed, 26 Apr 2006 16:07:53 +0200 Jan Beulich wrote:
> Since assign_irq_vector() can be called at runtime, its access of static
> variables should be protected by a lock.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
Hi,
Would you include diffstat output also, as mentioned (optional)
in Documentation/SubmittingPatches? I'd really like to see a list
of patched files without having to scan the entire patch.
Thanks.
Oh, the diff filenames should begin at the linux-2.x.y level so
that they can be applied with patch -p1.
Lots of tools know how to do this.
> diff -Npru /home/jbeulich/tmp/linux-2.6.17-rc2/arch/i386/kernel/io_apic.c
> 2.6.17-rc2-x86-assign_irq_vector-lock/arch/i386/kernel/io_apic.c
> --- /home/jbeulich/tmp/linux-2.6.17-rc2/arch/i386/kernel/io_apic.c 2006-04-26 10:55:11.000000000 +0200
> +++ 2.6.17-rc2-x86-assign_irq_vector-lock/arch/i386/kernel/io_apic.c 2006-04-25 15:38:32.000000000 +0200
> @@ -1163,16 +1170,21 @@ next:
>
> if (current_vector >= FIRST_SYSTEM_VECTOR) {
> offset++;
> - if (!(offset%8))
> + if (!(offset%8)) {
Use better spacing here: (offset % 8)
> + spin_unlock(&vector_lock);
> return -ENOSPC;
> + }
> current_vector = FIRST_DEVICE_VECTOR + offset;
> }
>
---
~Randy
prev parent reply other threads:[~2006-04-26 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:07 Jan Beulich
2006-04-26 14:14 ` Andi Kleen
2006-04-26 15:53 ` Randy.Dunlap [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=20060426085338.c1cd6b94.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jbeulich@novell.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®