From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: RE: [PATCH] Dom0 Kernel - Fixes forsaving/restoringMSI/MSI-X across Dom0 S3 Date: Mon, 24 Nov 2008 13:35:22 +0000 Message-ID: <492ABBAA.76E4.0078.0@novell.com> References: <492AA0F0.76E4.0078.0@novell.com> <0A882F4D99BBF6449D58E61AAFD7EDD601E23B69@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD601E23B69@pdsmsx502.ccr.corp.intel.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kevin Tian Cc: "'xen-devel@lists.xensource.com'" , Haitao Shan , 'Keir Fraser' List-Id: xen-devel@lists.xenproject.org >>> "Tian, Kevin" 24.11.08 13:53 >>> >It's possible that given device has been placed in D3cold state, >and then no change left for Xen to save. But isn't it the driver's resume handler that would have to restore (i.e. re-initialize) MSI in that case? Jan