| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 11 May 2011 23:39:23 -0400 From: Youquan Song <youquan.song@...ux.intel.com> To: "Woodhouse, David" <david.woodhouse@...el.com> Cc: "Song, Youquan" <youquan.song@...el.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "mingo@...e.hu" <mingo@...e.hu>, "tglx@...utronix.de" <tglx@...utronix.de>, "hpa@...or.com" <hpa@...or.com>, "hpa@...ux.intel.com" <hpa@...ux.intel.com>, "Kay, Allen M" <allen.m.kay@...el.com>, "Siddha, Suresh B" <suresh.b.siddha@...el.com>, "Liu, Kent" <kent.liu@...el.com>, Youquan Song <youquan.song@...ux.intel.com>, rajesh.sankaran@...el.com, asit.k.mallick@...el.com Subject: Re: [PATCH v2] x86, vt-d: enable x2apic opt out > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists