All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ky Srinivasan <ksrinivasan@novell.com>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Hank Janssen <hjanssen@microsoft.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Alok Kataria <akataria@vmware.com>
Subject: Re: RFC - Cleaned up hypervisor layer
Date: Fri, 7 May 2010 16:12:02 -0700	[thread overview]
Message-ID: <20100507231202.GA13771@kroah.com> (raw)
In-Reply-To: <4BE49D76.5000001@zytor.com>

On Fri, May 07, 2010 at 04:08:38PM -0700, H. Peter Anvin wrote:
> On 05/07/2010 04:02 PM, Greg KH wrote:
> > On Fri, May 07, 2010 at 03:43:04PM -0700, H. Peter Anvin wrote:
> >> This patch implements a cleaned up hypervisor layer, plus cleans up some
> >> of the aspects of both Hank's MS-HyperV patch and the existing VMware
> >> driver.  In particular, the MS-HyperV information is private
> >> information, per system, not per CPU, and can thus simply be stored in
> >> an ordinary global variable.  This also turns the hypervisor detection
> >> into an information structure instead of just an identifier.
> > 
> > This looks great to me, thanks for doing this work.
> > 
> > As this is a diff on top of my previous patch, do you want me to merge
> > it in with it and resend it, or will you?
> > 
> 
> I was planning to put this on top of your patch as a second commit, just
> to preserve history and authorship.

Wonderful.

Ah, I just realized that we cut-and-pasted the GPL lines from the vmware
file, I don't want the "v2 or later" marking on the new file KY added.
Want me to send an add-on patch to fix that up?

thanks,

greg k-h

  reply	other threads:[~2010-05-07 23:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 22:43 RFC - Cleaned up hypervisor layer H. Peter Anvin
2010-05-07 23:02 ` Greg KH
2010-05-07 23:08   ` H. Peter Anvin
2010-05-07 23:12     ` Greg KH [this message]
2010-05-07 23:18       ` H. Peter Anvin
2010-05-07 23:55         ` [PATCH] HyperV: fix up the license to mshyperv.c Greg KH
2010-05-08  1:58           ` [tip:x86/cpu] x86, " tip-bot for Greg Kroah-Hartman
2010-05-08  1:58 ` [tip:x86/cpu] x86: Clean up the hypervisor layer tip-bot for H. Peter Anvin
2010-05-08  8:16   ` Ingo Molnar
2010-05-19 16:54   ` [PATCH] Hyperv: Export the symbol that tracks hyperv features and recommendations Ky Srinivasan
2010-05-19 17:03     ` Greg KH
2010-05-08  5:54 ` RFC - Cleaned up hypervisor layer Dmitry Torokhov
2010-05-09  8:18 ` [tip:x86/cpu] x86, hypervisor: Export the x86_hyper* symbols tip-bot for H. Peter Anvin
2010-05-09  8:19 ` [tip:x86/cpu] Modify the VMware balloon driver for the new x86_hyper API tip-bot for H. Peter Anvin
2010-05-09  8:20   ` H. Peter Anvin
2010-05-10  8:06     ` Dmitry Torokhov
2010-05-10 15:23       ` H. Peter Anvin
2010-05-10 16:17         ` Dmitry Torokhov
2010-05-10 17:30           ` H. Peter Anvin
2010-05-10 17:52             ` Dmitry Torokhov
2010-05-10 18:05               ` H. Peter Anvin
2010-05-09 10:47   ` Ingo Molnar
2010-05-10  5:56 ` [tip:x86/cpu] x86, hypervisor: add missing <linux/module.h> tip-bot for H. Peter Anvin

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=20100507231202.GA13771@kroah.com \
    --to=greg@kroah.com \
    --cc=akataria@vmware.com \
    --cc=hjanssen@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=ksrinivasan@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.