From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Yinghai Lu <yinghai@kernel.org>, x86team <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC -tip] x86,io-apic: Do not map IO-APIC direct registers twice
Date: Fri, 13 Nov 2009 00:06:06 +0300 [thread overview]
Message-ID: <20091112210606.GD5728@lenovo> (raw)
In-Reply-To: <20091112205459.GC5728@lenovo>
On Thu, Nov 12, 2009 at 11:54:59PM +0300, Cyrill Gorcunov wrote:
> On Thu, Nov 12, 2009 at 11:48:52PM +0300, Cyrill Gorcunov wrote:
> > Please review, I didn't manage to test (emulate actually since I don't
> > have such a hardware) it yet (going to do so this weekend).
> >
> > Meanwhile I would like to heard comments, complains and etc...
> > Perhaps I miss something obvious so don't hesitate to poke me.
> >
> > -- Cyrill
> > ---
> > x86,io-apic: Do not map IO-APIC direct registers twice
> >
> ...
> I know that I've occasionally removed
>
> apic_printk(APIC_VERBOSE, "mapped IOAPIC
> to %08lx (%08lx)\n",
>
> already fixed in v2, just do not post updated version here.
>
> -- Cyrill
Forgot to mention that I know this double for() over nr_ioapics
is slowlest approach but firstly I need to be sure that this
idea works in general/simple way before speedup it.
-- Cyrill
next prev parent reply other threads:[~2009-11-12 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 20:48 [RFC -tip] x86,io-apic: Do not map IO-APIC direct registers twice Cyrill Gorcunov
2009-11-12 20:54 ` Cyrill Gorcunov
2009-11-12 21:06 ` Cyrill Gorcunov [this message]
2009-11-12 23:22 ` Yinghai Lu
2009-11-13 17:50 ` Cyrill Gorcunov
2009-11-13 18:56 ` Yinghai Lu
2009-11-13 19:09 ` Cyrill Gorcunov
2009-11-13 19:17 ` Yinghai Lu
2009-11-13 19:22 ` Cyrill Gorcunov
2009-11-13 19:23 ` Yinghai Lu
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=20091112210606.GD5728@lenovo \
--to=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=yinghai@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