From: ebiederm@xmission.com (Eric W. Biederman)
To: "Lu, Yinghai" <yinghai.lu@amd.com>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"Tobias Diedrich" <ranma+kernel@tdiedrich.de>,
"Andrew Morton" <akpm@osdl.org>, "Adrian Bunk" <bunk@stusta.de>,
"Andi Kleen" <ak@suse.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] x86_64 io_apic: Implement remove_pin_to_irq
Date: Mon, 08 Jan 2007 14:30:53 -0700 [thread overview]
Message-ID: <m1ps9pgq9e.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <5986589C150B2F49A46483AC44C7BCA490736C@ssvlexmb2.amd.com> (Yinghai Lu's message of "Mon, 8 Jan 2007 13:09:19 -0800")
"Lu, Yinghai" <yinghai.lu@amd.com> writes:
> -----Original Message-----
> From: ebiederm@xmission.com [mailto:ebiederm@xmission.com]
> Sent: Monday, January 08, 2007 7:50 AM
> To: Linus Torvalds
> Cc: Tobias Diedrich; Lu, Yinghai; Andrew Morton; Adrian Bunk; Andi
> Kleen; Linux Kernel Mailing List
> Subject: [PATCH 1/4] x86_64 io_apic: Implement remove_pin_to_irq
>
> +static void remove_pin_to_irq(unsigned int irq, int apic, int pin)
> +{
> + struct irq_pin_list *entry = irq_2_pin + irq;
>
> You may need to update add_pin_to_irq to avoid multi entries for irq 0.
Any updates to add_pin_to_irq are wrong. It works fine. If there
is something wrong we need to fix remove_pin_to_irq.
What is the problem you see? Sorry I'm dense at the moment.
I preserve the invariant that irq_2_pin + irq is always the first
entry in the chain. I do this when I delete a multi chain entry
by copying the next entry over the current entry, and then freeing
(and leaking) the second entry in the chain.
Is there something wrong with that? I came within an inch of deleting
this multiple apic, pin to irq mapping code but the comments said it
is needed for some ioapic case. So in resurrecting this variant I may
have goofed somewhere.
Eric
next prev parent reply other threads:[~2007-01-08 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 21:09 Lu, Yinghai
2007-01-08 21:30 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-08 21:46 Lu, Yinghai
[not found] <5986589C150B2F49A46483AC44C7BCA490733F@ssvlexmb2.amd.com>
2007-01-03 6:23 ` 2.6.20-rc3: known unfixed regressions - x86_64 boot failure: "IO-APIC + timer doesn't work" Yinghai Lu
2007-01-08 0:55 ` Tobias Diedrich
2007-01-08 1:09 ` Linus Torvalds
2007-01-08 15:49 ` [PATCH 1/4] x86_64 io_apic: Implement remove_pin_to_irq Eric W. Biederman
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=m1ps9pgq9e.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ranma+kernel@tdiedrich.de \
--cc=torvalds@osdl.org \
--cc=yinghai.lu@amd.com \
/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