From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH/RFC 0/4] Rework alarm timer infrastrucure. Date: Fri, 17 Aug 2007 15:44:06 +0300 Message-ID: <46C59816.3050008@qumranet.com> References: <11872968773449-git-send-email-kronos.it@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Dan Kenigsberg , qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org To: Luca Tettamanti Return-path: In-Reply-To: <11872968773449-git-send-email-kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Luca Tettamanti wrote: > Hello, > in reply to this mail I will send a serie of 4 patches that cleans up and expands > the alarm timer handling in QEMU. Patches apply to current kvm-userspace tree, > but I think I can rebase it to QEMU svn if desired. > > I would really like to see this go into qemu first (assuming the qemu maintainers want it). So far kvm changes are minor additions, but this is a fairly intrusive change. In addition, it benefits qemu as much as kvm. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/