From: marc.zyngier@arm•com (Marc Zyngier)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] KVM: arm64: Increase number of memslots to 512
Date: Sat, 14 Jan 2017 10:46:29 +0000 [thread overview]
Message-ID: <868tqdvrzu.fsf@arm.com> (raw)
In-Reply-To: <CAGOz-0bR-YnUiv5v_duJYOQE3jxCoGRO=f05==tD5kL489g2CQ@mail.gmail.com> (Linu Cherian's message of "Sat, 14 Jan 2017 15:23:52 +0530")
On Sat, Jan 14 2017 at 09:53:52 AM, Linu Cherian <linucherian@gmail•com> wrote:
>> Let me be more precise. At the moment, KVM on arm64 doesn't support the
>> delivery of MSIs generated by physical devices into a guest (patches are
>> in progress, but not merged yet). So unless you used devices that have
>> no need for interrupts, I don't see how this works.
>>
>> Can you shed some light on your test process?
>>
>
> We did the testing on top of latest VFIO msi support patches submitted
> by Eric Auger.
Did you? That's reassuring. It would have been good if any of the Cavium
folks did chime in on the list and help reviewing though - so far, all
I've heard is a deafening silence. I guess there was no hurry for Cavium
to see these patches being merged.
Thanks,
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2017-01-14 10:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 16:52 [PATCH] KVM: arm64: Increase number of memslots to 512 linucherian at gmail.com
2017-01-13 12:03 ` Marc Zyngier
2017-01-13 17:25 ` Linu Cherian
2017-01-13 18:16 ` Marc Zyngier
2017-01-14 9:53 ` Linu Cherian
2017-01-14 10:46 ` Marc Zyngier [this message]
[not found] ` <CANHdaiZf9bHaaNVo1FyMokZ89gfbnMKuQP2KjW21nBqNzqWqYw@mail.gmail.com>
2017-01-24 5:06 ` Linu Cherian
2017-01-24 9:04 ` Marc Zyngier
2017-02-07 9:00 ` Linu Cherian
2017-02-07 9:07 ` Marc Zyngier
2017-01-27 13:38 ` Prakash B
2017-02-07 10:16 ` Auger Eric
2017-02-08 1:57 ` Linu Cherian
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=868tqdvrzu.fsf@arm.com \
--to=marc.zyngier@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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