From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-5463-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 5B46E985D01 for ; Wed, 20 Feb 2019 03:46:46 +0000 (UTC) Date: Tue, 19 Feb 2019 22:46:42 -0500 From: "Michael S. Tsirkin" Message-ID: <20190219223936-mutt-send-email-mst@kernel.org> References: <20190211092943-mutt-send-email-mst@kernel.org> <20190212112547.GC2715@work-vm> <20190212144741.60083682.cohuck@redhat.com> <20190212090121-mutt-send-email-mst@kernel.org> <20190212164626.GG2715@work-vm> <20190219075415.v4xlw5ywrtmndew5@sirius.home.kraxel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [virtio-dev] Memory sharing device To: Frank Yang Cc: Gerd Hoffmann , "Dr. David Alan Gilbert" , Cornelia Huck , Roman Kiryanov , Stefan Hajnoczi , virtio-dev@lists.oasis-open.org, Greg Hartman List-ID: On Tue, Feb 19, 2019 at 07:54:04AM -0800, Frank Yang wrote: > To update driver/device functionality, ideally we want to ship two small shared > libraries, > one to guest userspace and one to plug in to the host VMM. I don't think we want to support that last in QEMU. Generally you want process isolation, not shared library plugins - definitely not host side - VMM is just to sensitive to allow random plugins - and maybe not guest side either. I'm at a conference tomorrow but I hope to complete review of the proposal and respond by end of week. Thanks! -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org