From: Meng Xu <xumeng1901@gmail.com>
To: Pavel Fedin <p.fedin@samsung.com>, qemu-arm@nongnu.org
Subject: Re: [Qemu-arm] aarch64 ivshmem issues
Date: Mon, 11 Jan 2016 10:33:53 -0500 [thread overview]
Message-ID: <5693CB61.4040502@gmail.com> (raw)
In-Reply-To: <052c01d14c47$20860ca0$619225e0$@samsung.com>
Hi Pavel,
Thanks! That's right, ivshmem works just fine on ARM64 once I switch to
the latest kernel and I can see the PCI bridge and devices now.
Thank you for the help,
Meng
On 01/11/2016 03:07 AM, Pavel Fedin wrote:
> Hello!
>
>> I am using the ivshmem device to create shared memory between an x86_64 host and aarch64
>> guest. The guest has ubuntu server 14.04 installed with kernel version 3.13.0. I wrote a kernel
>> driver to drive the ivshmem device (as a pci driver) however, the driver was never registered:
> There should be no problem with ivshmem itself on ARM64. Last year we did some tests with it, and it worked fine out of the box.
> Since you are saying that "the driver was never registered", then, perhaps, something is wrong with your guest kernel config. For the start, check whether PCI subsystem and PCI generic host is enabled. Mainline kernels older than 4.3 do not support generic PCI host controller on ARM64, therefore you have no PCI bus. If your distro has older kernel, it is likely to suffer from this problem. Check 'lspci' output on your guest.
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>
prev parent reply other threads:[~2016-01-11 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 5:35 [Qemu-arm] aarch64 ivshmem issues Meng Xu
2016-01-11 8:07 ` Pavel Fedin
2016-01-11 15:33 ` Meng Xu [this message]
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=5693CB61.4040502@gmail.com \
--to=xumeng1901@gmail.com \
--cc=p.fedin@samsung.com \
--cc=qemu-arm@nongnu.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;
as well as URLs for NNTP newsgroup(s).