public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org, Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Carsten Otte <cotte@de.ibm.com>
Subject: Re: kvm-s390: Dont exit SIE on SIGP sense running
Date: Mon, 21 Jun 2010 12:15:33 +0200	[thread overview]
Message-ID: <201006211215.33599.borntraeger@de.ibm.com> (raw)
In-Reply-To: <4C1F2286.7090108@redhat.com>

Am Montag 21 Juni 2010, 10:27:50 schrieb Avi Kivity:
[...]
> >   	VCPU_EVENT(vcpu, 3, "%s", "free cpu");
> > +	clear_bit(63 - vcpu->vcpu_id, (unsigned long *)&vcpu->kvm->arch.sca->mcn);
> >   	if (vcpu->kvm->arch.sca->cpu[vcpu->vcpu_id].sda ==
> >   		(__u64) vcpu->arch.sie_block)
> >   		vcpu->kvm->arch.sca->cpu[vcpu->vcpu_id].sda = 0;
> >    
> 
> Unrelated, do these VCPU_EVENTs want to become ftrace tracepoints?
> 
> 

Hmm, dont know. Currently this calls into a s390 debug tracing facility
(arch/s390/kernel/debug.c) which is heavily used by our service folks.
There are commands for crash and lcrash to show these s390 debug traces
from a dump.

Maybe its worth to investigate if we should change some of these events to
have both ftrace-tracepoints and the debug traces.

Christian

  reply	other threads:[~2010-06-21 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 21:16 kvm-s390: Dont exit SIE on SIGP sense running Christian Borntraeger
2010-06-21  8:27 ` Avi Kivity
2010-06-21 10:15   ` Christian Borntraeger [this message]
2010-06-21 10:26     ` Arnd Bergmann

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=201006211215.33599.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=avi@redhat.com \
    --cc=cotte@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=schwidefsky@de.ibm.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