From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v4 6/9] KVM: Save/restore state of assigned PCI device Date: Tue, 09 Nov 2010 15:46:40 +0200 Message-ID: <4CD950C0.4020201@redhat.com> References: <1323c55899273c3bfc746fda9b47948aca6eae2f.1289215310.git.jan.kiszka@siemens.com> <4CD94021.4090705@redhat.com> <4CD94CBB.8030105@siemens.com> <4CD94E5C.9050909@redhat.com> <4CD95044.4040402@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm , Alex Williamson , "Michael S. Tsirkin" To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:56791 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753290Ab0KINqq (ORCPT ); Tue, 9 Nov 2010 08:46:46 -0500 In-Reply-To: <4CD95044.4040402@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 11/09/2010 03:44 PM, Jan Kiszka wrote: > > > > Oh yes, I read the code but it didn't register. Of course this change > > is quite necessary. > > > > (I understood you to mean that the PCI 2.3 reset doesn't reset > > everything, but that isn't what you said). > > What the hardware makes out of the reset is even another story. No > guarantees I bet (isn't function-level reset an optional thing anyway?). It is. -- error compiling committee.c: too many arguments to function