linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Haiyang Zhang <haiyangz@microsoft.com>
To: Greg KH <greg@kroah.com>, Hank Janssen <hjanssen@microsoft.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Problem with auto-detecting a HV environment from within Linux
Date: Fri, 26 Feb 2010 19:07:14 +0000	[thread overview]
Message-ID: <1FB5E1D5CA062146B38059374562DF725B6A6D15@TK5EX14MBXC130.redmond.corp.microsoft.com> (raw)
In-Reply-To: <20100226025721.GA10310@kroah.com>

> From: Greg KH [mailto:greg@kroah.com]
> Sent: Thursday, February 25, 2010 9:57 PM
> In looking at the second patch again, I think you will need to put some
> spaces in the DMI strings to get it to match up properly.  Look at what
> the files in:
> 	/sys/class/dmi/id/
> look like exactly to get it to line up.  The module id stuff strips
> spaces out, so I can't get the real value there.

Thanks for your help! I have applied the two patches -- auto loading of hv_vmbus works fine after a space was inserted into the DMI strings ("Microsoft Corporation", "Virtual Machine").

Also, according to our Hyper-V team, we have no plan to change the virtual VGA card id and DMI info.

Thanks,

- Haiyang

  reply	other threads:[~2010-02-26 19:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 16:44 Problem with auto-detecting a HV environment from within Linux Greg KH
2010-02-25 17:30 ` Haiyang Zhang
2010-02-25 17:36   ` Greg KH
2010-02-25 18:37     ` Haiyang Zhang
2010-02-25 23:06       ` Greg KH
2010-02-25 23:40         ` Haiyang Zhang
2010-02-26  0:21           ` Greg KH
2010-02-26  0:46           ` Greg KH
2010-02-26  2:14             ` Hank Janssen
2010-02-26  2:57               ` Greg KH
2010-02-26 19:07                 ` Haiyang Zhang [this message]
2010-02-26 19:16                   ` Greg KH
2010-02-26  9:47             ` Ameya Palande
2010-02-26 14:54               ` Greg KH

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=1FB5E1D5CA062146B38059374562DF725B6A6D15@TK5EX14MBXC130.redmond.corp.microsoft.com \
    --to=haiyangz@microsoft.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=hjanssen@microsoft.com \
    --cc=linux-kernel@vger.kernel.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).