From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 2/2] KVM: Document KVM_SET_TSS_ADDR Date: Thu, 25 Mar 2010 14:02:13 +0200 Message-ID: <4BAB50C5.400@redhat.com> References: <1269513099-21060-1-git-send-email-avi@redhat.com> <1269513099-21060-3-git-send-email-avi@redhat.com> <4BAB3CB5.7050303@cs.helsinki.fi> <4BAB3E67.2040504@redhat.com> <4BAB506C.7060609@cs.helsinki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Marcelo Tosatti To: Pekka Enberg Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44251 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752107Ab0CYMCR (ORCPT ); Thu, 25 Mar 2010 08:02:17 -0400 In-Reply-To: <4BAB506C.7060609@cs.helsinki.fi> Sender: kvm-owner@vger.kernel.org List-ID: On 03/25/2010 02:00 PM, Pekka Enberg wrote: >> I don't think such a technical description of an implementation >> detail has a place in the API reference; maybe in internal >> documentation. > > > Sure but it would be nice to have something along the lines of "This > is needed on Intel hardware because of a quirk in the virtualization > implementation" and maybe point the reader to a more appropriate > document (internals document, Intel manuals, ...). Ok, will add. -- error compiling committee.c: too many arguments to function