WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH][TOOLS] libfsimage: portability fixes

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][TOOLS] libfsimage: portability fixes
From: Christoph Egger <Christoph.Egger@xxxxxxx>
Date: Thu, 27 Mar 2008 16:13:33 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 27 Mar 2008 08:16:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <18411.31985.471754.46628@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200803261514.33378.Christoph.Egger@xxxxxxx> <18411.31985.471754.46628@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.7
On Thursday 27 March 2008 11:54:41 Ian Jackson wrote:
> Christoph Egger writes ("[Xen-devel] [PATCH][TOOLS] libfsimage: portability 
fixes"):
> > -SUBDIRS-y += $(shell env CC="$(CC)" ./check-libext2fs)
> > +SUBDIRS-y += $(shell $(SHELL) env CC="$(CC)" ./check-libext2fs)
>
> What purpose does this serve ?

Everytime when I submitted a patch where I changed /bin/bash to /bin/sh
John Levon came up with a "Build is broken on Solaris" message.
The fix was always the same: Use $(SHELL) as this is explicitely set for
Solaris.

> > +   /*
> > +    * Make reads from a raw disk sector-aligned. This is a requirement
> > +    * for NetBSD. Split the read up into to three parts to meet this
> > +    * requirement.
> > +    */
>
> Please forgive my ignorance: Does NetBSD offer a different (non-raw)
> device which does not have this requirement.  If so perhaps we should
> be using it instead - if not, why not ?

The raw device pass requests directly to the underlying device, with
only check/adjustments against the partition bounds. Especially it won't
try to do read/modify/write for write requests, or expand the read if it's
not sector-aligned.

The block device doesn't have this restriction, but allows only ONE open,
therefore it is not usable by pygrub. It also has other side-effects
(as it goes through the buffer cache), it's definitively not useable for the 
NetBSD block device *backend*   or for qemu-dm I/O.

Christoph


-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel