All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Srivatsa Vaddagiri <vatsa@codeaurora.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 0/1] virtio_mmio: hypervisor specific interfaces for MMIO
Date: Thu, 30 Apr 2020 11:08:22 +0100	[thread overview]
Message-ID: <20200430100821.GC19932@willie-the-truck> (raw)
In-Reply-To: <1588240976-10213-1-git-send-email-vatsa@codeaurora.org>

On Thu, Apr 30, 2020 at 03:32:55PM +0530, Srivatsa Vaddagiri wrote:
> The Type-1 hypervisor we are dealing with does not allow for MMIO transport. 
> [1] summarizes some of the problems we have in making virtio work on such
> hypervisors. This patch proposes a solution for transport problem viz how we can
> do config space IO on such a hypervisor. Hypervisor specific methods
> introduced allows for seamless IO of config space.

Seamless huh? You'd hope that might obviate the need for extra patches...

> This patch is meant to seek comments. If its considered to be in right
> direction, will work on making it more complete and send the next version!

What's stopping you from implementing the trapping support in the
hypervisor? Unlike the other patches you sent out, where the guest memory
is not accessible to the host, there doesn't seem to be any advantage to
not having trapping support, or am I missing something here?

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Srivatsa Vaddagiri <vatsa@codeaurora.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 0/1] virtio_mmio: hypervisor specific interfaces for MMIO
Date: Thu, 30 Apr 2020 11:08:22 +0100	[thread overview]
Message-ID: <20200430100821.GC19932@willie-the-truck> (raw)
In-Reply-To: <1588240976-10213-1-git-send-email-vatsa@codeaurora.org>

On Thu, Apr 30, 2020 at 03:32:55PM +0530, Srivatsa Vaddagiri wrote:
> The Type-1 hypervisor we are dealing with does not allow for MMIO transport. 
> [1] summarizes some of the problems we have in making virtio work on such
> hypervisors. This patch proposes a solution for transport problem viz how we can
> do config space IO on such a hypervisor. Hypervisor specific methods
> introduced allows for seamless IO of config space.

Seamless huh? You'd hope that might obviate the need for extra patches...

> This patch is meant to seek comments. If its considered to be in right
> direction, will work on making it more complete and send the next version!

What's stopping you from implementing the trapping support in the
hypervisor? Unlike the other patches you sent out, where the guest memory
is not accessible to the host, there doesn't seem to be any advantage to
not having trapping support, or am I missing something here?

Will
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  parent reply	other threads:[~2020-04-30 10:08 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
2020-04-30 11:11           ` Srivatsa Vaddagiri
2020-04-30 12:59           ` Jan Kiszka
2020-04-30 12:59             ` [virtio-dev] " Jan Kiszka
2020-04-30 12:59             ` 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                 ` [virtio-dev] " Michael S. Tsirkin
2020-04-30 19:34                 ` 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   ` [virtio-dev] " Michael S. Tsirkin
2020-04-30 10:07   ` 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     ` [virtio-dev] " Jason Wang
2020-04-30 10:56     ` Jason Wang
2020-04-30 10:08 ` Will Deacon [this message]
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=20200430100821.GC19932@willie-the-truck \
    --to=will@kernel.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=vatsa@codeaurora.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.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.