From: Greg KH <greg@kroah.com>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: devel@driverdev.osuosl.org, Virtualization@lists.osdl.org,
Haiyang Zhang <haiyangz@microsoft.com>, Greg KH <gregkh@suse.de>
Subject: Re: [PATCH]: An implementation of HyperV KVP functionality
Date: Thu, 11 Nov 2010 13:19:04 -0800 [thread overview]
Message-ID: <20101111211904.GB31373@kroah.com> (raw)
In-Reply-To: <4CDBE98E02000030000902C9@novprvoes0310.provo.novell.com>
On Thu, Nov 11, 2010 at 01:03:10PM -0700, Ky Srinivasan wrote:
> +/*
> + * Array of keys we support in Linux.
Not really, you can support "any" number of keys as the kernel shouldn't
care, or did I get it wrong?
> + *
> + */
> +#define KVP_MAX_KEY 10
> +#define KVP_LIC_VERSION 1
Um, this is a nice magic number, care to explain it a bit more?
> +static char *kvp_keys[KVP_MAX_KEY] = {"FullyQualifiedDomainName",
> + "IntegrationServicesVersion",
Looks like it matches up with this, right? You might want to make that
a bit more "tied" together.
> + case (KVP_LIC_VERSION):
> + kvp_transaction_active = true;
> + kvp_respond_to_host(kvp_data->index,
> + HV_DRV_VERSION);
Why are you doing this in the kernel? Why not do it from userspace like
all other messages?
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-11 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 20:03 [PATCH]: An implementation of HyperV KVP functionality Ky Srinivasan
2010-11-11 20:49 ` Stephen Hemminger
2010-11-12 16:57 ` Ky Srinivasan
2010-11-12 16:57 ` Ky Srinivasan
2010-11-12 16:57 ` Ky Srinivasan
2010-11-11 21:15 ` Greg KH
2010-11-12 18:06 ` Ky Srinivasan
2010-11-12 18:47 ` Greg KH
2010-11-12 20:59 ` Ky Srinivasan
2010-11-12 21:38 ` Greg KH
2010-11-11 21:19 ` Greg KH [this message]
2010-11-12 18:29 ` Ky Srinivasan
2010-11-12 19:22 ` Greg KH
2010-11-14 10:46 ` Dor Laor
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=20101111211904.GB31373@kroah.com \
--to=greg@kroah.com \
--cc=Virtualization@lists.osdl.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=ksrinivasan@novell.com \
/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.