public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	tglx@linutronix.de, hpa@zytor.com, yhlu.kernel@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 8/8] x86: apic - unify init_bsp_APIC
Date: Fri, 15 Aug 2008 13:51:48 +0200	[thread overview]
Message-ID: <20080815115147.GA32726@elte.hu> (raw)
In-Reply-To: <aa79d98a0808142341k6a074c8fh41e44a9f23c14f0a@mail.gmail.com>


* Cyrill Gorcunov <gorcunov@gmail.com> wrote:

> On Thu, Aug 14, 2008 at 11:44 PM, Maciej W. Rozycki
> <macro@linux-mips.org> wrote:
> > On Thu, 1 Jan 1970, Cyrill Gorcunov wrote:
> >
> >> @@ -962,7 +962,8 @@ void __init init_bsp_APIC(void)
> >>        */
> >>       apic_write(APIC_LVT0, APIC_DM_EXTINT);
> >>       value = APIC_DM_NMI;
> >> -     if (!lapic_is_integrated())             /* 82489DX */
> >> +     /* discrete on 82489DX */
> >> +     if (!lapic_is_integrated())
> >>               value |= APIC_LVT_LEVEL_TRIGGER;
> >>       apic_write(APIC_LVT1, value);
> >>  }
> >
> >  Please elaborate.
> >
> >  Maciej
> >
> 
> Hi Maciej,
> 
> don't really understand what do you mean. [...]

i suspect the question might have been: 'why this change'.

If that was the question, the answer would be: to unify apic_32.c and 
apic_64.c we first use tiny little changes to bring the two files in 
sync. Presumably, each such change is a NOP or at least very safe - and 
clearly bisectable in the worst-case.

In this case, something that only makes sense on 32-bit has been added 
over to the 64-bit side. The resulting apic.c file will have to have 
legacy code as well - but hopefully not too much.

Cyrill, i've applied your series to tip/x86/apic. (i have fixed the 
timestamps) Please address Maciej's feedback as well, in subsequent 
patches.

	Ingo

  reply	other threads:[~2008-08-15 11:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 18:34 [patch 0/8] [RFC -tip] another one step toward APIC merging Cyrill Gorcunov
1970-01-01  0:00 ` [patch 1/8] x86: apic - use SET_APIC_DEST_FIELD instead of hardcoded shift Cyrill Gorcunov
1970-01-01  0:00 ` [patch 2/8] x86: apic - unify disable_apic_timer Cyrill Gorcunov
1970-01-01  0:00 ` [patch 3/8] x86: apic - unify __setup_APIC_LVTT Cyrill Gorcunov
1970-01-01  0:00 ` [patch 4/8] x86: apic - do not clear APIC twice in lapic_shutdown Cyrill Gorcunov
1970-01-01  0:00 ` [patch 5/8] x86: apic - get rid of local_apic_timer_verify_ok Cyrill Gorcunov
1970-01-01  0:00 ` [patch 6/8] x86: apic - unify verify_local_APIC Cyrill Gorcunov
1970-01-01  0:00 ` [patch 7/8] x86: apic - unify sync_Arb_IDs Cyrill Gorcunov
2008-08-14 19:41   ` Maciej W. Rozycki
2008-08-14 20:10     ` Cyrill Gorcunov
1970-01-01  0:00 ` [patch 8/8] x86: apic - unify init_bsp_APIC Cyrill Gorcunov
2008-08-14 19:44   ` Maciej W. Rozycki
2008-08-15  6:41     ` Cyrill Gorcunov
2008-08-15 11:51       ` Ingo Molnar [this message]
2008-08-15 12:15         ` Maciej W. Rozycki
2008-08-15 13:48           ` Ingo Molnar
2008-08-15 14:45             ` Cyrill Gorcunov
2008-08-15 14:47               ` Ingo Molnar
2008-08-15 15:31               ` Maciej W. Rozycki
2008-08-15 16:35                 ` Cyrill Gorcunov

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=20080815115147.GA32726@elte.hu \
    --to=mingo@elte.hu \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox