All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@codeaurora.org>
To: Will Deacon <will@kernel.org>
Cc: tsoni@codeaurora.org, virtio-dev@lists.oasis-open.org,
	mst@redhat.com, jan.kiszka@siemens.com, jasowang@redhat.com,
	konrad.wilk@oracle.com, christoffer.dall@arm.com,
	virtualization@lists.linux-foundation.org,
	alex.bennee@linaro.org, iommu@lists.linux-foundation.org,
	stefano.stabellini@xilinx.com, pratikp@codeaurora.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/1] virtio: Introduce MMIO ops
Date: Thu, 30 Apr 2020 16:41:56 +0530	[thread overview]
Message-ID: <20200430111156.GI5097@quicinc.com> (raw)
In-Reply-To: <20200430104149.GG19932@willie-the-truck>

* Will Deacon <will@kernel.org> [2020-04-30 11:41:50]:

> On Thu, Apr 30, 2020 at 04:04:46PM +0530, Srivatsa Vaddagiri wrote:
> > If CONFIG_VIRTIO_MMIO_OPS is defined, then I expect this to be unconditionally
> > set to 'magic_qcom_ops' that uses hypervisor-supported interface for IO (for
> > example: message_queue_send() and message_queue_recevie() hypercalls).
> 
> Hmm, but then how would such a kernel work as a guest under all the
> spec-compliant hypervisors out there?

Ok I see your point and yes for better binary compatibility, the ops have to be
set based on runtime detection of hypervisor capabilities.

> > Ok. I guess the other option is to standardize on a new virtio transport (like
> > ivshmem2-virtio)?
> 
> I haven't looked at that, but I suppose it depends on what your hypervisor
> folks are willing to accomodate.

I believe ivshmem2_virtio requires hypervisor to support PCI device emulation
(for life-cycle management of VMs), which our hypervisor may not support. A
simple shared memory and doorbell or message-queue based transport will work for
us.

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Srivatsa Vaddagiri <vatsa@codeaurora.org>
To: Will Deacon <will@kernel.org>
Cc: konrad.wilk@oracle.com, mst@redhat.com, jasowang@redhat.com,
	jan.kiszka@siemens.com, stefano.stabellini@xilinx.com,
	iommu@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	virtio-dev@lists.oasis-open.org, tsoni@codeaurora.org,
	pratikp@codeaurora.org, christoffer.dall@arm.com,
	alex.bennee@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/1] virtio: Introduce MMIO ops
Date: Thu, 30 Apr 2020 16:41:56 +0530	[thread overview]
Message-ID: <20200430111156.GI5097@quicinc.com> (raw)
In-Reply-To: <20200430104149.GG19932@willie-the-truck>

* Will Deacon <will@kernel.org> [2020-04-30 11:41:50]:

> On Thu, Apr 30, 2020 at 04:04:46PM +0530, Srivatsa Vaddagiri wrote:
> > If CONFIG_VIRTIO_MMIO_OPS is defined, then I expect this to be unconditionally
> > set to 'magic_qcom_ops' that uses hypervisor-supported interface for IO (for
> > example: message_queue_send() and message_queue_recevie() hypercalls).
> 
> Hmm, but then how would such a kernel work as a guest under all the
> spec-compliant hypervisors out there?

Ok I see your point and yes for better binary compatibility, the ops have to be
set based on runtime detection of hypervisor capabilities.

> > Ok. I guess the other option is to standardize on a new virtio transport (like
> > ivshmem2-virtio)?
> 
> I haven't looked at that, but I suppose it depends on what your hypervisor
> folks are willing to accomodate.

I believe ivshmem2_virtio requires hypervisor to support PCI device emulation
(for life-cycle management of VMs), which our hypervisor may not support. A
simple shared memory and doorbell or message-queue based transport will work for
us.

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation

  reply	other threads:[~2020-04-30 11:12 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 10:02 [RFC/PATCH 0/1] virtio_mmio: hypervisor specific interfaces for MMIO Srivatsa Vaddagiri
2020-04-30 10:02 ` Srivatsa Vaddagiri
2020-04-30 10:02 ` [RFC/PATCH 1/1] virtio: Introduce MMIO ops Srivatsa Vaddagiri
2020-04-30 10:02   ` Srivatsa Vaddagiri
2020-04-30 10:14   ` Will Deacon
2020-04-30 10:14     ` Will Deacon
2020-04-30 10:34     ` Srivatsa Vaddagiri
2020-04-30 10:34       ` Srivatsa Vaddagiri
2020-04-30 10:41       ` Will Deacon
2020-04-30 10:41         ` Will Deacon
2020-04-30 11:11         ` Srivatsa Vaddagiri [this message]
2020-04-30 11:11           ` Srivatsa Vaddagiri
2020-04-30 12:59           ` Jan Kiszka
2020-04-30 12:59             ` Jan Kiszka
2020-04-30 12:59             ` [virtio-dev] " Jan Kiszka
2020-04-30 13:33             ` Srivatsa Vaddagiri
2020-04-30 13:33               ` Srivatsa Vaddagiri
2020-04-30 13:33               ` Srivatsa Vaddagiri
2020-04-30 19:34               ` Michael S. Tsirkin
2020-04-30 19:34                 ` Michael S. Tsirkin
2020-04-30 19:34                 ` [virtio-dev] " Michael S. Tsirkin
2020-04-30 10:07 ` [RFC/PATCH 0/1] virtio_mmio: hypervisor specific interfaces for MMIO Michael S. Tsirkin
2020-04-30 10:07   ` Michael S. Tsirkin
2020-04-30 10:07   ` [virtio-dev] " Michael S. Tsirkin
2020-04-30 10:40   ` Srivatsa Vaddagiri
2020-04-30 10:40     ` Srivatsa Vaddagiri
2020-04-30 10:56   ` Jason Wang
2020-04-30 10:56     ` Jason Wang
2020-04-30 10:56     ` [virtio-dev] " Jason Wang
2020-04-30 10:08 ` Will Deacon
2020-04-30 10:08   ` Will Deacon
2020-04-30 10:29   ` Srivatsa Vaddagiri
2020-04-30 10:29     ` Srivatsa Vaddagiri
2020-04-30 10:39     ` Will Deacon
2020-04-30 10:39       ` Will Deacon
2020-04-30 11:02       ` Srivatsa Vaddagiri
2020-04-30 11:02         ` Srivatsa Vaddagiri
2020-04-30 11:02         ` Srivatsa Vaddagiri

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=20200430111156.GI5097@quicinc.com \
    --to=vatsa@codeaurora.org \
    --cc=alex.bennee@linaro.org \
    --cc=christoffer.dall@arm.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jan.kiszka@siemens.com \
    --cc=jasowang@redhat.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pratikp@codeaurora.org \
    --cc=stefano.stabellini@xilinx.com \
    --cc=tsoni@codeaurora.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=will@kernel.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 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.