From: Andi Kleen <andi@firstfloor.org>
Organization: -
To: Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH] [19/50] Experimental: detect if SVM is disabled by BIOS
Date: Mon, 1 Oct 2007 18:47:50 +0200
User-Agent: KMail/1.9.6
Cc: patches@x86-64.org, linux-kernel@vger.kernel.org
References: <200709221231.836138000@suse.de> <20070921223218.22A8D13DCD@wotan.suse.de> <20070922091708.GD8998@8bytes.org>
In-Reply-To: <20070922091708.GD8998@8bytes.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200710011847.50533.andi@firstfloor.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 851
Lines: 21

On Saturday 22 September 2007 11:17:08 Joerg Roedel wrote:
> I don't think we need this patch. When SVM is disabled KVM will tell on
> module load. 

The point is that people often want to know in advance (before they
even try to use KVM or Xen) if their CPU and BIOS supports this.

> Further with SVM-lock it will be possible to re-enable SVM 
> even if it was disabled by BIOS using a key. In this case the user of
> SVM has to clear the capability bit you set in this patch for all cpus.

Not sure I follow you. Can you clarify?  What exactly needs to be
done to do a full non reversible lock? 

-Andi

-
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/