From: Avi Kivity <avi@qumranet.com>
To: "Liu, Eric E" <eric.e.liu@intel.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/2]kvmtrace: add event mask support (kernel part)
Date: Tue, 22 Apr 2008 15:52:24 +0300 [thread overview]
Message-ID: <480DDF88.50203@qumranet.com> (raw)
In-Reply-To: <9D7649D18729DE4BB2BD7B494F7FEDC201261FEE@pdsmsx415.ccr.corp.intel.com>
Liu, Eric E wrote:
> >From a1b062cfd4d1a91c447b680ac9a2250fe55119ec Mon Sep 17 00:00:00 2001
> From: Feng (Eric) Liu <eric.e.liu@intel.com>
> Date: Wed, 16 Apr 2008 05:29:37 -0400
> Subject: [PATCH] KVM: trace: Add event mask support.
>
> Allow user space application to specify one or more
> filter masks to limit the events being captured via it.
>
>
Sorry about the late review.
> --- a/include/linux/kvm.h
> +++ b/include/linux/kvm.h
> @@ -18,6 +18,8 @@
> struct kvm_user_trace_setup {
> __u32 buf_size; /* sub_buffer size of each per-cpu */
> __u32 buf_nr; /* the number of sub_buffers of each per-cpu */
> + __u16 cat_mask; /* the tracing categories are enabled */
> + __u64 act_bitmap[16]; /* the actions are enabled for each
> category */
> };
>
The structures will be laid out differently on 32-bit and 64-bit. This
is important since we'd like 32-bit userspace to work correctly with a
64-bit kernel. The usual solution is to insert a "__u16 pad1[3];"
between the two fields.
Otherwise, the patch seems fine.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-04-22 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 7:19 [PATCH 1/2]kvmtrace: add event mask support (kernel part) Liu, Eric E
2008-04-22 12:52 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480DDF88.50203@qumranet.com \
--to=avi@qumranet.com \
--cc=eric.e.liu@intel.com \
--cc=kvm-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox