mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Cyrill Gorcunov" <gorcunov@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"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 11:37:21 -0700	[thread overview]
Message-ID: <86802c440809221137v63e46951j78ae337275872b58@mail.gmail.com> (raw)
In-Reply-To: <20080922101505.GF7663@localhost>

On Mon, Sep 22, 2008 at 3:15 AM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> [Yinghai Lu - Mon, Sep 22, 2008 at 02:57:17AM -0700]
> | >
> | > 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?
> |
> | YH
> |
>
> Yinghai what was the reason of this question? I've a suspicious
> you're planning to test apic version early and only _once_ so
> eliminating APIC_INTERGRATED call? Am I right?

want to put more thing in genapic...

YH

  reply	other threads:[~2008-09-22 18:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22  9:36 Cyrill Gorcunov
2008-09-22  9:51 ` Cyrill Gorcunov
2008-09-22  9:57   ` Yinghai Lu
2008-09-22 10:00     ` Ingo Molnar
2008-09-22 10:04     ` Cyrill Gorcunov
2008-09-22 10:15     ` Cyrill Gorcunov
2008-09-22 18:37       ` Yinghai Lu [this message]
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=86802c440809221137v63e46951j78ae337275872b58@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    /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®