From: David Hildenbrand <david@redhat.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
linuxarm@huawei.com, qemu-devel@nongnu.org,
Auger Eric <eric.auger@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v2] hw/arm/virt enable support for virtio-mem
Date: Wed, 25 Nov 2020 17:32:44 +0100 [thread overview]
Message-ID: <2b69a10f-4c8b-d903-2980-5ac02b0b329b@redhat.com> (raw)
In-Reply-To: <20201125161148.00005f6e@Huawei.com>
On 25.11.20 17:11, Jonathan Cameron wrote:
> On Wed, 25 Nov 2020 16:54:53 +0100
> David Hildenbrand <david@redhat.com> wrote:
>
>>>>>>
>>>>>> 64k guest on 4k host with 512MiB block size seems fine.
>>>>>>
>>>>>> If there are any places anyone thinks need particular poking I'd appreciate a hint :)
>>>>>
>>>>> If things seem to work for now, that's great :) Thanks!
>>>>>
>>>> Cool. I'll run a few more comprehensive tests then send out the
>>>> trivial patch to enable the kernel option + v2 of the qemu support.
>>>
>>> Perfect, thanks!
>>
>> Oh, btw, I have no idea what the state of vfio-pci + QEMU on arm64 is.
>> In case it's supposed to work, you could give
>>
>> https://lkml.kernel.org/r/20201119153918.120976-1-david@redhat.com
>>
>> to see what we're missing.
>
> vfio-pci works in general (and we use it a lot), so sure I'll give
> this a test run.
Cool.
In case you get it to run, please test with both "online_kernel" and
"online_movable" in the guest, and small boot memory (e.g., 2 GiB).
For example, on x86-64 I got my vfio-pci provided GPUs to consume
virtio-mem memory easily when starting with 2-4 GiB boot memory and
using "online_kernel". (I verified that when not creating the mappings,
IO errors can be observed and graphics are messed up).
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-11-25 16:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 17:43 [PATCH v2] hw/arm/virt enable support for virtio-mem Jonathan Cameron
2020-11-05 17:51 ` Philippe Mathieu-Daudé
2020-11-09 13:40 ` Auger Eric
2020-11-09 19:47 ` David Hildenbrand
2020-11-24 18:11 ` Jonathan Cameron
2020-11-24 19:17 ` David Hildenbrand
2020-11-25 8:38 ` Andrew Jones
2020-11-25 8:45 ` David Hildenbrand
2020-11-25 10:47 ` Andrew Jones
2020-11-25 10:57 ` David Hildenbrand
2020-11-25 14:56 ` Jonathan Cameron
2020-11-25 15:04 ` David Hildenbrand
2020-11-25 15:54 ` David Hildenbrand
2020-11-25 16:11 ` Jonathan Cameron
2020-11-25 16:32 ` David Hildenbrand [this message]
2020-12-02 10:02 ` Michael S. Tsirkin
2020-12-02 10:45 ` Jonathan Cameron
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=2b69a10f-4c8b-d903-2980-5ac02b0b329b@redhat.com \
--to=david@redhat.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=eric.auger@redhat.com \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).