linux-kernel - Re: [PATCH 1/2] Hyperv detection

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: <4BF3D7130200003000085657@sinclair.provo.novell.com>
Date:	Wed, 19 May 2010 12:18:27 -0600
From:	"Ky Srinivasan" <ksrinivasan@...ell.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	<greg@...ah.com>, <hjanssen@...rosoft.com>,
	"Avi Kivity" <avi@...hat.com>, <mingo@...hat.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] Hyperv detection - code cleanup



>>> On 5/19/2010 at  1:51 PM, in message <4BF4252E.6090609@...or.com>, "H. Peter
Anvin" <hpa@...or.com> wrote: 
> On 05/19/2010 10:12 AM, Ky Srinivasan wrote:
>> 
>> From: K. Y. Srinivasan <ksrinivasan@...ell.com>
>> Subject: Code cleanup - consolidate all hyperv related definitions into one
>> header file.
>> 
> 
> How will this affect KVM?  I was under the impression that this was
> separated out as a constants-only header file for a reason.

I was under the impression that hyperv.h was for all public definitions of  Hyperv. I am hoping Avi can shed some light on KVM implications (if any). 

Regards,

K. Y
> 
> 	-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/