All of lore.kernel.org
 help / color / mirror / Atom feed
From: Youquan Song <youquan.song@linux.intel.com>
To: "Woodhouse, David" <david.woodhouse@intel.com>
Cc: "Song, Youquan" <youquan.song@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"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>,
	"Liu, Kent" <kent.liu@intel.com>,
	Youquan Song <youquan.song@linux.intel.com>,
	rajesh.sankaran@intel.com, asit.k.mallick@intel.com
Subject: Re: [PATCH v2] x86, vt-d: enable x2apic opt out
Date: Wed, 11 May 2011 23:39:23 -0400	[thread overview]
Message-ID: <20110512033923.GA19708@linux-youquan.bj.intel.com> (raw)
In-Reply-To: <1305126431.30435.163.camel@i7.infradead.org>

 
> Given that x2apic is *required* to be safe from irq injection tricks,
> why would we ever want to manually disable it?
> Is this just a workaround for a crappy BIOS? What is the *actual* reason
> for wanting to disable x2apic?

The VT-d 1.3 version specification add this new feature because OEM
request it. If OEM platform has issues to support x2apic or BIOS is 
buggy to support x2apic, there is alternative way to opt out x2apic. 

Refer to VT-d 1.3 specification Chpater 8.1.

Thanks
-Youquan


  reply	other threads:[~2011-05-11 15:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  7:06 [PATCH v2] x86, vt-d: enable x2apic opt out Youquan Song
2011-05-11 15:07 ` Woodhouse, David
2011-05-12  3:39   ` Youquan Song [this message]
2011-05-11 15:39     ` David Woodhouse
2011-05-11 22:38       ` Valdis.Kletnieks
2011-05-16 20:32   ` Alex Williamson
2011-05-17  9:49     ` Woodhouse, David
2011-05-17 12:50       ` Alex Williamson
2011-05-18 22:58     ` Woodhouse, David
2011-05-19  5:43       ` Alex Williamson
2011-05-11 17:21 ` Woodhouse, David
2011-05-12  1:52 ` Youquan Song

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=20110512033923.GA19708@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 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.