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: Tue, 7 Feb 2017 09:07:48 +0000 [thread overview]
Message-ID: <9811e65a-d0db-4a13-7618-e7a1d13c0cf6@arm.com> (raw)
In-Reply-To: <CAGOz-0Z90aqzkWf+XJ4NZkk4u0fLG2UhYFXdqORVg27Q2G5sPg@mail.gmail.com>
On 07/02/17 09:00, Linu Cherian wrote:
> On Tue, Jan 24, 2017 at 2:34 PM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> On 24/01/17 05:06, Linu Cherian wrote:
>>> On Sat, Jan 14, 2017 at 9:53 PM, Geetha Akula
>>> <geethasowjanya.akula@gmail.com> wrote:
>>>> Hi Marc,
>>>>
>>>> We have been testing vfio patches regularly. We are in contact with Eric
>>>> offline. In fact we are the first one to test V5 patches on Eric request as
>>>> he had some issue with his test setup. After our feedback it was posted in
>>>> upstream.
>>>> We also reported issues found with vfio patches. We been contact with Eric
>>>> regularly.
>>>>
>>>> Thanks,
>>>> Geetha.
>>>>
>>>> On 14-Jan-2017 4:17 PM, "Marc Zyngier" <marc.zyngier@arm.com> wrote:
>>>>>
>>>>> 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.
>>>>>
>>>
>>> May i know if this patch is queued for merge.
>>
>> Not at the moment, since none of the patches it implicitly depends on
>> are merged yet either. Once Eric's patches are in (or at least in
>> -next), this can be queued - assuming it gets some reviewing too.
>>
>
> Marc,
> Hope this patch will be queued for merge, since Eric's patches has been pulled.
Pulled, but not merged yet (as in, not in Linus' tree).
Look, I perfectly understand that you want this in, but there is no need
to send me an email every other week asking me whether I've queued it or
not. Once Eric's stuff is in, and provided that this very patch gets
reviewed (hint: nobody has), it will be queued as a fix post -rc1.
In the mean time, please relax.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-02-07 9:07 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
[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 [this message]
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=9811e65a-d0db-4a13-7618-e7a1d13c0cf6@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).