mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>,
	x86@kernel.org, yinghai@kernel.org, macro@linux-mips.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 3/3] x86,apic: limit apic dumping, introduce show_lapic setup option
Date: Thu, 15 Oct 2009 18:27:37 +0400	[thread overview]
Message-ID: <20091015142737.GB5331@lenovo> (raw)
In-Reply-To: <20091014202941.GE5259@lenovo>

[Cyrill Gorcunov - Thu, Oct 15, 2009 at 12:29:41AM +0400]
| [Ingo Molnar - Wed, Oct 14, 2009 at 07:56:16PM +0200]
| | 
| | btw., i'm getting this warning on a test-box:
| ...
| | 
| | [    0.400000] Checking 'hlt' instruction... OK.
| | [    0.440000] SMP alternatives: switching to UP code
| | [    0.450000] debug: unmapping init memory 79c7a000..79c80000
| | 
| | noop_default_phys_pkg_id() should return 0 i guess, and not generate a 
| | warning?
| | 
| | 	Ingo
| | 
| 
| Ingo, I think the better would be to just make NOOP plain
| NOOP without any kind of checking. Something like below
| (I still can't fetch last/fresh -tip repo /remote point hangs/
|  for this so I've used interdiff).
| 
| Comments?
| 
| Btw, the base problem from dump you posted is that we've been
| cheking only for read/write operations allowing all other ops
| be called without any kind of check (and retrieving pkgid happened
| there all the time just didn't trigger warn until we've substituted
| apic driver completely). Using NOOP without warn should be more
| convenient (all previous "dark" places in apic code already covered
| with cpu_has_apic/disable_apic checks so the only risk we have --
| is code that will appear in future).
| 
| 	-- Cyrill
| ---

Ingo, please don't apply it yet. I think there is a nit.
Checking now. Will resend later the proper patch.

	-- Cyrill

  reply	other threads:[~2009-10-15 14:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 20:07 [patch 0/3] x86 apic series Cyrill Gorcunov
2009-10-13 20:07 ` [patch 1/3] x86,apic: introduce NOOP apic driver Cyrill Gorcunov
2009-10-14  8:17   ` [tip:x86/apic] x86, apic: Introduce the " tip-bot for Cyrill Gorcunov
2009-10-13 20:07 ` [patch 2/3] x86,apic -- use apic noop driver Cyrill Gorcunov
2009-10-14  8:17   ` [tip:x86/apic] x86, apic: Use " tip-bot for Cyrill Gorcunov
2009-10-13 20:07 ` [patch 3/3] x86,apic: limit apic dumping, introduce show_lapic setup option Cyrill Gorcunov
2009-10-14  7:12   ` Ingo Molnar
2009-10-14  7:51     ` Cyrill Gorcunov
2009-10-14 15:09     ` Cyrill Gorcunov
2009-10-14 15:40       ` [tip:x86/apic] x86, apic: Explain show_lapic= in kernel parameters list tip-bot for Cyrill Gorcunov
2009-10-14 17:56       ` [patch 3/3] x86,apic: limit apic dumping, introduce show_lapic setup option Ingo Molnar
2009-10-14 18:00         ` Cyrill Gorcunov
2009-10-14 18:20         ` Cyrill Gorcunov
2009-10-14 20:29         ` Cyrill Gorcunov
2009-10-15 14:27           ` Cyrill Gorcunov [this message]
2009-10-14  8:17   ` [tip:x86/apic] x86, apic: Limit apic dumping, introduce new show_lapic= " tip-bot for 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=20091015142737.GB5331@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

all inboxes | Powered by JetHome®