Message-ID: <4888CA62.5010602@goop.org>
Date: Thu, 24 Jul 2008 11:30:58 -0700
From: Jeremy Fitzhardinge <jeremy@goop.org>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: patrizio.bassi@gmail.com
CC: "Kernel, " <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.26 vanilla paravirt config issue
References: <4888B8CD.1030501@gmail.com>
In-Reply-To: <4888B8CD.1030501@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 928
Lines: 29

Patrizio Bassi wrote:
> Hi All
>
> on my amd64 profile i cannot disable PARAVIRT option.
>
> even if i disable all i still get in my .config:
>
> # CONFIG_X86_ES7000 is not set
> # CONFIG_X86_RDC321X is not set
> CONFIG_X86_VSMP=y
> # CONFIG_PARAVIRT_GUEST is not set
> CONFIG_PARAVIRT=y    <<<<-------------------------------- issue
> # CONFIG_MEMTEST_BOOTPARAM is not set
> # CONFIG_M386 is not set
>
> how to disable it? i guess it's a config bug.

As Randy pointed out, VSMP selects PARAVIRT.  VSMP does something 
strange with AC in rflags and interrupt enable/disable, and so hooks the 
appropriate pvops to implement it.

What's your underlying concern about PARAVIRT?

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/