From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: Re: [PATCH] x86/hvm: implement save/restore for posted
 interrupts
Date: Fri, 19 Sep 2014 15:32:27 +0200
Message-ID: <20140919133227.GA2611@aepfle.de>
References: <A9667DDFB95DB7438FA9D7D576C3D87E0AB31DF7@SHSMSX104.ccr.corp.intel.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D125FF31EB@SHSMSX101.ccr.corp.intel.com>
	<20140728065232.GA6519@aepfle.de>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AB3C3F9@SHSMSX104.ccr.corp.intel.com>
	<20140802105956.GA16174@aepfle.de>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AB4E9C0@SHSMSX104.ccr.corp.intel.com>
	<20140804075007.GA11609@aepfle.de>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AB4EE79@SHSMSX104.ccr.corp.intel.com>
	<20140805103224.GA15563@aepfle.de>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AB9439F@SHSMSX104.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AB9439F@SHSMSX104.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>, "Dong, Eddie" <eddie.dong@intel.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, "Nakajima,
	Jun" <jun.nakajima@intel.com>
List-Id: xen-devel@lists.xenproject.org

On Thu, Sep 18, Zhang, Yang Z wrote:

> Zhang, Yang Z wrote on 2014-09-01:
> > Zhang, Yang Z wrote on 2014-08-08:
> >> Can you tell how you reproduce it? I am following the steps you told
> >> me previously, but I cannot reproduce it with this fixing.
> > Any update on this?
> Ping again.

I will have a look at this issue next week.

Olaf