All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: do_boot_cpu - add check if we have ESR register
Date: Mon, 22 Sep 2008 12:00:24 +0200	[thread overview]
Message-ID: <20080922100024.GA24705@elte.hu> (raw)
In-Reply-To: <86802c440809220257q4e1b4c81o534c957d919a6b3c@mail.gmail.com>


* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

> > Actually it's resend of the patch. On previous attempt Yinghai was 
> > proposed to choose:
> >
> >> one apic_version or boot_cpu_apic_version could be enough
> >
> > but I think it should be different patch which does cleaning up 
> > variables usage. So for now I think _this_ patch is enough since 
> > idea is to prevent of touching nonexistant register rather code 
> > cleaning (whci could be done later).
> 
> do we have systems that have mixed cpu supported with different apic 
> version?

i dont think that ever happened in the past. Vendors have trouble 
keeping same-cpu type systems going ;-)

OTOH, if it's simple to have multi-version support then lets do that 
throughout. (although we certainly cannot test it. Perhaps we can 
provoke it artificially via a hack that artificially degrades one cpu's 
apic version or so.)

	Ingo

  reply	other threads:[~2008-09-22 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22  9:36 [PATCH] x86: do_boot_cpu - add check if we have ESR register Cyrill Gorcunov
2008-09-22  9:51 ` Cyrill Gorcunov
2008-09-22  9:57   ` Yinghai Lu
2008-09-22 10:00     ` Ingo Molnar [this message]
2008-09-22 10:04     ` Cyrill Gorcunov
2008-09-22 10:15     ` Cyrill Gorcunov
2008-09-22 18:37       ` Yinghai Lu
2008-09-22 19:21         ` 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=20080922100024.GA24705@elte.hu \
    --to=mingo@elte.hu \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --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 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.