[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <500FDC9E.3010504@parallels.com>
Date: Wed, 25 Jul 2012 15:46:38 +0400
From: Vladimir Davydov <vdavydov@...allels.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Andre Przywara <andre.przywara@....com>,
Borislav Petkov <bp@...64.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...ux.intel.com>,
Borislav Petkov <borislav.petkov@....com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andreas Herrmann <andreas.herrmann3@....com>,
Pavel Emelianov <xemul@...allels.com>,
Konstantin Khorenko <khorenko@...allels.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: Re: [PATCH 2/2] cpu: intel, amd: mask cleared cpuid features
On 07/25/2012 03:31 PM, Alan Cox wrote:
> On Wed, 25 Jul 2012 14:31:30 +0400
> Vladimir Davydov<vdavydov@...allels.com> wrote:
>
>> On 07/24/2012 04:44 PM, Alan Cox wrote:
>>>> This approach does not need any kernel support (except for the
>>>> /proc/cpuinfo filtering). Does this address the issues you have?
>>> You can do the /proc/cpuinfo filtering in user space too
>>>
>> How?
> bind mount your own normal file over the top or a FUSE file
In general, we've agreed that wiring CPUID masking into the kernel was
not a good idea.
We will try to virtualize /proc/cpuinfo as well as other /proc stuff in
mainstream.
Thank you for your time and feedback.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists