From: Aron Griffis <aron@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Alex Williamson <alex.williamson@hp.com>
Subject: Re: [patch-resend] take a bite out of xen-mkbuildtree-pre
Date: Wed, 31 May 2006 10:43:20 -0400 [thread overview]
Message-ID: <20060531144320.GC12106@mustard.flatmonk> (raw)
In-Reply-To: <2cef186b310801f085d7952598c9c707@cl.cam.ac.uk>
Keir Fraser wrote: [Wed May 31 2006, 02:49:48AM EDT]
> Lots of new config variables -- are they all really needed?
Not really lots... these are the new ones:
XEN_UTIL
...doesn't work if XEN_IA64_DOM0_VP
XEN_BALLOON
XEN_CHAR
XEN_SKBUFF
XEN_REBOOT
XEN_SMPBOOT
...don't work unless XEN_IA64_DOM0_VP
We could use bigger hammers by handling them all with 2 variables, but
IMHO that's just setting them up to be separated in the future when
the situation changes, a new architecture is ported, etc.
Do you think there's a better way?
> Can ia64 not use the Xenified /dev/mem (ia64 and x86 both seem to use
> direct_remap_pfn_range for various things now)?
I'm a little confused how this relates to the patch...
> Referring to xenia64_init.c from a generic Kconfig file is odd.
> Can we pull the event-channel merge before taking this patch and avoid
> the kludge to pull in the ia64-specific evtchn code?
I'd like that. Alex, what do you think?
Aron
next prev parent reply other threads:[~2006-05-31 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 21:56 [patch-resend] take a bite out of xen-mkbuildtree-pre Aron Griffis
2006-05-31 6:49 ` Keir Fraser
2006-05-31 14:43 ` Aron Griffis [this message]
2006-05-31 15:02 ` Keir Fraser
2006-05-31 15:04 ` Alex Williamson
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=20060531144320.GC12106@mustard.flatmonk \
--to=aron@hp.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=alex.williamson@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.