From: ebiederm@xmission.com (Eric W. Biederman)
To: sedat.dilek@gmail.com
Cc: Florian Mickler <florian@mickler.org>,
Paul Bolle <pebolle@tiscali.nl>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
kurup_avinash@yahoo.com, maciej.rutecki@gmail.com, mingo@elte.hu,
rjw@sisk.pl, zersaa@gmail.com, stable@kernel.org
Subject: Re: [PATCH][POKE] Skip looking for ioapic overrides when ioapics are not present
Date: Thu, 31 Mar 2011 05:05:30 -0700 [thread overview]
Message-ID: <m1ipuzfqb9.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <AANLkTikmWDu7FZ2A7_CWGCuAeKOeK4x+u8vctCro0mSN@mail.gmail.com> (Sedat Dilek's message of "Thu, 31 Mar 2011 13:01:18 +0200")
Sedat Dilek <sedat.dilek@googlemail.com> writes:
> On Thu, Mar 31, 2011 at 12:53 PM, Florian Mickler <florian@mickler.org> wrote:
>> On Thu, 31 Mar 2011 10:48:43 +0200
>> Paul Bolle <pebolle@tiscali.nl> wrote:
>>
>>> On Thu, 2011-03-31 at 10:01 +0200, Florian Mickler wrote:
>>> > diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
>>> > index 68df09b..3940103 100644
>>> > --- a/arch/x86/kernel/apic/io_apic.c
>>> > +++ b/arch/x86/kernel/apic/io_apic.c
>>> > @@ -3789,6 +3789,9 @@ int acpi_get_override_irq(u32 gsi, int *trigger, int *polarity)
>>> > {
>>> > int ioapic, pin, idx;
>>> >
>>> > + if (acpi_irq_model != ACPI_IRQ_MODEL_IOAPIC)
>>> > + return -1;
>>> > +
>>> > if (skip_ioapic_setup)
>>> > return -1;
>>> >
>>>
>>> Seems to have the same goal as commit
>>> 678301ecadec24ff77ab310eebf8a32ccddb1850 ("x86, ioapic: Don't warn about
>>> non-existing IOAPICs if we have none"), which got merged in the v2.6.38
>>> cycle (authored by me, signed off by Ingo Molnar). Maybe Eric's patch is
>>> more correct. I can't say as I was happy with the effect of my patch
>>> (ie, make an uninteresting error disappear) and didn't investigate any
>>> further. I have also no desire to dive into this matter again.
Yes. My patch is more correct. We really do want the warning if we have
0 ioapics and we expect to be using ioapics. It doesn't make sense to
suppress the warning unless we aren't in ioapic mode.
I don't have a clue why my patch got lost, but can we please get it
applied?
>> Thanks for letting me know. Sedat, did you actually test with 2.6.38?
>>
>> Regards,
>> Flo
> I have and had this patch in my own patch-series *before* Debian
> included it (IIRC right after Eric committed it to LKML).
> To answer your question: Yes.
> I have the patch also in my current linux-next kernels
> (next-20110331).
Eric
next prev parent reply other threads:[~2011-03-31 12:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 8:01 [PATCH][POKE] Skip looking for ioapic overrides when ioapics are not present Florian Mickler
2011-03-31 8:43 ` Ingo Molnar
2011-03-31 10:59 ` Florian Mickler
2011-04-02 15:11 ` [stable] " Andi Kleen
2011-04-02 18:35 ` Ingo Molnar
2011-04-01 1:23 ` [PATCH v2] x86, ioapic: " Florian Mickler
2011-04-01 6:20 ` Ingo Molnar
2011-04-01 6:43 ` Eric W. Biederman
2011-04-01 6:47 ` Len Brown
2011-04-01 7:50 ` Ingo Molnar
2011-04-01 15:44 ` [PATCH] x86, ioapic: move acpi_get_override_irq to acpi.c Florian Mickler
2011-04-01 16:26 ` Florian Mickler
2011-04-03 14:34 ` Florian Mickler
2011-04-04 15:00 ` Ingo Molnar
2011-04-12 7:39 ` Ingo Molnar
2011-04-12 19:53 ` Florian Mickler
2011-04-12 20:01 ` [PATCH 1/2 v2] x86, ioapic: Skip looking for ioapic overrides when ioapics are not present Florian Mickler
2011-04-12 20:01 ` [PATCH 2/2 v2] x86, ioapic: move acpi_get_override_irq to acpi.c Florian Mickler
2011-04-15 10:19 ` Ingo Molnar
2011-05-17 14:38 ` Florian Mickler
2011-03-31 8:48 ` [PATCH][POKE] Skip looking for ioapic overrides when ioapics are not present Paul Bolle
2011-03-31 10:53 ` Florian Mickler
2011-03-31 11:01 ` Sedat Dilek
2011-03-31 12:05 ` Eric W. Biederman [this message]
2011-03-31 12:43 ` Ingo Molnar
2011-04-02 0:48 ` Eric W. Biederman
2011-04-02 18:43 ` Ingo Molnar
2011-04-02 22:21 ` Eric W. Biederman
2011-03-31 13:16 ` Florian Mickler
2011-03-31 13:25 ` Sedat Dilek
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=m1ipuzfqb9.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=florian@mickler.org \
--cc=kurup_avinash@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=mingo@elte.hu \
--cc=pebolle@tiscali.nl \
--cc=rjw@sisk.pl \
--cc=sedat.dilek@gmail.com \
--cc=stable@kernel.org \
--cc=zersaa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.