From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [PATCH 19/19] KVM: introduce a KVM_DELETE_DEVICE ioctl Date: Thu, 24 Jan 2019 08:32:57 +1100 Message-ID: <56614ab4b8ecaa4c02fb78864e6a0c2baf252567.camel@kernel.crashing.org> References: <20190107184331.8429-1-clg@kaod.org> <20190107191006.10648-1-clg@kaod.org> <20190107191006.10648-3-clg@kaod.org> <20190122054253.GH15124@blackberry> <57f8817f-ecef-8bae-189a-8975870411df@kaod.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, David Gibson To: =?ISO-8859-1?Q?C=E9dric?= Le Goater , Paul Mackerras Return-path: In-Reply-To: <57f8817f-ecef-8bae-189a-8975870411df@kaod.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Sender: "Linuxppc-dev" List-Id: kvm.vger.kernel.org On Wed, 2019-01-23 at 19:39 +0100, Cédric Le Goater wrote: > > The reason I ask is that we will have to be much more careful about > > memory allocation lifetimes with this patch. > > yes. bad refcounting will lead the host kernel to a crash. One way to alleviate that is to make sure this is only supported on selected devices such as XICS via some flag or the presence of a callback. Cheers, Ben.