Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752622Ab2FRO4l (ORCPT ); Mon, 18 Jun 2012 10:56:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45768 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751016Ab2FRO4j (ORCPT ); Mon, 18 Jun 2012 10:56:39 -0400 Date: Mon, 18 Jun 2012 17:56:26 +0300 From: "Michael S. Tsirkin" To: Avi Kivity Cc: x86@kernel.org, kvm@vger.kernel.org, Ingo Molnar , "H. Peter Anvin" , Marcelo Tosatti , gleb@redhat.com, Linus Torvalds , linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: [PATCHv7 5/8] kvm: eoi msi documentation Message-ID: <20120618145626.GF26540@redhat.com> References: <4FDF3911.7020902@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FDF3911.7020902@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1729 Lines: 40 On Mon, Jun 18, 2012 at 05:20:01PM +0300, Avi Kivity wrote: > On 06/14/2012 04:53 PM, Michael S. Tsirkin wrote: > > Document the new EOI MSR. Couldn't decide whether this change belongs > > conceptually on guest or host side, so a separate patch. > > > > Signed-off-by: Michael S. Tsirkin > > --- > > Documentation/virtual/kvm/msr.txt | 32 ++++++++++++++++++++++++++++++++ > > 1 file changed, 32 insertions(+) > > > > diff --git a/Documentation/virtual/kvm/msr.txt b/Documentation/virtual/kvm/msr.txt > > index 96b41bd..6ae5a85 100644 > > --- a/Documentation/virtual/kvm/msr.txt > > +++ b/Documentation/virtual/kvm/msr.txt > > @@ -223,3 +223,35 @@ MSR_KVM_STEAL_TIME: 0x4b564d03 > > steal: the amount of time in which this vCPU did not run, in > > nanoseconds. Time during which the vcpu is idle, will not be > > reported as steal time. > > + > > +MSR_KVM_EOI_EN: 0x4b564d04 > > + data: Bit 0 is 1 when PV end of interrupt is enabled on the vcpu; 0 > > + when disabled. When enabled, bits 63-1 hold 2-byte aligned physical address > > + of a 2 byte memory area which must be in guest RAM and must be zeroed. > > 2 byte aligned means we must never access it on the host with a >2 byte > instruction, or we risk touching unmapped memory. Yes. So ... that's correct for any length. The patch actually accesses a single byte only. Could you clarify what you are saying here please? > -- > error compiling committee.c: too many arguments to function > -- 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/