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: Greg KH <greg@kroah.com>,
	xen-devel@lists.xensource.com,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [PATCH 2.6.12.6-xen] sysfs attributes for xen
Date: Mon, 30 Jan 2006 12:17:17 -0500	[thread overview]
Message-ID: <43DE4A1D.4050501@us.ibm.com> (raw)
In-Reply-To: <1138640666.19801.106.camel@localhost.localdomain>

Dave Hansen wrote:
> In the final version, there will be available Xen headers, and the patch
> won't need the open-coded 1024?

Good question, I need some advice. The Xen hcall headers get soft-linked into every paravirtualized OS tree: linux, bsd, solaris, etc. In linux right now the xen version.h shows up as  /include/asm-xen/version.h.

This file uses typedefs for every important parameter. For example, typedef char [1024] xen_capabilities_info_t;. 

But as Greg says TYPEDEFS ARE EVIL. 

Last resort would be to use the funky gcc #include_next to override the xen hcall headers with a linux-specific hcall headers. But I don't know if that would be cool with lkml either. 

So, advice would be welcome :). 

thanks, 

Mike


-- 



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: Re: [PATCH 2.6.12.6-xen] sysfs attributes for xen
Date: Mon, 30 Jan 2006 12:17:17 -0500	[thread overview]
Message-ID: <43DE4A1D.4050501@us.ibm.com> (raw)
In-Reply-To: <1138640666.19801.106.camel@localhost.localdomain>

Dave Hansen wrote:
> In the final version, there will be available Xen headers, and the patch
> won't need the open-coded 1024?

Good question, I need some advice. The Xen hcall headers get soft-linked into every paravirtualized OS tree: linux, bsd, solaris, etc. In linux right now the xen version.h shows up as  /include/asm-xen/version.h.

This file uses typedefs for every important parameter. For example, typedef char [1024] xen_capabilities_info_t;. 

But as Greg says TYPEDEFS ARE EVIL. 

Last resort would be to use the funky gcc #include_next to override the xen hcall headers with a linux-specific hcall headers. But I don't know if that would be cool with lkml either. 

So, advice would be welcome :). 

thanks, 

Mike


-- 

  reply	other threads:[~2006-01-30 17:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28  2:20 [PATCH 2.6.12.6-xen] sysfs attributes for xen Mike D. Day
2006-01-28  2:20 ` Mike D. Day
2006-01-28  2:25 ` Greg KH
2006-01-28  2:38 ` Greg KH
2006-01-28 12:23   ` Vincent Hanquez
2006-01-28  3:03 ` [Xen-devel] " Anthony Liguori
2006-01-28  3:03   ` Anthony Liguori
2006-01-30 16:18 ` Dave Hansen
2006-01-30 16:58   ` [Xen-devel] " Mike D. Day
2006-01-30 16:58     ` Mike D. Day
2006-01-30 17:04     ` [Xen-devel] " Dave Hansen
2006-01-30 17:04       ` Dave Hansen
2006-01-30 17:17       ` Mike D. Day [this message]
2006-01-30 17:17         ` Mike D. Day
2006-01-30 17:26         ` [Xen-devel] " Greg KH
2006-01-30 17:38         ` Dave Hansen
2006-01-30 17:38           ` Dave Hansen
2006-01-30 17:53           ` [Xen-devel] " Keir Fraser
2006-01-30 17:53             ` Keir Fraser
2006-01-30 17:56             ` [Xen-devel] " Dave Hansen
2006-01-30 17:56               ` Dave Hansen
2006-01-30 19:33             ` [Xen-devel] " 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=43DE4A1D.4050501@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.