From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH][QEMU] Use a separate device for in-kernel PIT Date: Sun, 16 Mar 2008 13:24:00 +0200 Message-ID: <47DD0350.3040705@qumranet.com> References: <1205343520-11789-1-git-send-email-aliguori@us.ibm.com> <1205359450.3163.21.camel@localhost.localdomain> <47D8559C.6060203@us.ibm.com> <200803131020.18323.sheng.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net To: "Yang, Sheng" Return-path: In-Reply-To: <200803131020.18323.sheng.yang@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Yang, Sheng wrote: > And we got two choices in userspace: one ioctl to reset all kvm devices, or > one ioctl for each device. For we are separating in kernel device into > separate devices, seems the later is more proper. But would it bring other > troubles like inconsistent state for smp? > > I agree that a separate ioctl would introduce smp problems, so I think one ioctl that resets all devices and all vcpus is the way to go. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/