From: Avi Kivity <avi@qumranet.com>
To: "Tan, Li" <li.tan@intel.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] [RFC][PATCH] kvm: kvmtrace: kvm_trace in kernel for supporting big_endian
Date: Tue, 20 May 2008 19:25:43 +0300 [thread overview]
Message-ID: <4832FB87.9020501@qumranet.com> (raw)
In-Reply-To: <08DF4D958216244799FC84F3514D70F00164BF05@pdsmsx415.ccr.corp.intel.com>
Tan, Li wrote:
> From 63283d32ad5faf0845fa0358fd71d119f4dc0e3d Mon Sep 17 00:00:00 2001
> From: Tan Li <li.tan@intel.com>
> Date: Mon, 19 May 2008 17:18:54 +0800
> Subject: [PATCH] [RFC][PATCH] kvm: kvmtrace: kvm_trace in kernel for
> supporting big_endian
>
> Currently kvmtrace is not portable. This will prevent from copying a
> trace file from big-endian target to little-endian workstation for
> analysis.
>
> In the patch, kernel outputs metadata containing a magic number to trace
> log.
>
> diff --git a/include/linux/kvm.h b/include/linux/kvm.h
> index a281afe..ca08cb1 100644
> --- a/include/linux/kvm.h
> +++ b/include/linux/kvm.h
> @@ -294,14 +294,14 @@ struct kvm_trace_rec {
> __u32 vcpu_id;
> union {
> struct {
> - __u32 cycle_lo, cycle_hi;
> + __u64 cycle_u64;
> __u32 extra_u32[KVM_TRC_EXTRA_MAX];
> } cycle;
>
For this bit, you'll need to change 'II' to 'L' in the format, no?
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-05-20 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <08DF4D958216244799FC84F3514D70F0015B1B58@pdsmsx415.ccr.corp.intel.com>
2008-05-14 21:37 ` kvm trace support for ppc Hollis Blanchard
2008-05-15 1:20 ` Tan, Li
2008-05-16 6:26 ` Tan, Li
2008-05-20 6:53 ` [PATCH] [RFC][PATCH] kvm: kvmtrace: kvm_trace in kernel for supporting big_endian Tan, Li
2008-05-20 7:03 ` [PATCH] [RFC][PATCH] kvm: kvmtrace: kvmtrace_format " Tan, Li
2008-05-20 16:22 ` Avi Kivity
2008-05-21 7:36 ` Tan, Li
2008-05-21 9:21 ` Avi Kivity
2008-05-22 0:30 ` Tan, Li
2008-05-25 9:34 ` Avi Kivity
2008-05-26 5:38 ` Tan, Li
2008-05-28 11:17 ` Avi Kivity
2008-06-02 1:25 ` Tan, Li
2008-05-20 16:25 ` 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=4832FB87.9020501@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=li.tan@intel.com \
/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