All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Arnold" <carnold@suse.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Matt Wilson <msw@amazon.com>
Subject: Re: Support for btrfs in pv-grub
Date: Fri, 28 Feb 2014 08:24:57 -0700	[thread overview]
Message-ID: <531047D902000091000B9532@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20140228033029.GA14114@u109add4315675089e695.ant.amazon.com>

>>> On 2/27/2014 at 08:30 PM, Matt Wilson <msw@linux.com> wrote: 
> On Fri, Feb 28, 2014 at 02:42:28AM +0000, Ian Campbell wrote:
>> On Wed, 2014-02-26 at 15:59 -0700, Charles Arnold wrote:
>> > Code to support btrfs in pv-grub was added almost two years ago (c/s 25154).
>> 
>> Ccing the author.
>> 
>> > Building the code doesn't seem to be enabled in stubdom/grub/Makefile.
>> > Was this functionality ever intended to work?
>> 
>> One would like to assume so!
>> 
>> > Does anyone know the status of this code?
>> 
>> Matt?
>> 
>> Looks like Makefile.am was patched but not Makefile.in, and I don't
>> think we run automake as part of the stubdom build process.
> 
> True, but we also don't use the Makefiles in grub-upstream to build
> GRUB. We use xen/stubdom/grub/Makefile, which also isn't patched to
> build the btrfs code.
> 
> Unfortunately when I added it grub/Makefile, it doesn't build on a
> modern compiler.
> 
> Do you think we should revert the patch that adds btrfs support?
> 
> --msw

Another option would be to fix the compiler errors and get it working :)
The compiler has problems with the cassert define and to many args in
the call to next_partition in the 61btrfs.diff patch.  These issues may be
worked around but given that the code has never actually been used there
may be runtime problems as well.  Is there someone familiar enough with
btrfs on the list to work through these issues?

- Charles

  reply	other threads:[~2014-02-28 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 22:59 Support for btrfs in pv-grub Charles Arnold
2014-02-28  2:42 ` Ian Campbell
2014-02-28  3:30   ` Matt Wilson
2014-02-28 15:24     ` Charles Arnold [this message]
2014-03-11 10:58     ` Ian Campbell

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=531047D902000091000B9532@prv-mh.provo.novell.com \
    --to=carnold@suse.com \
    --cc=msw@amazon.com \
    --cc=xen-devel@lists.xen.org \
    /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.