From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH 2 of 3] [v2] Move KVM TRACE DEFINITIONS to common header
Date: Sat, 05 Jul 2008 12:35:40 +0300
Message-ID: <486F406C.6070805@qumranet.com>
References: <463b4c3970c638fc3537.1213935554@thinkpadL>	 <4867770A.1080707@qumranet.com>	 <1214942353.6238.48.camel@localhost.localdomain> <1214947429.6238.53.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jerone Young <jyoung5@us.ibm.com>, kvm <kvm@vger.kernel.org>,
	kvm-ppc <kvm-ppc@vger.kernel.org>
To: Hollis Blanchard <hollisb@us.ibm.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from il.qumranet.com ([212.179.150.194]:48801 "EHLO il.qumranet.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751134AbYGEJfn (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sat, 5 Jul 2008 05:35:43 -0400
In-Reply-To: <1214947429.6238.53.camel@localhost.localdomain>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hollis Blanchard wrote:
> Move KVM trace definitions from x86 specific kvm headers to common kvm
> headers to create a cross-architecture numbering scheme for trace
> events. This means the kvmtrace_format userspace tool won't need to know
> which architecture produced the log file being processed.
>
>   

Applied, thanks.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.