From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCH v6 0/5] KVM: VMX: Add Posted Interrupt supporting Date: Mon, 18 Mar 2013 13:28:08 +0200 Message-ID: <20130318112808.GE4020@redhat.com> References: <1363354271-25302-1-git-send-email-yang.z.zhang@intel.com> <20130318091624.GB1276@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]:16789 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750899Ab3CRL2K (ORCPT ); Mon, 18 Mar 2013 07:28:10 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Mar 18, 2013 at 10:43:16AM +0000, Zhang, Yang Z wrote: > >> For TMR issue, since it has nothing to do with APICv, if we really need to handle > > it later, then we may need a separate patch to fix it. But currently, we may > > focused on APICv only. > >> > > What do you mean by "TMR has nothing to do with APICv"? > Just ignore it. I will send out the fixing with APICv patch. > Does this mean we cannot get away with updating TMR like we do now? Because if we can I prefer to not complicate the code further. -- Gleb.