xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Marco Nenciarini <marco.nenciarini@devise.it>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: XFS support for pygrub patch
Date: Thu, 23 Dec 2010 16:27:30 +0100	[thread overview]
Message-ID: <4D136A62.4070905@devise.it> (raw)
In-Reply-To: <4D07EE72.3060406@devise.it>

On 14/12/2010 23:23, Marco Nenciarini wrote:
> On 13/12/2010 18:06, Stefano Stabellini wrote:
>> On Fri, 26 Nov 2010, Marco Nenciarini wrote:
>>>
>>> Hi,
>>> I've ported the xfs code from grub to pygrub for our company internal use.
>>>
>>> If you find it useful fell free to merge with main code.
>>
>> Can anybody test this patch and confirm it works properly?
> 
> To help you testing the patch and auditing the code, I've attached to
> this message the diff against xfs code in grub-0.97.
> 
> As stated before, the resulting fsimage.so works perfectly for me when
> installed in XCP-0.5 as /usr/lib/fs/xfs/fsimage.so
> 
> Actually I've 3 Debian Squeeze machines and one Ubuntu 10.10 machine in
> our testing environment booting from xfs with pygrub.
> 
> The only problem I've found is that the module doesn't compile on Debian
> based system due to some bug in gcc code optimizer. On such a systems
> the compiler returns the following error:
> 
> gcc  -DPIC -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99
> -Wall -Wstrict-prototypes -Wno-unused-value
> -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .fsys_xfs.opic.d
>  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -I../../../tools/libfsimage/common/ -Werror -fPIC -c -o fsys_xfs.opic
> fsys_xfs.c
> fsys_xfs.c: In function ‘next_dentry’:
> fsys_xfs.c:409: error: extended registers have no high halves
> fsys_xfs.c:409: error: extended registers have no high halves
> 
> The problem disappear if you turn off optimization with -O0
> 

I've solved the compilation error on Ubuntu/Debian x86_64 (sed
s/"=q"/"=Q"/), but the resulting libary doesn't works (it doesn't even
recognize the XFS partition). I'll debug it during the next week.

Regards,
Marco

-- 
Marco Nenciarini - System manager @ Devise.IT
marco.nenciarini@devise.it | http://www.devise.it

  reply	other threads:[~2010-12-23 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 11:16 XFS support for pygrub patch Marco Nenciarini
2010-12-13 17:06 ` Stefano Stabellini
2010-12-14 22:23   ` Marco Nenciarini
2010-12-23 15:27     ` Marco Nenciarini [this message]
2011-01-19 12:44       ` Marco Nenciarini
2011-01-20 16:10         ` Ian Jackson
2011-01-20 16:15           ` Stefano Stabellini
2011-05-11 17:05             ` alxgomz
     [not found] <22752968ADD47840A7D404102C7563B005A82DE827@vasco-be-exch2.vasco.com>
2010-12-08 22:39 ` Marco Nenciarini
  -- strict thread matches above, loose matches on Subject: below --
2011-02-10  9:18 Adi Kriegisch
2011-02-10 11:13 ` Stefano Stabellini
2011-05-03  8:53   ` Marco Nenciarini

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=4D136A62.4070905@devise.it \
    --to=marco.nenciarini@devise.it \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).