WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH][RFC] Support S3 for MSI interrupt in latest kern

To: Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH][RFC] Support S3 for MSI interrupt in latest kernel dom0
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 17 Dec 2008 15:53:40 +0000
Cc: Yunhong Jiang <yunhong.jiang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 17 Dec 2008 07:53:52 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4949294A.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclgX6E8DykH3fjE1UCGshHsMGt1qA==
Thread-topic: [PATCH][RFC] Support S3 for MSI interrupt in latest kernel dom0
User-agent: Microsoft-Entourage/12.14.0.081024
On 17/12/2008 15:31, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 17.12.08 16:22 >>>
>> Well, maybe it's okay then. I don't think Yunhong's patch was a good
>> argument for it -- looking again it appears to have plenty of not really
>> related chunks contained in it.
> 
> I don't think it's really okay as-is: As he indicated, there may be side
> effects of the changes during other than resume from S3 (in particular
> the IRQ_GUEST check around the newly added call to ->startup()), and
> I was hoping you might have a suggestion on how to better distinguish
> that particular case. In the worst case, Xen has to set another flag in
> each MSI irq_desc when it resumes from S3, and do the startup as well
> as the clearing of the flag when map_domain_pirq runs first for that
> particular vector.

Then do it as a new hypercall? How much complexity does that add on the
guest side?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel