From: Alexander Graf <agraf@suse.de>
To: Claudio Fontana <claudio.fontana@huawei.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"<ard.biesheuvel@linaro.org>" <ard.biesheuvel@linaro.org>,
"<rob.herring@linaro.org>" <rob.herring@linaro.org>,
"<qemu-devel@nongnu.org>" <qemu-devel@nongnu.org>,
"<mst@redhat.com>" <mst@redhat.com>,
"<a.rigo@virtualopensystems.com>" <a.rigo@virtualopensystems.com>,
"<stuart.yoder@freescale.com>" <stuart.yoder@freescale.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] ARM: Add support for a generic PCI Express host bridge
Date: Wed, 07 Jan 2015 15:36:28 +0100 [thread overview]
Message-ID: <54AD446C.5000103@suse.de> (raw)
In-Reply-To: <54AD421D.5020207@huawei.com>
On 07.01.15 15:26, Claudio Fontana wrote:
> On 07.01.2015 15:07, Alexander Graf wrote:
>>
>>
>>
>>> Am 07.01.2015 um 14:52 schrieb Claudio Fontana <claudio.fontana@huawei.com>:
>>>
>>> Hi Alexander, happy new year!
>>>
>>>> On 06.01.2015 17:03, Alexander Graf wrote:
>>>> Linux implements a nice binding to describe a "generic" PCI Express host bridge
>>>> using only device tree.
>>>>
>>>> This patch set adds enough emulation logic to expose the parts that are
>>>> "generic" as a simple sysbus device and maps it into ARM's virt machine.
>>>>
>>>> With this patch set, we can finally spawn PCI devices on ARM VMs. I was able
>>>> to have a fully DRM enabled virtual machine with VGA, e1000 and XHCI (for
>>>> keyboard and mouse) up and working.
>>>>
>>>> It's only a small step for QEMU, but a big step for ARM VM's usability.
>>>
>>> I tried to test your patches, but I get in trouble quite early:
>>>
>>> I usually run qemu-system-aarch64 for pci for OSv with the following command line (using the patches from Alvise):
>>>
>>> ./qemu-system-aarch64 -nographic -machine type=virt -enable-kvm -kernel ./loader.img -cpu host -m 1024M -drive file=usr.img,if=none,id=hd0,media=disk -device virtio-blk-pci,id=blk0,bootindex=0,drive=hd0,scsi=off,vectors=0 -device virtio-rng-pci -netdev user,id=un0,net=xxx.xxx.xxx.xxx/xx,host=xxx.xxx.xxx.xxx -redir tcp:2222::22 -device virtio-net-pci,netdev=un0,vectors=0
>>>
>>> and with this series I get:
>>>
>>> qemu-system-aarch64: Unknown device 'gpex-pcihost' for default sysbus
>>>
>>> Is there something I need to mention in the command line to enable the gpex-pcihost maybe?
>>
>> If I had to guess I'd say you're missing the object file in your binary. Did you run configure again after applying the patches?
>>
>> Alex
>
> Yes I did but it seems it's not picking up the CONFIG_PCI_GENERIC=y for some reason.
> If I force hw/pci-host/Makefile.objs to build it by making it a common-obj-y then it builds.
>
> I see the CONFIG_PCI_GENERIC in default-configs/arm-softmmu.mak,
>
> and there is a default-configs/aarch64-softmmu.mak which says
>
> include arm-softmmu.mak
>
> but still it does not seem to pick it up over here..
>
> while it picks up the CONFIG_PCI from the other mak files for example.
>
> Wierd.. does it build on AArch64 for you? Or did you test only 32bit?
Well, in fact I only tested aarch64 :). It definitely worked for me.
Can you try to do a fresh checkout and a new configure run on that one?
You should have a line saying
CONFIG_PCI_GENERIC=y
in aarch64-softmmu/config-devices.mak.
Alex
next prev parent reply other threads:[~2015-01-07 14:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 16:03 [Qemu-devel] [PATCH 0/4] ARM: Add support for a generic PCI Express host bridge Alexander Graf
2015-01-06 16:03 ` [Qemu-devel] [PATCH 1/4] pci: Split pcie_host_mmcfg_map() Alexander Graf
2015-01-12 16:28 ` Claudio Fontana
2015-01-06 16:03 ` [Qemu-devel] [PATCH 2/4] pci: Add generic PCIe host bridge Alexander Graf
2015-01-12 16:29 ` Claudio Fontana
2015-01-12 17:36 ` alvise rigo
2015-01-12 17:38 ` Alexander Graf
2015-01-12 20:08 ` Peter Maydell
2015-01-12 21:06 ` Alexander Graf
2015-01-12 21:20 ` Peter Maydell
2015-01-13 0:13 ` Alexander Graf
2015-01-13 10:07 ` Peter Maydell
2015-01-13 9:09 ` Claudio Fontana
2015-01-06 16:03 ` [Qemu-devel] [PATCH 3/4] arm: Add PCIe host bridge in virt machine Alexander Graf
2015-01-07 15:52 ` Claudio Fontana
2015-01-07 21:47 ` Alexander Graf
2015-01-08 12:55 ` Claudio Fontana
2015-01-08 13:26 ` Alexander Graf
2015-01-08 15:01 ` Claudio Fontana
2015-01-12 16:23 ` Claudio Fontana
2015-01-12 16:35 ` Alexander Graf
2015-01-08 13:36 ` alvise rigo
2015-01-08 10:31 ` Peter Maydell
2015-01-08 12:30 ` Claudio Fontana
2015-01-12 16:20 ` Claudio Fontana
2015-01-12 16:36 ` Alexander Graf
2015-01-12 16:49 ` alvise rigo
2015-01-12 16:57 ` Alexander Graf
2015-01-06 16:03 ` [Qemu-devel] [PATCH 4/4] arm: enable Bochs PCI VGA Alexander Graf
2015-01-06 16:16 ` Peter Maydell
2015-01-06 21:08 ` Alexander Graf
2015-01-06 21:28 ` Peter Maydell
2015-01-06 21:42 ` Alexander Graf
2015-01-07 6:22 ` Paolo Bonzini
2015-01-07 13:52 ` [Qemu-devel] [PATCH 0/4] ARM: Add support for a generic PCI Express host bridge Claudio Fontana
2015-01-07 14:07 ` Alexander Graf
2015-01-07 14:26 ` Claudio Fontana
2015-01-07 14:36 ` Alexander Graf [this message]
2015-01-07 15:16 ` Claudio Fontana
2015-01-07 16:31 ` Peter Maydell
2015-01-12 16:24 ` Claudio Fontana
2015-01-21 12:59 ` Claudio Fontana
2015-01-21 13:01 ` Alexander Graf
2015-01-21 13:02 ` Peter Maydell
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=54AD446C.5000103@suse.de \
--to=agraf@suse.de \
--cc=a.rigo@virtualopensystems.com \
--cc=ard.biesheuvel@linaro.org \
--cc=claudio.fontana@huawei.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rob.herring@linaro.org \
--cc=stuart.yoder@freescale.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).