From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Status of SMP? Date: Sun, 18 Mar 2007 07:48:17 +0200 Message-ID: <45FCD2A1.8040704@qumranet.com> References: <8FFF7E42E93CC646B632AB40643802A8023B8983@scsmsx412.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: "Nakajima, Jun" Return-path: In-reply-to: <8FFF7E42E93CC646B632AB40643802A8023B8983-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Nakajima, Jun wrote: > Avi Kivity wrote: > >> I'd also like to add a read-only memory type so that apic reads can >> proceed natively rather than be emulated (the TODO has this now). >> > > I don't understand how this can work. You're right - it can't. I thought all read accesses are static and side-effect-free, but reading the timer is not static. > Instead, we should use the > hardware-based virtualization for the local APIC. > Can you point me at documentation for that? What I have only mentions tpr/cr8 shadow, but not much else. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV