[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH][LINUX] use machine_emergency_restart() from the generic header.


  • To: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 08 Aug 2006 13:54:16 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 08 Aug 2006 05:54:42 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aca66cFP/7uvxibcEduaRAAKle7CWA==
  • Thread-topic: [Xen-devel] [PATCH][LINUX] use machine_emergency_restart() from the generic header.



On 8/8/06 1:46 pm, "Jimi Xenidis" <jimix@xxxxxxxxxxxxxx> wrote:

> hmm, there are a lot of x86 isms in this file.. I think having all
> these ifdefs in ./drivers will be problematic to the Linux
> integration cause.
> At some point I could see us trying to remove/abstract them anyway.
> 
> Perhaps we could prefix all the methods with "xen_" and have arch
> specific code _in_ arch specific directories call it accordingly?
> 
> I would also like to separate the suspend code from the reboot/halt
> code into different files since thats is cleaner to select that
> support by CONFIG_, thoughts?

All sound like good suggestions. It'll be necessary for upstream merging
anyway, as it'll need to hook under arch-specific paravirt_ops.

I'd take patches to split into separate source files, certainly. And the
xen_ prefixing probably too.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.