|
xen-devel
[Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config options and d
|
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config options and disable unsupported config options. |
|
From: |
Dan Hecht <dhecht@xxxxxxxxxx> |
|
Date: |
Tue, 13 Feb 2007 15:58:50 -0800 |
|
Cc: |
Andrew Morton <akpm@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Pratt <ian.pratt@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>, Andi Kleen <ak@xxxxxx>, virtualization@xxxxxxxxxxxxxx |
|
Delivery-date: |
Wed, 14 Feb 2007 02:24:16 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<45D249D9.80407@xxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<20070213221729.772002682@xxxxxxxx> <20070213221830.542511707@xxxxxxxx> <45D24172.9020800@xxxxxxxxxx> <45D249D9.80407@xxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Thunderbird 1.5.0.2 (X11/20060420) |
On 02/13/2007 03:29 PM, Jeremy Fitzhardinge wrote:
Dan Hecht wrote:
I assume you plan to eventually get all this stuff working but just
want to prevent configurations that the Xen paravirt-ops isn't ready
for at the moment?
Instead can you do it this way:
config XEN
depends on PARAVIRT && !PREEMPT && HZ_100 && !DOUBLEFAULT && !KEXEC
That's a bit simpler code-wise, but it does make it pretty complex to
get everything just-so to even see the CONFIG_XEN option.
Not only is it simpler code-wise, but it is more to the point... it is
CONFIG_XEN that needs to be fixed to handle PREEMPT, KEXEC, different HZ
values, etc. Not the other way around.
Enabling the compile of any paravirt-ops backend shouldn't cripple the
kernel in any way... instead, the burden should be on the xen
paravirt-ops backend to be completed. CONFIG_PREEMPT shouldn't care
about which paravirt-ops are compiled in. Instead, CONFIG_XEN is the
one that needs !PREEMPT.
Dan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home