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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 30 Jul 2008 10:14:21 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"roland@...hat.com" <roland@...hat.com>,
	"drepper@...hat.com" <drepper@...hat.com>,
	"mikpe@...uu.se" <mikpe@...uu.se>,
	"chrisw@...s-sol.org" <chrisw@...s-sol.org>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [patch 0/9] x86, xsave: xsave/xrstor support

Suresh Siddha wrote:

>> It somewhat concerns me, because one of the conflicts is generated by
>> collision with x2apic.  The rest of them I don't think are too problematic.
> 
> hpa, confilicts with x2apic branch are very small and related to cpuid bits.
> 
> commit 04df16d2465cbb59b84c9c57ad865dbbeebadad8
> Author: Suresh Siddha <suresh.b.siddha@...el.com>
> Date:   Tue Jul 29 10:29:18 2008 -0700
> 
>     x86, xsave: xsave cpuid feature bits
> 
>     Add xsave CPU feature bits.
>     
> and 
> 
> commit 32e1d0a0651004f5fe47f85a2a5c725ad579a90c
> Author: Suresh Siddha <suresh.b.siddha@...el.com>
> Date:   Thu Jul 10 11:16:50 2008 -0700
> 
>     x64, x2apic/intr-remap: cpuid bits for x2apic feature
>     
>     cpuid feature for x2apic.
> 
> Both of these patches are straight forward, simple and can be moved
> to x86/core(?) now, if that helps.

This is true.  Cherry-picking those to the x86/core branch is probably 
the easiest, even if that means they're duplicated in the x2apic branch 
(I presume we don't want to rebase x2apic).

	-hpa
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ