All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geetha Akula <geethasowjanya.akula@gmail.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: sunil.goutham@cavium.com, Linu Cherian <linucherian@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Linu Cherian <linu.cherian@cavium.com>,
	pbonzini@redhat.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM: arm64: Increase number of memslots to 512
Date: Sat, 14 Jan 2017 21:53:07 +0530	[thread overview]
Message-ID: <CANHdaiZf9bHaaNVo1FyMokZ89gfbnMKuQP2KjW21nBqNzqWqYw@mail.gmail.com> (raw)
In-Reply-To: <868tqdvrzu.fsf@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 1474 bytes --]

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.
>
> Thanks,
>
>         M.
> --
> Jazz is not dead. It just smells funny.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

[-- Attachment #1.2: Type: text/html, Size: 2517 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2017-01-14 16:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 16:52 [PATCH] KVM: arm64: Increase number of memslots to 512 linucherian
2017-01-11 16:52 ` linucherian at gmail.com
2017-01-13 12:03 ` Marc Zyngier
2017-01-13 12:03   ` Marc Zyngier
2017-01-13 17:25   ` Linu Cherian
2017-01-13 17:25     ` Linu Cherian
2017-01-13 18:16     ` Marc Zyngier
2017-01-13 18:16       ` Marc Zyngier
2017-01-14  9:53       ` Linu Cherian
2017-01-14  9:53         ` Linu Cherian
2017-01-14 10:46         ` Marc Zyngier
2017-01-14 10:46           ` Marc Zyngier
2017-01-14 16:23           ` Geetha Akula [this message]
2017-01-24  5:06             ` Linu Cherian
2017-01-24  5:06               ` Linu Cherian
2017-01-24  9:04               ` Marc Zyngier
2017-01-24  9:04                 ` Marc Zyngier
2017-02-07  9:00                 ` Linu Cherian
2017-02-07  9:00                   ` Linu Cherian
2017-02-07  9:07                   ` Marc Zyngier
2017-02-07  9:07                     ` Marc Zyngier
2017-01-27 13:38       ` Prakash B
2017-01-27 13:38         ` Prakash B
2017-02-07 10:16 ` Auger Eric
2017-02-07 10:16   ` Auger Eric
2017-02-08  1:57   ` Linu Cherian
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=CANHdaiZf9bHaaNVo1FyMokZ89gfbnMKuQP2KjW21nBqNzqWqYw@mail.gmail.com \
    --to=geethasowjanya.akula@gmail.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linu.cherian@cavium.com \
    --cc=linucherian@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=sunil.goutham@cavium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.