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]
Message-ID: <20080911063523.GA27877@elte.hu>
Date:	Thu, 11 Sep 2008 08:35:23 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Sheng Yang <sheng.yang@...el.com>
Cc:	linux-kernel@...r.kernel.org, Avi Kivity <avi@...ranet.com>
Subject: Re: [PATCH 0/2] Clean up for MSR_IA32_FEATURE_CONTROL


* Sheng Yang <sheng.yang@...el.com> wrote:

> Hi, Ingo
> 
> Here is some follow up clean up for "Move VMX MSRs to msr-index.h". 
> After discussion with Avi, I found it's more proper to move 
> MSR_IA32_FEATURE_CONTROL bits to msr-index.h as well.
> 
> But I got a little puzzle about where to accept these patches. I 
> suppose these can be picked up by tip then go with kvm when it merge 
> upstream? The main problem is macro name changed to keep consistent 
> style.

there's a few changes pending for that file:

  earth4:~/tip> gll linus.. include/asm-x86/msr-index.h
  315a655: x86: move VMX MSRs to msr-index.h
  77ef50a: x86: consolidate header guards

so i guess best is to put 315a655 into kvm.git as well and do these 
changes there. The header-guard changes should not cause significant 
merge trouble.

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