Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Chris Patterson <cjp256@gmail.com>,
	 Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu: upgrade to 1.6.1
Date: Tue, 29 Oct 2013 13:30:30 -0700	[thread overview]
Message-ID: <52701AE6.30106@linux.intel.com> (raw)
In-Reply-To: <CABZSBQfM7hwgF7ZtmypBzJQoTGPObow59zADZdbnaEK-+YO-Jw@mail.gmail.com>

On 10/29/2013 01:20 PM, Chris Patterson wrote:
>
>
>
> On Tue, Oct 29, 2013 at 3:27 AM, Laurentiu Palcu
> <laurentiu.palcu@intel.com <mailto:laurentiu.palcu@intel.com>> wrote:
>
>     Hi Chris,
>
>     On Mon, Oct 28, 2013 at 07:54:51PM -0400, Chris Patterson wrote:
>      >
>      > I'm not terribly familiar with the nativesdk, and (foolishly)
>     neglected to test
>      > that.  However, I looked into it, and it looks like the
>     relocatable_sdk.patch
>      > affects a linker script that is no longer available.  I dropped
>     the patch and
>      > tested installing an oe-core sdk sysroot (via bitbake -c populate_sdk
>      > core-image-minimal) and qemu appears to work fine from within the sdk
>      > environment.
>      >
>      > I'm open to suggestions for further testing this upgrade
>     (particularly a case
>      > to cover what relocatable_sdk.patch was originally intended to
>     resolve). I'm
>      > certainly not the expert here, but am willing to help out.
>      >
>     To test this particular case, build meta-toolchain and install it in a
>     different location than the default one. Then, just do a 'readelf -s"
>     on any qemu binary and make sure the .interp section has a size of
>     0x1000 bytes.
>
>     If it does, then it's ok to drop the patch. That patch was needed
>     because qemu happened to use their own linker scripts and, in order to
>     have the SDK relocatable, we needed to reseve space in the .interp
>     section to squeeze the new path.
>
>
> Thanks Laurentiu - I did validate that the interp section looks to be
> 0x1000 bytes for the qemu-* binaries:
>
> $
> /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/qemu-system-arm
> --version
> QEMU emulator version 1.6.1, Copyright (c) 2003-2008 Fabrice Bellard
>
> $ readelf -S
> /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/qemu-system-arm
>
> There are 29 section headers, starting at offset 0x5a14b8:
>
> Section Headers:
>    [Nr] Name              Type             Address           Offset
>         Size              EntSize          Flags  Link  Info  Align
>    [ 0]                   NULL             0000000000000000  00000000
>         0000000000000000  0000000000000000           0     0     0
>    [ 1] .interp           PROGBITS         0000000000000270  00000270
>         0000000000001000  0000000000000000   A       0     0     1
>    [ 2] .note.ABI-tag     NOTE             0000000000001270  00001270
>         0000000000000020  0000000000000000   A       0     0     4
>    [ 3] .note.gnu.build-i NOTE             0000000000001290  00001290
> ...
>
> If anyone has any other suggestions to test, I will gladly attempt them
> before posting a v2.
>

Your last message said you tested core-image-minimal, did you do any 
testing with a graphical image like core-image sato?  We really 
apperciate the work you put in here.

Thanks
	Sau!

> Cheers!
> -Chris


  reply	other threads:[~2013-10-29 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  0:15 [PATCH] qemu: upgrade to 1.6.1 Chris Patterson
2013-10-24  8:48 ` Saul Wold
2013-10-28 23:54   ` Chris Patterson
2013-10-29  7:27     ` Laurentiu Palcu
2013-10-29 20:20       ` Chris Patterson
2013-10-29 20:30         ` Saul Wold [this message]
2013-10-30 11:49           ` Chris Patterson

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=52701AE6.30106@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=cjp256@gmail.com \
    --cc=laurentiu.palcu@intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox