mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Youquan Song <youquan.song@linux.intel.com>
To: "Woodhouse, David" <david.woodhouse@intel.com>,
	Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"Song, Youquan" <youquan.song@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"hpa@linux.intel.com" <hpa@linux.intel.com>,
	"Kay, Allen M" <allen.m.kay@intel.com>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	"Sankaran, Rajesh" <rajesh.sankaran@intel.com>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Liu, Kent" <kent.liu@intel.com>,
	Youquan Song <youquan.song@linux.intel.com>
Subject: Re: [PATCH v4] x86, vt-d: enable x2apic opt out
Date: Thu, 9 Jun 2011 11:34:32 -0400	[thread overview]
Message-ID: <20110609153432.GA12741@linux-youquan.bj.intel.com> (raw)
In-Reply-To: <1306366670.2029.46.camel@i7.infradead.org>

 
> Is that going to make these broken BIOSes fall over too? If so, it
> really does look like the placement of this bit in the DMAR table is
> entirely wrong.
> 
> Rajesh, can you tell use *exactly* what is the BIOS brokenness that this
> hack was invented to work around?
> 
Hi Ingo and David,

IMO, the OPT-OUT flag is not good solution to workround BIOS or platform
issues. 
But some custmoers really requires it to 1) meet their business target.
2) some components in OEM platforms have issue if they generate
platform-events like SMI, or SMM handlers, some interrupt from LAPIC,
because they does not go through VT-d,so they do not know CPU in x2APIC
or xAPIC. 

Can you take it to maintainer tree? 
It will be better for OSVs integration. 
   
Thanks
-Youquan

      reply	other threads:[~2011-06-09  3:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 16:36 Youquan Song
2011-05-25 20:58 ` Ingo Molnar
2011-05-25 22:01   ` Thomas Gleixner
2011-05-25 23:37     ` Woodhouse, David
2011-06-09 15:34       ` Youquan Song [this message]

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=20110609153432.GA12741@linux-youquan.bj.intel.com \
    --to=youquan.song@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.m.kay@intel.com \
    --cc=asit.k.mallick@intel.com \
    --cc=david.woodhouse@intel.com \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kent.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rajesh.sankaran@intel.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=youquan.song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome