From: "Wang, Wei W" <wei.w.wang@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Yamahata, Isaku" <isaku.yamahata@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"srutherford@google.com" <srutherford@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"erdemaktas@google.com" <erdemaktas@google.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: RE: [RFC] hypercall-vsock: add a new vsock transport
Date: Thu, 25 Nov 2021 08:43:55 +0000 [thread overview]
Message-ID: <58911901bd7b4bc3a99642214106bc2f@intel.com> (raw)
In-Reply-To: <CACGkMEsY_XkRo_P+R=ipQ1iYm-AimvLvfXUwEy40Nn4f1D_suA@mail.gmail.com>
On Thursday, November 25, 2021 2:38 PM, Jason Wang wrote:
> > We thought about virtio-mmio. There are some barriers:
> > 1) It wasn't originally intended for x86 machines. The only machine
> > type in QEMU that supports it (to run on x86) is microvm. But
> > "microvm" doesn’t support TDX currently, and adding this support might
> need larger effort.
>
> Can you explain why microvm needs larger effort? It looks to me it fits for TDX
> perfectly since it has less attack surface.
The main thing is TDVF doesn’t support microvm so far (the based OVMF
support for microvm is still under their community discussion).
Do you guys think it is possible to add virtio-mmio support for q35?
(e.g. create a special platform bus in some fashion for memory mapped devices)
Not sure if the effort would be larger.
Thanks,
Wei
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Wang, Wei W" <wei.w.wang@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"kys@microsoft.com" <kys@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"Yamahata, Isaku" <isaku.yamahata@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"srutherford@google.com" <srutherford@google.com>,
"erdemaktas@google.com" <erdemaktas@google.com>
Subject: RE: [RFC] hypercall-vsock: add a new vsock transport
Date: Thu, 25 Nov 2021 08:43:55 +0000 [thread overview]
Message-ID: <58911901bd7b4bc3a99642214106bc2f@intel.com> (raw)
In-Reply-To: <CACGkMEsY_XkRo_P+R=ipQ1iYm-AimvLvfXUwEy40Nn4f1D_suA@mail.gmail.com>
On Thursday, November 25, 2021 2:38 PM, Jason Wang wrote:
> > We thought about virtio-mmio. There are some barriers:
> > 1) It wasn't originally intended for x86 machines. The only machine
> > type in QEMU that supports it (to run on x86) is microvm. But
> > "microvm" doesn’t support TDX currently, and adding this support might
> need larger effort.
>
> Can you explain why microvm needs larger effort? It looks to me it fits for TDX
> perfectly since it has less attack surface.
The main thing is TDVF doesn’t support microvm so far (the based OVMF
support for microvm is still under their community discussion).
Do you guys think it is possible to add virtio-mmio support for q35?
(e.g. create a special platform bus in some fashion for memory mapped devices)
Not sure if the effort would be larger.
Thanks,
Wei
next prev parent reply other threads:[~2021-11-25 8:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 7:12 [RFC] hypercall-vsock: add a new vsock transport Wang, Wei W
2021-11-10 9:34 ` Stefan Hajnoczi
2021-11-10 9:34 ` Stefan Hajnoczi
2021-11-11 8:02 ` Wang, Wei W
2021-11-11 8:02 ` Wang, Wei W
2021-11-10 10:50 ` Michael S. Tsirkin
2021-11-10 10:50 ` Michael S. Tsirkin
2021-11-11 7:58 ` Wang, Wei W
2021-11-11 7:58 ` Wang, Wei W
2021-11-11 15:19 ` Michael S. Tsirkin
2021-11-11 15:19 ` Michael S. Tsirkin
2021-11-25 6:37 ` Jason Wang
2021-11-25 6:37 ` Jason Wang
2021-11-25 8:43 ` Wang, Wei W [this message]
2021-11-25 8:43 ` Wang, Wei W
2021-11-25 12:04 ` Gerd Hoffmann
2021-11-25 12:04 ` Gerd Hoffmann
2021-11-10 11:17 ` Stefano Garzarella
2021-11-10 11:17 ` Stefano Garzarella
2021-11-10 21:45 ` Paraschiv, Andra-Irina
2021-11-11 8:14 ` Wang, Wei W
2021-11-11 8:14 ` Wang, Wei W
2021-11-11 8:24 ` Paolo Bonzini
2021-11-11 8:24 ` Paolo Bonzini
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=58911901bd7b4bc3a99642214106bc2f@intel.com \
--to=wei.w.wang@intel.com \
--cc=andi.kleen@intel.com \
--cc=davem@davemloft.net \
--cc=erdemaktas@google.com \
--cc=isaku.yamahata@intel.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=srutherford@google.com \
--cc=stefanha@redhat.com \
--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.