From: Hollis Blanchard <hollisb@us.ibm.com>
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Xen/ia64 presentation
Date: Wed, 27 Apr 2005 17:34:17 -0500 [thread overview]
Message-ID: <42701369.4060800@us.ibm.com> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD535B01B@cacexc12.americas.cpqcorp.net>
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
next prev parent reply other threads:[~2005-04-27 22:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 21:47 Re: Xen/ia64 presentation Magenheimer, Dan (HP Labs Fort Collins)
2005-04-27 22:34 ` Hollis Blanchard [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-28 19:05 Magenheimer, Dan (HP Labs Fort Collins)
2005-04-28 14:53 Dong, Eddie
2005-04-27 17:25 Magenheimer, Dan (HP Labs Fort Collins)
2005-04-27 19:12 ` Hollis Blanchard
2005-04-27 19:24 ` Keir Fraser
2005-04-27 19:31 ` Hollis Blanchard
2005-04-27 19:34 ` Keir Fraser
2005-04-27 20:08 ` Hollis Blanchard
2005-04-28 8:32 ` Keir Fraser
2005-04-28 8:54 ` Keir Fraser
2005-04-28 18:10 ` Hollis Blanchard
2005-04-28 18:38 ` Keir Fraser
2005-04-28 18:58 ` Hollis Blanchard
2005-04-28 19:47 ` Keir Fraser
2005-04-28 20:11 ` Hollis Blanchard
2005-04-27 19:31 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42701369.4060800@us.ibm.com \
--to=hollisb@us.ibm.com \
--cc=dan.magenheimer@hp.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.