From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: kvmmmu tracing
Date: Tue, 24 Nov 2009 16:17:36 +0200
Message-ID: <4B0BEB00.5090703@redhat.com>
References: <1258974375.7094.158.camel@johannes.local>	 <4B0BAC76.3080202@redhat.com> <1259057130.3985.1.camel@johannes.local>	 <4B0BB6B1.5010302@redhat.com> <1259071713.3491.2.camel@johannes.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Steven Rostedt <srostedt@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S933058AbZKXOSG@vger.kernel.org>
In-Reply-To: <1259071713.3491.2.camel@johannes.local>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 11/24/2009 04:08 PM, Johannes Berg wrote:
> On Tue, 2009-11-24 at 12:34 +0200, Avi Kivity wrote:
>
>    
>> Um, C can be easily parsed with a C compiler.  I don't think you can
>> expect it to be a plain format string and argument list.
>>      
> Actually, it turns out that it cannot be parsed even with a C compiler:
>
> ({ const char *ret = p->buffer + p->len; static const char *access_str[]
> = { "---", "--x", "w--", "w-x", "-u-", "-ux", "wu-", "wux" }; union
> kvm_mmu_page_role role;
>
> ...
>
> userspace cannot possibly know from this what "union kvm_mmu_page_role"
> is.
>    

We can expose kvm_mmu_page_role, but that's a new can of worms.  And 
it's certainly not meant to be stable across kernel versions.

-- 
error compiling committee.c: too many arguments to function