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] serial console driver using release_irq()/setup_irq() on sus

To: "Keir Fraser" <keir@xxxxxxx>
Subject: [Xen-devel] serial console driver using release_irq()/setup_irq() on suspend/resume
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Thu, 17 Mar 2011 16:45:55 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 17 Mar 2011 09:45:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Keir,

is there any particular reason this is being done this way, other than
having made the change in 15259:35e38c9048c8 very simple? I'm
asking because in general, with no modules, Xen ought to not need
setup_irq() post-init (for release_irq() the serial driver is actually the
only consumer), and after fiddling with request_irq() callers this is
now the only one needing the function to be in .text.

Jan


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

<Prev in Thread] Current Thread [Next in Thread>