All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: stefanha@redhat.com, jasowang@redhat.com,
	torvalds@linux-foundation.org, ascull@google.com, maz@kernel.org,
	keirf@google.com, jiyong@google.com, kernel-team@android.com,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	crosvm-dev@chromium.org
Subject: Re: IOTLB support for vhost/vsock breaks crosvm on Android
Date: Wed, 17 Aug 2022 13:05:49 -0400	[thread overview]
Message-ID: <20220817130510-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220817134821.GA12615@willie-the-truck>

On Wed, Aug 17, 2022 at 02:48:22PM +0100, Will Deacon wrote:
> On Mon, Aug 08, 2022 at 08:45:48AM -0400, Michael S. Tsirkin wrote:
> > > > Also yes, I think it's a good idea to change crosvm anyway.  While the
> > > > work around I describe might make sense upstream I don't think it's a
> > > > reasonable thing to do in stable kernels.
> > > > I think I'll prepare a patch documenting the legal vhost features
> > > > as a 1st step even though crosvm is rust so it's not importing
> > > > the header directly, right?
> > > 
> > > Documentation is a good idea regardless, so thanks for that. Even though
> > > crosvm has its own bindings for the vhost ioctl()s, the documentation
> > > can be reference or duplicated once it's available in the kernel headers.
> > > 
> > So for crosvm change, I will post the documentation change and
> > you guys can discuss?
> 
> FYI, the crosvm patch is merged here:
> 
> https://github.com/google/crosvm/commit/4e7d00be2e135b0a2d964320ea4276e5d896f426
> 
> Will

Great thanks a lot!
I'm on vacation next week but will work on it afterwards.

-- 
MST


WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: jiyong@google.com, kvm@vger.kernel.org, kernel-team@android.com,
	maz@kernel.org, keirf@google.com, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, ascull@google.com,
	stefanha@redhat.com, crosvm-dev@chromium.org,
	torvalds@linux-foundation.org
Subject: Re: IOTLB support for vhost/vsock breaks crosvm on Android
Date: Wed, 17 Aug 2022 13:05:49 -0400	[thread overview]
Message-ID: <20220817130510-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220817134821.GA12615@willie-the-truck>

On Wed, Aug 17, 2022 at 02:48:22PM +0100, Will Deacon wrote:
> On Mon, Aug 08, 2022 at 08:45:48AM -0400, Michael S. Tsirkin wrote:
> > > > Also yes, I think it's a good idea to change crosvm anyway.  While the
> > > > work around I describe might make sense upstream I don't think it's a
> > > > reasonable thing to do in stable kernels.
> > > > I think I'll prepare a patch documenting the legal vhost features
> > > > as a 1st step even though crosvm is rust so it's not importing
> > > > the header directly, right?
> > > 
> > > Documentation is a good idea regardless, so thanks for that. Even though
> > > crosvm has its own bindings for the vhost ioctl()s, the documentation
> > > can be reference or duplicated once it's available in the kernel headers.
> > > 
> > So for crosvm change, I will post the documentation change and
> > you guys can discuss?
> 
> FYI, the crosvm patch is merged here:
> 
> https://github.com/google/crosvm/commit/4e7d00be2e135b0a2d964320ea4276e5d896f426
> 
> Will

Great thanks a lot!
I'm on vacation next week but will work on it afterwards.

-- 
MST

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

  reply	other threads:[~2022-08-17 17:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 18:11 IOTLB support for vhost/vsock breaks crosvm on Android Will Deacon
2022-08-05 18:11 ` Will Deacon
2022-08-05 22:57 ` Linus Torvalds
2022-08-05 22:57   ` Linus Torvalds
2022-08-06  8:17   ` Stefano Garzarella
2022-08-06  8:17     ` Stefano Garzarella
2022-08-06  9:42   ` Will Deacon
2022-08-06  9:42     ` Will Deacon
2022-08-07  6:52   ` Christoph Hellwig
2022-08-07  6:52     ` Christoph Hellwig
2022-08-07 13:35     ` Michael S. Tsirkin
2022-08-07 13:35       ` Michael S. Tsirkin
2022-08-07 13:27   ` Michael S. Tsirkin
2022-08-07 13:27     ` Michael S. Tsirkin
2022-08-06  7:48 ` Stefano Garzarella
2022-08-06  7:48   ` Stefano Garzarella
2022-08-06  9:42   ` Will Deacon
2022-08-06  9:42     ` Will Deacon
2022-08-06 10:52     ` Stefan Hajnoczi
2022-08-06 10:52       ` Stefan Hajnoczi
2022-08-06 14:34       ` Will Deacon
2022-08-06 14:34         ` Will Deacon
2022-08-06 21:47         ` Stefan Hajnoczi
2022-08-06 10:52     ` Stefano Garzarella
2022-08-06 10:52       ` Stefano Garzarella
2022-08-07 13:14 ` Michael S. Tsirkin
2022-08-07 13:14   ` Michael S. Tsirkin
2022-08-08 10:18   ` Will Deacon
2022-08-08 10:18     ` Will Deacon
2022-08-08 12:45     ` Michael S. Tsirkin
2022-08-08 12:45       ` Michael S. Tsirkin
2022-08-08 14:33       ` Stefan Hajnoczi
2022-08-09  3:16       ` Jason Wang
2022-08-09  3:16         ` Jason Wang
2022-08-17 13:48       ` Will Deacon
2022-08-17 13:48         ` Will Deacon
2022-08-17 17:05         ` Michael S. Tsirkin [this message]
2022-08-17 17:05           ` Michael S. Tsirkin
2022-08-09  3:12   ` Jason Wang
2022-08-09  3:12     ` Jason Wang

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=20220817130510-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=ascull@google.com \
    --cc=crosvm-dev@chromium.org \
    --cc=jasowang@redhat.com \
    --cc=jiyong@google.com \
    --cc=keirf@google.com \
    --cc=kernel-team@android.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=stefanha@redhat.com \
    --cc=torvalds@linux-foundation.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.