From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: Re: Xen/ia64 presentation Date: Wed, 27 Apr 2005 17:34:17 -0500 Message-ID: <42701369.4060800@us.ibm.com> References: <516F50407E01324991DD6D07B0531AD535B01B@cacexc12.americas.cpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <516F50407E01324991DD6D07B0531AD535B01B@cacexc12.americas.cpqcorp.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Magenheimer, Dan (HP Labs Fort Collins)" Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org Magenheimer, Dan (HP Labs Fort Collins) wrote: > As you may have noticed, Xen/ia64 completely ignores > all of the execution context structs because (as > described in the base for this thread), ia64 can't > represent its state that way. To remove common users of xen_regs/execution_context_t (i.e. drivers/char/*.c) I think we should be able to just pass 'current' to show_registers(). To remove full_execution_context_t, we'll need to change the arch_getdomaininfo_ctxt() interface a little bit (to do the copy itself), then add a arch hook for do_boot_vcpu() and set_info_guest(). Right? Sounds like that would help clean up ia64 code a bit, so let's do it. :) Even after that's done though, I see value in having core structures like these named identically across architectures. I understand now that some of those won't matter to you... but at least exec_domain/arch_exec_domain still should, and we're also talking about those names. -- Hollis Blanchard IBM Linux Technology Center