From: Balbir Singh <bsingharora@gmail.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: will.deacon@arm.com, kvm@vger.kernel.org, mpe@ellerman.id.au,
mikey@neuling.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/5] Add support for ppc64le in kvmtool
Date: Fri, 1 Apr 2016 11:12:51 +1100 [thread overview]
Message-ID: <56FDBD03.9050504@gmail.com> (raw)
In-Reply-To: <56FD286A.9070001@redhat.com>
On 01/04/16 00:38, Laurent Vivier wrote:
> Hi,
>
>
> could you add "kvmtool" in the subject, next time, please? :)
> And it could be a good idea to send to kvm-ppc ML too.
You mean like in [kvmtool]? The cover letter does have kvmtool, I think
adding [kvmtool] tag helps. I'll keep it in mind
> On 31/03/2016 13:28, Balbir Singh wrote:
>> Changelog v2: Add support for running a task on all cpus by
>> Michael Ellerman. Large improvements to patch 2/4
>>
>> This patchset adds support for ppc64le. As a part of the support 1/4 converts
>> key data structures in the fdt to big endian. 2/4 introduces h_set_mode call
>> to support little endian interrupt processing. This requires support to execute
>> and queue commands to a particular vcpu and hence a generic infrastructure
>> is added in patch 2/4. Patch 3/4 fixes a race condition found during exit.
>> Patch 4/4 adds support for fixing spapr_pci to support little endian guests
>> so that virtio-pci can be detected and virtio can work
>>
>> This patchset was tested on x64 (on my laptop) and on a ppc64le system.
>>
>> Balbir Singh (5):
>> Add basic little endian support.
>> Add basic infrastructure to run tasks on vCPUs
>> Implement H_SET_MODE for ppc64le
>> Fix a race during exit processing
>> Implement spapr pci for little endian systems.
> I was trying to use kvmtool on ppc64, some days ago, and I was not able
> to run anything (yes, I'm stupid), So could you also update the README
> with some ppc64/ppc64le stuff explaining how to use kvmtool on POWER?
No.. I don't think anyone is stupid, may be it just doesn't work. For ppc64le
here are the steps. I'll write a README after this series is committed
1. Make sure you have this patchset
2. Compile a ppc64le_defconfig kernel
3. Strip the elf header from vmlinux (yes, we don't yet have an elf parser - TODO)
4. lkvm run -c <cpus> -m <mem{constrained to 4G}> -k <kernel from step 3> -i <initrd> -d <diskimage> -p <args> --console hv
There are two limitations that need to be fixed
1. memory is limited to 4G because of the way RTAS is currently setup in kvmtool, I have a brute force
fix for it, I'll post it after this series is merged
2. HPT size is limited to 16MB, will post a patch after this series is merged
TODOs
1. Implement an elf parser so that we don't have to do step 3
> Or give me a link to the information, and I'll do.
I hope this helps, I can do some documentation once we get the limitations and TODOs
resolved
> Thanks,
> Laurent
Thanks for looking into this
Balbir
next prev parent reply other threads:[~2016-04-01 0:12 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 [this message]
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
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=56FDBD03.9050504@gmail.com \
--to=bsingharora@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--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).