[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: [PATCH] Export xen_start_info & notify_remote_via_irq symbols
Hi, This patch has been rejected? And is there any reason why we don't export xenbus_register_backend() ? Thanks. NAH On 10/2/05, NAHieu <nahieu@xxxxxxxxx> wrote: > The below patch exports xen_start_info & notify_remote_via_irq, makes > them available for external kernel modules. > > Signed-off-by: Nguyen Anh Hieu <nahieu@xxxxxxxxx> > > > > diff -r 9d047fb99e38 linux-2.6-xen-sparse/arch/xen/i386/kernel/setup.c > --- a/linux-2.6-xen-sparse/arch/xen/i386/kernel/setup.c Fri Sep 30 16:37:52 > 2005 > +++ b/linux-2.6-xen-sparse/arch/xen/i386/kernel/setup.c Sat Oct 1 23:38:52 > 2005 > @@ -365,6 +365,7 @@ > > /* Raw start-of-day parameters from the hypervisor. */ > start_info_t *xen_start_info; > +EXPORT_SYMBOL(xen_start_info); > > static void __init limit_regions(unsigned long long size) > { > diff -r 9d047fb99e38 linux-2.6-xen-sparse/arch/xen/kernel/evtchn.c > --- a/linux-2.6-xen-sparse/arch/xen/kernel/evtchn.c Fri Sep 30 16:37:52 > 2005 > +++ b/linux-2.6-xen-sparse/arch/xen/kernel/evtchn.c Sat Oct 1 23:38:52 > 2005 > @@ -629,6 +629,7 @@ > if (VALID_EVTCHN(evtchn)) > notify_remote_via_evtchn(evtchn); > } > +EXPORT_SYMBOL(notify_remote_via_irq); > > void irq_resume(void) > { > diff -r 9d047fb99e38 linux-2.6-xen-sparse/arch/xen/x86_64/kernel/setup.c > --- a/linux-2.6-xen-sparse/arch/xen/x86_64/kernel/setup.c Fri > Sep 30 16:37:52 2005 > +++ b/linux-2.6-xen-sparse/arch/xen/x86_64/kernel/setup.c Sat > Oct 1 23:38:52 2005 > @@ -86,6 +86,7 @@ > > /* Raw start-of-day parameters from the hypervisor. */ > start_info_t *xen_start_info; > +EXPORT_SYMBOL(xen_start_info); > #endif > > /* > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |