mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: don't map io_apic two times.
Date: Wed, 20 May 2009 01:03:14 -0700	[thread overview]
Message-ID: <86802c440905200103o5905e997weec5da0fd0a86c41@mail.gmail.com> (raw)
In-Reply-To: <20090520075829.GD23959@elte.hu>

On Wed, May 20, 2009 at 12:58 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Yinghai Lu <yinghai@kernel.org> wrote:
>
>> mp_register_ioapic() already map it.
>>
>> [ Impact: don't map io apic address again ]
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>>
>> ---
>>  arch/x86/kernel/apic/io_apic.c |    7 ++++++-
>>  1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> Index: linux-2.6/arch/x86/kernel/apic/io_apic.c
>> ===================================================================
>> --- linux-2.6.orig/arch/x86/kernel/apic/io_apic.c
>> +++ linux-2.6/arch/x86/kernel/apic/io_apic.c
>> @@ -4162,7 +4162,12 @@ fake_ioapic_page:
>>                               alloc_bootmem_pages(PAGE_SIZE);
>>                       ioapic_phys = __pa(ioapic_phys);
>>               }
>> -             set_fixmap_nocache(idx, ioapic_phys);
>> +             /*
>> +              * when acpi ioapic is used, mp_register_ioapic() map
>> +              * ioapic_phys already
>> +              */
>> +             if (!acpi_ioapic)
>> +                     set_fixmap_nocache(idx, ioapic_phys);
>
> The change is correct, but i'm not sure we want to do this - the
> acpi_ioapic flag might change its meaning (and then break this code
> subtly) and this is bootup code so doing the mapping twice should be
> no issue.
>
> If it were some expensive initialization i'd agree, but here it's
> really just a couple of instructions and an INVLPG.
>
> Hm?

ok, please drop it.

YH

      reply	other threads:[~2009-05-20  8:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  5:23 Yinghai Lu
2009-05-20  7:45 ` [PATCH] x86: don't allocate dummy page for wrong madt/mptable Yinghai Lu
2009-05-20 18:34   ` [PATCH, v2] " Yinghai Lu
2009-05-20  7:58 ` [PATCH] x86: don't map io_apic two times Ingo Molnar
2009-05-20  8:03   ` Yinghai Lu [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=86802c440905200103o5905e997weec5da0fd0a86c41@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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®