From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCH] KVM: Set TMR when programming ioapic entry Date: Mon, 18 Mar 2013 14:52:32 +0200 Message-ID: <20130318125232.GJ4020@redhat.com> References: <1363606942-5600-1-git-send-email-yang.z.zhang@intel.com> <20130318122819.GG4020@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "kvm@vger.kernel.org" , "mtosatti@redhat.com" , "Zhang, Xiantao" To: "Zhang, Yang Z" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4387 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752412Ab3CRMwe (ORCPT ); Mon, 18 Mar 2013 08:52:34 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Mar 18, 2013 at 12:32:51PM +0000, Zhang, Yang Z wrote: > Gleb Natapov wrote on 2013-03-18: > > On Mon, Mar 18, 2013 at 07:42:22PM +0800, Yang Zhang wrote: > >> From: Yang Zhang > >> > >> We already know the trigger mode of a given interrupt when programming > >> the ioapice entry. So it's not necessary to set it in each interrupt > >> delivery. > >> > > What this patch suppose to go on top of? > Sorry, forget to mention it. > This is based on RTC patch(Use eoi to track RTC interrupt delivery status) and Posted interrupt patch(KVM: VMX: Add Posted Interrupt supporting). > Since it touches the code added by RTC patch series that will be changed after my latest comments it is hard to review that. -- Gleb.