All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: anthony.perard@citrix.com, xen-devel@lists.xensource.com,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: Xen 4.6, OVMF and arm64
Date: Wed, 14 Oct 2015 12:35:45 +0100	[thread overview]
Message-ID: <20151014113545.GI23759@zion.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510141229350.27957@kaball.uk.xensource.com>

On Wed, Oct 14, 2015 at 12:30:15PM +0100, Stefano Stabellini wrote:
> On Wed, 14 Oct 2015, Wei Liu wrote:
> > On Wed, Oct 14, 2015 at 12:25:32PM +0100, Stefano Stabellini wrote:
> > > Hi Wei, Anthony,
> > > 
> > > the OVMF revision that we use with Xen 4.6 is
> > > cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd, however that doesn't work for
> > > arm64. It is not a problem for xen.git, because the arm64 build of ovmf
> > > is not enabled in the xen tree (it is built separately). However it is a
> > > problem for raisin: I am trying to enable the ovmf build on arm64 in
> > > raisin but it fails on arm64 for the latest release (at least on CentOS
> > > 7) which is not nice.
> > > 
> > > One fix is required on top of
> > > cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd to make it work:
> > > 
> > > commit 28e80befa4fe0edd7cce876e991fed912f0f2795
> > > Author: Leif Lindholm <leif.lindholm@linaro.org>
> > > Date:   Thu Jul 9 16:29:44 2015 +0000
> > > 
> > >     BaseTools: aarch64: add -fno-asynchronous-unwind-tables to gcc cflags
> > > 
> > > 
> > > This is not required but it would be nice:
> > > 
> > > commit ad2a2e5623a4a4ac5f24ae827f7842995ef4c2a9
> > > Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > > Date:   Wed Aug 12 05:22:49 2015 +0000
> > > 
> > >     BaseTools: add ARCH detection for AARCH64 and ARM
> > > 
> > > 
> > > They only affect aarch64. Do you think it would be possible to apply
> > > them to the ovfm tree on xenbits and maybe update the ovmf revision in
> > > Config.mk, once it passes any required osstest tests?
> > > 
> > 
> > I can send a patch for Config.mk when the patch passed our tests.
> 
> OK, thanks. But can you also cherry-pick them into
> git://xenbits.xen.org/ovmf.git ?

I don't have commit access. 

What I normally do is to ask committers to do it when I send my patch --
it's a bit cumbersome, but at least it works.

Wei.

  reply	other threads:[~2015-10-14 11:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 11:25 Xen 4.6, OVMF and arm64 Stefano Stabellini
2015-10-14 11:29 ` Wei Liu
2015-10-14 11:30   ` Stefano Stabellini
2015-10-14 11:35     ` Wei Liu [this message]
2015-10-14 11:32   ` Wei Liu
2015-10-14 11:38   ` Ian Campbell
2015-10-14 12:55     ` Stefano Stabellini
2015-10-14 13:04       ` Wei Liu
2015-10-14 13:04         ` Stefano Stabellini
2015-10-14 13:24           ` Wei Liu
2015-10-14 13:35             ` Ian Campbell
2015-10-14 13:39               ` Wei Liu
2015-10-14 13:51               ` Stefano Stabellini
2015-10-14 14:10                 ` Ian Campbell
2015-10-14 14:11                   ` Stefano Stabellini
2015-10-14 14:25                     ` Ian Campbell
2015-10-14 13:05       ` 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=20151014113545.GI23759@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=anthony.perard@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 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.