From: Borislav Petkov <bp@alien8.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Greg KH (gregkh@linuxfoundation.org)"
<gregkh@linuxfoundation.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>
Subject: Re: 0xB16B00B5? Really? (was Re: Move hyperv out of the drivers/staging/ directory)
Date: Thu, 19 Jul 2012 17:30:15 +0200 [thread overview]
Message-ID: <20120719153014.GA13235@x1.osrc.amd.com> (raw)
In-Reply-To: <426367E2313C2449837CD2DE46E7EAF923547292@SN2PRD0310MB382.namprd03.prod.outlook.com>
On Thu, Jul 19, 2012 at 02:11:47AM +0000, KY Srinivasan wrote:
> As I noted earlier, this is just a guest ID that needs to be
> registered with the hypervisor. Thanks for reporting this issue and
> on behalf of Microsoft, I would like to apologize for this offensive
> string. I have submitted a patch to fix this issue.
Ok, quick question:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542653%28v=vs.85%29.aspx
says that that guest ID encodes a bunch of version numbers and IDs
pertaining to the guest OS. And in that case, I would've thought
you'd encode kernel versions or whatever like it is done with
LINUX_VERSION_CODE, for example.
How does this define fit with that scheme or was it chosen completely
arbitrarily?
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-07-19 15:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 16:17 Hyper-V TODO file K. Y. Srinivasan
2011-09-22 16:05 ` Joe Perches
2011-09-22 17:04 ` Greg KH
2011-09-22 17:20 ` KY Srinivasan
2011-09-22 17:36 ` Greg KH
2011-09-22 18:22 ` KY Srinivasan
2011-10-04 13:59 ` KY Srinivasan
2011-10-04 17:04 ` Greg KH
2011-10-04 17:23 ` KY Srinivasan
2011-10-04 19:34 ` Move hyperv out of the drivers/staging/ directory Greg KH
2011-10-04 21:22 ` KY Srinivasan
2011-10-05 2:49 ` KY Srinivasan
2012-07-13 10:23 ` 0xB16B00B5? Really? (was Re: Move hyperv out of the drivers/staging/ directory) Paolo Bonzini
2012-07-13 13:13 ` KY Srinivasan
2012-07-13 13:15 ` Paolo Bonzini
2012-07-13 13:21 ` KY Srinivasan
2012-07-13 20:30 ` 2976579765? " Paul Bolle
2012-07-13 13:24 ` 0xB16B00B5? " Borislav Petkov
2012-07-13 19:00 ` Steven Rostedt
2012-07-14 10:50 ` Borislav Petkov
2012-07-19 2:11 ` KY Srinivasan
2012-07-19 15:30 ` Borislav Petkov [this message]
2012-07-19 15:53 ` KY Srinivasan
2012-07-19 21:07 ` Greg KH (gregkh@linuxfoundation.org)
2012-07-19 21:22 ` KY Srinivasan
2012-07-19 22:01 ` Greg KH (gregkh@linuxfoundation.org)
2012-07-19 22:30 ` KY Srinivasan
2012-07-19 23:18 ` Anthony Liguori
2012-07-20 0:37 ` KY Srinivasan
2012-07-19 23:28 ` Greg KH (gregkh@linuxfoundation.org)
2012-07-20 0:41 ` KY Srinivasan
2012-07-20 7:59 ` Bjørn Mork
2012-07-20 8:03 ` [PATCH] drivers: hv: use Linux version in guest ID Bjørn Mork
2012-07-20 15:26 ` Greg KH
2012-07-20 16:02 ` KY Srinivasan
2012-07-20 14:00 ` 0xB16B00B5? Really? (was Re: Move hyperv out of the drivers/staging/ directory) KY Srinivasan
2012-07-20 15:03 ` richard -rw- weinberger
2012-07-20 15:16 ` KY Srinivasan
2012-07-21 23:21 ` valdis.kletnieks
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=20120719153014.GA13235@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).