All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: xen-devel@lists.xensource.com,
	lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor	attributes to sysfs
Date: Tue, 21 Feb 2006 12:48:43 -0500	[thread overview]
Message-ID: <43FB527B.5030404@us.ibm.com> (raw)
In-Reply-To: <1140542130.8693.18.camel@localhost.localdomain>

Dave Hansen wrote:
> It could be:
> 
> +---sys
>         +---hypervisor
>                 +---type
> 		+---version
>                         +---major
>                         +---minor
>                         +---extra
> 

Yeah, the type file could be useful.

>> +static ssize_t extra_show(struct kobject * kobj,
>> +			  struct attribute * attr,
>> +			  char * page)
>> +{
>> +	char extra_ver[XENVER_EXTRAVERSION_LEN];
> 
> At 1k, this is a wee bit too big to be on the stack.  I'd just kmalloc
> it instead.

This particular constant is 16 bytes so I'll leave it as is. The other 
one (CAPABILTIES_INFO), which is 1k, I did kmalloc as you suggested.

>> +static void xen_compilation_destroy(void)
>> +{
>> +	sysfs_remove_group(c_kobj, &xen_compilation_group);
>> +	kobject_put(c_kobj);
>> +	return;
>> +}
> 
> Yup, this is another excellent function name.

I'll change the others to be as descriptive. Thanks,

Mike Day

WARNING: multiple messages have this Message-ID (diff)
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Greg KH <greg@kroah.com>,
	xen-devel@lists.xensource.com,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor	attributes to sysfs
Date: Tue, 21 Feb 2006 12:48:43 -0500	[thread overview]
Message-ID: <43FB527B.5030404@us.ibm.com> (raw)
In-Reply-To: <1140542130.8693.18.camel@localhost.localdomain>

Dave Hansen wrote:
> It could be:
> 
> +---sys
>         +---hypervisor
>                 +---type
> 		+---version
>                         +---major
>                         +---minor
>                         +---extra
> 

Yeah, the type file could be useful.

>> +static ssize_t extra_show(struct kobject * kobj,
>> +			  struct attribute * attr,
>> +			  char * page)
>> +{
>> +	char extra_ver[XENVER_EXTRAVERSION_LEN];
> 
> At 1k, this is a wee bit too big to be on the stack.  I'd just kmalloc
> it instead.

This particular constant is 16 bytes so I'll leave it as is. The other 
one (CAPABILTIES_INFO), which is 1k, I did kmalloc as you suggested.

>> +static void xen_compilation_destroy(void)
>> +{
>> +	sysfs_remove_group(c_kobj, &xen_compilation_group);
>> +	kobject_put(c_kobj);
>> +	return;
>> +}
> 
> Yup, this is another excellent function name.

I'll change the others to be as descriptive. Thanks,

Mike Day

  reply	other threads:[~2006-02-21 17:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 14:40 [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor attributes to sysfs Mike D. Day
2006-02-21 17:15 ` Dave Hansen
2006-02-21 17:15   ` Dave Hansen
2006-02-21 17:48   ` Mike D. Day [this message]
2006-02-21 17:48     ` Mike D. Day
2006-02-22 12:32   ` Heiko Carstens
2006-02-22 12:37     ` Mike D. Day
2006-02-22 12:37       ` Mike D. Day
2006-02-22 12:56       ` Arjan van de Ven
2006-02-22 13:06         ` Mike D. Day
2006-02-22 13:06           ` Mike D. Day
2006-02-22 13:19           ` Heiko Carstens
2006-02-22 13:43             ` Mike D. Day
2006-02-22 13:43               ` Mike D. Day
2006-02-22 14:01               ` Arjan van de Ven
2006-02-22 16:08                 ` Mike D. Day
2006-02-23  4:26                 ` Anthony Liguori
2006-02-23  4:26                   ` Anthony Liguori
2006-02-23  8:24                   ` Arjan van de Ven
2006-02-21 18:02 ` Alan Cox
2006-02-21 18:10 ` Greg KH
2006-02-22 12:26 ` Heiko Carstens

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=43FB527B.5030404@us.ibm.com \
    --to=ncmike@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.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.