From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC 1/8]KVM: fix bugs in kvm sched integration patch Date: Tue, 24 Jul 2007 08:35:04 +0300 Message-ID: <46A58F88.9050906@qumranet.com> References: <1185173492.2645.65.camel@sli10-conroe.sh.intel.com> <46A48713.9080404@qumranet.com> <1185241544.24201.15.camel@sli10-conroe.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , lkml To: Shaohua Li Return-path: In-Reply-To: <1185241544.24201.15.camel-yAZKuqJtXNMXR+D7ky4Foa2pdiUAq4bhAL8bYrjMMd8@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 Shaohua Li wrote: >> >>> 1. vmcs_readl/vmcs_writel are called with preempt enabled >>> >>> >> Why is that bad? >> > 1. raw_smp_processor_id() > 2. migrate to other cpu > 3. current->kvm_vcpu->cpu != the cpu id of step 1. > you will see the warning. > Ah, that code is gone from preempt-hooks, hence I didn't understand you. The current version of the patchset does not change vmcs_readl/vmcs_writel. So I think everything is safe. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/