From: Laurent Vivier <lvivier@redhat.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: Will Deacon <will.deacon@arm.com>,
kvm@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
Michael Neuling <mikey@neuling.org>,
kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/5] Add support for ppc64le in kvmtool
Date: Mon, 4 Apr 2016 14:21:52 +0200 [thread overview]
Message-ID: <57025C60.4000006@redhat.com> (raw)
In-Reply-To: <CAKTCnz=zRNaMKoYj+6BTxRsbD297prUaWQLePTP+9BcB+tWNTg@mail.gmail.com>
On 04/04/2016 12:24, Balbir Singh wrote:
>>>
>>
>> This is helpful but I didn't have the time to try again.
>>
>> Just one more question: how do you strip the ELF header (step 3)?
>
> I use
>
> objcopy -O binary vmlinux vmlinux.bin
Many thanks!
It was the missing part :)
I'm able to boot a big-endian kernel now, I'll test your patches as soon
as I have access to a little-endian capable host.
Laurent
next prev parent reply other threads:[~2016-04-04 12:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 11:28 [PATCH 0/5] Add support for ppc64le in kvmtool Balbir Singh
2016-03-31 11:28 ` [PATCH 1/5] Add basic little endian support Balbir Singh
2016-03-31 11:28 ` [PATCH 2/5] Add basic infrastructure to run tasks on vCPUs Balbir Singh
2016-04-01 10:42 ` Michael Ellerman
2016-04-01 11:29 ` Balbir Singh
2016-04-01 12:27 ` Will Deacon
2016-04-07 1:12 ` Balbir Singh
2016-03-31 11:28 ` [PATCH 3/5] Implement H_SET_MODE for ppc64le Balbir Singh
2016-03-31 11:28 ` [PATCH 4/5] Fix a race during exit processing Balbir Singh
2016-04-11 15:37 ` Will Deacon
2016-03-31 11:28 ` [PATCH 5/5] Implement spapr pci for little endian systems Balbir Singh
2016-03-31 13:38 ` [PATCH 0/5] Add support for ppc64le in kvmtool Laurent Vivier
2016-04-01 0:12 ` Balbir Singh
2016-04-04 8:34 ` Balbir Singh
2016-04-04 8:41 ` Laurent Vivier
2016-04-04 10:24 ` Balbir Singh
2016-04-04 12:21 ` Laurent Vivier [this message]
2016-04-01 10:47 ` Michael Ellerman
2016-04-01 10:48 ` Will Deacon
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=57025C60.4000006@redhat.com \
--to=lvivier@redhat.com \
--cc=bsingharora@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=will.deacon@arm.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).