From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Jerone Young <jyoung5@us.ibm.com>, kvm <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH 2 of 3] [v2] Move KVM TRACE DEFINITIONS to common header
Date: Sat, 05 Jul 2008 09:35:40 +0000 [thread overview]
Message-ID: <486F406C.6070805@qumranet.com> (raw)
In-Reply-To: <1214947429.6238.53.camel@localhost.localdomain>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Jerone Young <jyoung5@us.ibm.com>, kvm <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH 2 of 3] [v2] Move KVM TRACE DEFINITIONS to common header
Date: Sat, 05 Jul 2008 12:35:40 +0300 [thread overview]
Message-ID: <486F406C.6070805@qumranet.com> (raw)
In-Reply-To: <1214947429.6238.53.camel@localhost.localdomain>
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.
next prev parent reply other threads:[~2008-07-05 9:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 4:19 [PATCH 0 of 3] Add ability for KVM TRACE to work on other archs Jerone Young
2008-06-20 4:19 ` Jerone Young
2008-06-20 4:19 ` [PATCH 1 of 3] Remove use of bit fields in kvm trace structure Jerone Young
2008-06-20 4:19 ` Jerone Young
2008-06-20 16:59 ` Hollis Blanchard
2008-06-20 16:59 ` Hollis Blanchard
2008-06-23 2:33 ` Avi Kivity
2008-06-23 2:33 ` Avi Kivity
2008-06-20 4:19 ` [PATCH 2 of 3] Move KVM TRACE DEFINITIONS to common header Jerone Young
2008-06-20 4:19 ` Jerone Young
2008-06-29 11:50 ` Avi Kivity
2008-06-29 11:50 ` Avi Kivity
2008-07-01 19:59 ` Hollis Blanchard
2008-07-01 19:59 ` Hollis Blanchard
2008-07-01 21:23 ` [PATCH 2 of 3] [v2] " Hollis Blanchard
2008-07-01 21:23 ` Hollis Blanchard
2008-07-05 9:35 ` Avi Kivity [this message]
2008-07-05 9:35 ` Avi Kivity
2008-06-20 4:19 ` [PATCH 3 of 3] Add new KVM TRACE events Jerone Young
2008-06-20 4:19 ` Jerone Young
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=486F406C.6070805@qumranet.com \
--to=avi@qumranet.com \
--cc=hollisb@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.