From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH v8 2/7] KVM: VMX: Register a new IPI for posted interrupt Date: Wed, 10 Apr 2013 11:31:22 +0200 Message-ID: <20130410093121.GB24443@gmail.com> References: <1365431002-31202-1-git-send-email-yang.z.zhang@intel.com> <1365431002-31202-3-git-send-email-yang.z.zhang@intel.com> <20130409072659.GQ17919@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Yang Zhang , kvm@vger.kernel.org, mtosatti@redhat.com, xiantao.zhang@intel.com, jun.nakajima@intel.com To: Gleb Natapov Return-path: Received: from mail-ea0-f180.google.com ([209.85.215.180]:45185 "EHLO mail-ea0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754582Ab3DJJb0 (ORCPT ); Wed, 10 Apr 2013 05:31:26 -0400 Received: by mail-ea0-f180.google.com with SMTP id d10so118991eaj.39 for ; Wed, 10 Apr 2013 02:31:24 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20130409072659.GQ17919@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: * Gleb Natapov wrote: > On Mon, Apr 08, 2013 at 10:23:17PM +0800, Yang Zhang wrote: > > From: Yang Zhang > > > > Posted Interrupt feature requires a special IPI to deliver posted interrupt > > to guest. And it should has a high priority so the interrupt will not be > > blocked by others. > > Normally, the posted interrupt will be consumed by vcpu if target vcpu is > > running and transparent to OS. But in some cases, the interrupt will arrive > > when target vcpu is scheduled out. And host will see it. So we need to > > register a dump handler to handle it. > > Ingo can I add your ACK to this one? In the past you agreed to the > approach. Yeah, it's fine to me - assuming it's tested and does not break anything. Thanks, Ingo