From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: KVM: x86: relax MSR_KVM_SYSTEM_TIME alignment check Date: Fri, 22 Mar 2013 16:47:35 -0300 Message-ID: <20130322194735.GA21288@amt.cnet> References: <20130322191407.GA23681@amt.cnet> <20130322192100.GA9382@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andy Honig , kvm To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:20733 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754810Ab3CVTrt (ORCPT ); Fri, 22 Mar 2013 15:47:49 -0400 Content-Disposition: inline In-Reply-To: <20130322192100.GA9382@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, Mar 22, 2013 at 09:21:00PM +0200, Gleb Natapov wrote: > On Fri, Mar 22, 2013 at 04:14:07PM -0300, Marcelo Tosatti wrote: > > > > RHEL5 i386 guests register non 32-byte aligned addresses: > > > > kvm-clock: cpu 1, msr 0:3018aa5, secondary cpu clock > > kvm-clock: cpu 2, msr 0:301f8e9, secondary cpu clock > > kvm-clock: cpu 3, msr 0:302672d, secondary cpu clock > > > > Check for an address+len that would cross page boundary > > instead. > > > Ugh. Is there guaranty that it will not register a memory region that > crosses page boundary or it is pure luck that this does not happen? Pure build time luck - there is no guarantee that percpu data will not cross page boundary AFAIK.