All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: "Han, Weidong" <weidong.han@intel.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>,
	"Kay, Allen M" <allen.m.kay@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>
Subject: Re: [PATCH 3/5] x86, intr-remap: enable interrupt remapping early
Date: Sat, 18 Apr 2009 09:24:14 +0200	[thread overview]
Message-ID: <20090418072414.GF7678@elte.hu> (raw)
In-Reply-To: <1240011743.27006.8496.camel@localhost.localdomain>


* Suresh Siddha <suresh.b.siddha@intel.com> wrote:

> On Fri, 2009-04-17 at 07:13 -0700, Ingo Molnar wrote:
> > * Weidong Han <weidong.han@intel.com> wrote:
> > 
> > > --- a/arch/x86/kernel/apic/apic.c
> > > +++ b/arch/x86/kernel/apic/apic.c
> > > @@ -118,6 +118,8 @@ static int x2apic_preenabled;
> > >  static int disable_x2apic;
> > >  static __init int setup_nox2apic(char *str)
> > >  {
> > > +	if (x2apic_enabled())
> > > +		panic("Bios already enabled x2apic, can't enforce nox2apic");
> > 
> > Could you please turn that into something like:
> 
> I have couple of patches cleaning these up(including some 
> warnings). I will post them shortly.

ok!

> > > +ir_failed:
> > > +	if (x2apic_preenabled)
> > > +		panic("x2apic enabled by bios. But IR enabling failed");
> > 
> > What is the likelyhood that we can continue in compat mode? If 
> > there's some chance, we should rather print a KERN_WARNING and 
> > should try to continue. If IRQs are not coming we'll hang shortly 
> > afterwards anyway.
> 
> Typically only on high end platforms we will see x2apic enabled by 
> BIOS before OS handover. And in these cases, BIOS should have 
> already enabled interrupt-remapping in extended interrupt mode, 
> before handing over control to OS. If the extended interrupt mode 
> is set, HW will block the compatibility format interrupts anyway. 
> And I think its better to panic rather than hanging at random 
> places(depending on which interrupts are already in remapped 
> format and which are not). This way, it will be easy for anyone to 
> figure out what is happening.

fair enough.

	Ingo

  reply	other threads:[~2009-04-18  7:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  8:42 [PATCH 0/5] fix bugs of x2apic/intr-remap Weidong Han
2009-04-17  8:42 ` [PATCH 1/5] docs: add nox2apic back to kernel-parameters.txt Weidong Han
2009-04-17 13:51   ` Ingo Molnar
2009-04-17 14:48   ` [tip:x86/apic] docs, x86: " tip-bot for Weidong Han
2009-04-18  7:31   ` [tip:x86/urgent] " tip-bot for Weidong Han
2009-04-19  8:24   ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-17  8:42 ` [PATCH 2/5] x86,intr-remap: fix ack for interrupt remapping Weidong Han
2009-04-17 14:49   ` [tip:x86/apic] x86, intr-remap: " tip-bot for Weidong Han
2009-04-19  8:25   ` tip-bot for Weidong Han
2009-04-17  8:42 ` [PATCH 3/5] x86, intr-remap: enable interrupt remapping early Weidong Han
2009-04-17 14:13   ` Ingo Molnar
2009-04-17 23:42     ` Suresh Siddha
2009-04-18  7:24       ` Ingo Molnar [this message]
2009-04-17 14:49   ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-19  8:25   ` tip-bot for Weidong Han
2009-04-17  8:42 ` [PATCH 4/5] x86, intr-remap: add option to disable interrupt remapping Weidong Han
2009-04-17 14:49   ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-19  8:25   ` tip-bot for Weidong Han
2009-04-17  8:42 ` [PATCH 5/5] x86: fix x2apic/intr-remap resume Weidong Han
2009-04-17 14:15   ` Ingo Molnar
2009-04-17 14:49   ` [tip:x86/apic] x86, intr-remap: " tip-bot for Weidong Han
2009-04-19  8:25   ` tip-bot for Weidong Han
2009-04-17 14:30 ` [PATCH 0/5] fix bugs of x2apic/intr-remap Ingo Molnar
2009-04-17 14:41   ` Ingo Molnar
2009-04-18  3:07     ` Han, Weidong
2009-04-18  6:41       ` Ingo Molnar
2009-04-19  6:32   ` David Woodhouse
2009-04-19  8:22     ` Ingo Molnar

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=20090418072414.GF7678@elte.hu \
    --to=mingo@elte.hu \
    --cc=allen.m.kay@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=weidong.han@intel.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.