From: Alexander Graf <agraf@suse.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
graalfs@linux.vnet.ibm.com, jfrei@linux.vnet.ibm.com,
jan.kiszka@siemens.com, pbonzini@redhat.com, aik@ozlabs.ru
Subject: Re: [PATCH 6/6] kvm_stat: Add powerpc support
Date: Wed, 18 Jun 2014 02:59:53 +0200 [thread overview]
Message-ID: <53A0E489.1040901@suse.de> (raw)
In-Reply-To: <1403052608.32307.1.camel@concordia>
On 18.06.14 02:50, Michael Ellerman wrote:
> On Tue, 2014-06-17 at 10:27 +0200, Alexander Graf wrote:
>> On 17.06.14 09:54, Michael Ellerman wrote:
>>> Add support for powerpc platforms. We use uname -m, which allows us to
>>> detect ppc, ppc64 and ppc64le/el.
>>>
>>> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>> Could you please add support for PR KVM tracepoints along the way? There
>> we do know the exit reason for every single guest <-> host transition. I
>> would like to move to a similar model with HV in the future, so we can
>> hopefully just reuse this by then.
> So I think what you're saying is you want it to somehow support using
> 'kvm_exit' for PR and 'kvm_userspace_exit' for HV?
"kvm_userspace_exit" is implemented on both HV and PR. "kvm_exit" is PR
only, but I'm hoping we can get it working in HV as well.
> Or actually use 'kvm_exit' if it exists and fall back to 'kvm_userspace_exit',
> so that if HV starts providing 'kvm_exit' the script will pick that up without
> further changes.
They are completely different things. "kvm_userspace_exit" tells us
which exits we take from KVM -> QEMU. "kvm_exit" tells us which exits we
take from guest -> KVM.
In fact, IIRC x86 also implements kvm_userspace_exit - or at least
something very similar to it. It's a completely separate category. Maybe
it should be a command line switch to distinguish between the count types?
Paolo, do you have any strong opinion here?
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: graalfs@linux.vnet.ibm.com, kvm@vger.kernel.org, aik@ozlabs.ru,
jan.kiszka@siemens.com, qemu-devel@nongnu.org,
jfrei@linux.vnet.ibm.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 6/6] kvm_stat: Add powerpc support
Date: Wed, 18 Jun 2014 02:59:53 +0200 [thread overview]
Message-ID: <53A0E489.1040901@suse.de> (raw)
In-Reply-To: <1403052608.32307.1.camel@concordia>
On 18.06.14 02:50, Michael Ellerman wrote:
> On Tue, 2014-06-17 at 10:27 +0200, Alexander Graf wrote:
>> On 17.06.14 09:54, Michael Ellerman wrote:
>>> Add support for powerpc platforms. We use uname -m, which allows us to
>>> detect ppc, ppc64 and ppc64le/el.
>>>
>>> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>> Could you please add support for PR KVM tracepoints along the way? There
>> we do know the exit reason for every single guest <-> host transition. I
>> would like to move to a similar model with HV in the future, so we can
>> hopefully just reuse this by then.
> So I think what you're saying is you want it to somehow support using
> 'kvm_exit' for PR and 'kvm_userspace_exit' for HV?
"kvm_userspace_exit" is implemented on both HV and PR. "kvm_exit" is PR
only, but I'm hoping we can get it working in HV as well.
> Or actually use 'kvm_exit' if it exists and fall back to 'kvm_userspace_exit',
> so that if HV starts providing 'kvm_exit' the script will pick that up without
> further changes.
They are completely different things. "kvm_userspace_exit" tells us
which exits we take from KVM -> QEMU. "kvm_exit" tells us which exits we
take from guest -> KVM.
In fact, IIRC x86 also implements kvm_userspace_exit - or at least
something very similar to it. It's a completely separate category. Maybe
it should be a command line switch to distinguish between the count types?
Paolo, do you have any strong opinion here?
Alex
next prev parent reply other threads:[~2014-06-18 0:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:54 [PATCH 1/6] kvm_stat: Only consider online cpus Michael Ellerman
2014-06-17 7:54 ` [Qemu-devel] " Michael Ellerman
2014-06-17 7:54 ` [PATCH 2/6] kvm_stat: Fix the non-x86 exit reasons Michael Ellerman
2014-06-17 7:54 ` [Qemu-devel] " Michael Ellerman
2014-10-31 15:49 ` Paolo Bonzini
2014-10-31 15:49 ` [Qemu-devel] " Paolo Bonzini
2014-06-17 7:54 ` [PATCH 3/6] kvm_stat: Rework platform detection Michael Ellerman
2014-06-17 7:54 ` [Qemu-devel] " Michael Ellerman
2014-06-17 7:54 ` [PATCH 4/6] kvm_stat: Fix tracepoint filter definition for s390 Michael Ellerman
2014-06-17 7:54 ` [Qemu-devel] " Michael Ellerman
2014-06-17 7:54 ` [PATCH 5/6] kvm_stat: Abstract ioctl numbers Michael Ellerman
2014-06-17 7:54 ` [Qemu-devel] " Michael Ellerman
2014-06-17 7:54 ` [PATCH 6/6] kvm_stat: Add powerpc support Michael Ellerman
2014-06-17 7:54 ` [Qemu-devel] " Michael Ellerman
2014-06-17 8:27 ` Alexander Graf
2014-06-17 8:27 ` [Qemu-devel] " Alexander Graf
2014-06-18 0:50 ` Michael Ellerman
2014-06-18 0:50 ` [Qemu-devel] " Michael Ellerman
2014-06-18 0:59 ` Alexander Graf [this message]
2014-06-18 0:59 ` Alexander Graf
2014-06-18 1:37 ` Michael Ellerman
2014-06-18 1:37 ` [Qemu-devel] " Michael Ellerman
2014-06-18 1:54 ` Alexander Graf
2014-06-18 1:54 ` [Qemu-devel] " Alexander Graf
2014-10-31 15:36 ` Paolo Bonzini
2014-10-31 15:36 ` [Qemu-devel] " Paolo Bonzini
2014-11-03 0:40 ` Michael Ellerman
2014-11-03 0:40 ` [Qemu-devel] " Michael Ellerman
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=53A0E489.1040901@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=graalfs@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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.