xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: julien.grall@citrix.com, xen-devel@lists.xensource.com
Subject: Re: [PATCH 2/2] xen/arm: support compressed kernels
Date: Wed, 12 Aug 2015 16:43:03 +0100	[thread overview]
Message-ID: <1439394183.8356.56.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1508121612300.11337@kaball.uk.xensource.com>

On Wed, 2015-08-12 at 16:22 +0100, Stefano Stabellini wrote:
> -obj-bin-$(CONFIG_X86) += $(foreach n,decompress gunzip bunzip2 unxz
> > > unlzma unlzo unlz4 earlycpio,$(n).init.o)
> > > +obj-bin-y += $(foreach n,decompress gunzip bunzip2 unxz unlzma unlzo 
> > > unlz4 earlycpio,$(n).init.o)
> > 
> > I don't think we need/want earlycpio support on ARM (not yet anyway).
> 
> Unfortunately it is not possible to only compile some and not all
> because decompress.c makes use of them all.


earlycpio isn't a decompression algorithm though, it just happens to be
bundled into the same obj-bin. I don't see any sign of cpio support in
decompress.c (since that wouldn't make sense).

> 
> > >  obj-$(perfc)       += perfc.o
> > >  obj-$(crash_debug) += gdbstub.o
> > > diff --git a/xen/include/asm-arm/byteorder.h b/xen/include/asm
> > > -arm/byteorder.h
> > > index 9c712c4..3b7feda 100644
> > > --- a/xen/include/asm-arm/byteorder.h
> > > +++ b/xen/include/asm-arm/byteorder.h
> > > @@ -5,6 +5,8 @@
> > >  
> > >  #include <xen/byteorder/little_endian.h>
> > >  
> > > +#define CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS
> > 
> > While CONFIG_HAVE_UNALIGNED_ACCESS might be true on arm64 it may not be 
> > the
> > case that it is efficient. Also I'm not sure about arm32 at all.
> 
> It is true on arm archs >= v8,

I'm not sure about that.

>  so we should be fine. See:
> 
> http://lwn.net/Articles/540022/

Even this says it is not always the best option, but this is not fast path
code so never mind.

Also if it isn't true for armv7 you shouldn't set it unconditionally, it
needs either an ifdef or for arm{32,64}/byteorder.h to have it.

On x86 this #define is in config.h, please lets be consistent. Also that
makes more sense anyway since alignment != byteorder.

Ian.

  parent reply	other threads:[~2015-08-12 15:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 14:47 [PATCH 0/2] support compressed kernels on ARM64 Stefano Stabellini
2015-08-12 14:47 ` [PATCH 1/2] xen: move perform_gunzip to common Stefano Stabellini
2015-08-12 15:14   ` Jan Beulich
2015-08-12 16:15     ` Stefano Stabellini
2015-08-13  6:29       ` Jan Beulich
2015-08-13  9:28         ` Stefano Stabellini
2015-08-13  9:57           ` Jan Beulich
2015-08-13 10:17             ` Ian Campbell
2015-08-13 10:27               ` Jan Beulich
2015-08-12 14:47 ` [PATCH 2/2] xen/arm: support compressed kernels Stefano Stabellini
2015-08-12 15:03   ` Ian Campbell
2015-08-12 15:20     ` Julien Grall
2015-08-12 15:22     ` Stefano Stabellini
2015-08-12 15:27       ` Julien Grall
2015-08-12 15:35       ` Jan Beulich
2015-08-12 15:40         ` Stefano Stabellini
2015-08-12 15:43       ` Ian Campbell [this message]
2015-08-12 15:09   ` Julien Grall
2015-08-12 16:35   ` Andrew Cooper
2015-08-12 17:00     ` Julien Grall

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=1439394183.8356.56.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --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).