public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] trace "exit to userspace" event
Date: Thu, 14 Oct 2010 13:28:43 +0200	[thread overview]
Message-ID: <20101014112843.GJ19207@redhat.com> (raw)
In-Reply-To: <4CB6E558.6010009@redhat.com>

On Thu, Oct 14, 2010 at 01:11:20PM +0200, Avi Kivity wrote:
>  On 10/14/2010 12:29 PM, Gleb Natapov wrote:
> >On Thu, Oct 14, 2010 at 12:27:15PM +0200, Avi Kivity wrote:
> >>   On 10/10/2010 05:46 PM, Gleb Natapov wrote:
> >>  >>
> >>  >>   We should log both errno and exit_reason.  If we want to be clever,
> >>  >>   we can display strerror(errno) if it's nonzero, and exit_reason
> >>  >>   otherwise (easy to do in a trace-cmd plugin).
> >>  >>
> >>  >For starters we should remove KVM_EXIT_INTR exit reason. Looking into
> >>  >qemu-kvm history it was never used and there is at least one code path
> >>  >that returns -EINTR and does not set KVM_EXIT_INTR, so exit_reason field
> >>  >contains stale info on exit.
> >>  >
> >>
> >>  The two issues are unrelated.
> >>
> >So what do you propose? I see no issue with my original patch.
> 
> Record both errno and exit_reason.  While they're never both valid
> at the same time, they're both necessary.
> 
If they can't be valid at the same time, why not record one of them? The
one that happened? Also any error other then -EINTR will cause qemu to
stop, so it is not very interesting. And ioctl return value can be
traced by strace anyway.

--
			Gleb.

  reply	other threads:[~2010-10-14 11:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 13:14 [PATCH] trace "exit to userspace" event Gleb Natapov
2010-10-07 16:18 ` Marcelo Tosatti
2010-10-07 17:56   ` Gleb Natapov
2010-10-08  0:49     ` Marcelo Tosatti
2010-10-08 16:44       ` Gleb Natapov
2010-10-10  8:45         ` Avi Kivity
2010-10-10 15:46           ` Gleb Natapov
2010-10-14 10:27             ` Avi Kivity
2010-10-14 10:29               ` Gleb Natapov
2010-10-14 11:11                 ` Avi Kivity
2010-10-14 11:28                   ` Gleb Natapov [this message]
2010-10-14 11:32                     ` Avi Kivity
2010-10-14 11:41                       ` Gleb Natapov
2010-10-14 11:43                         ` Avi Kivity
2010-10-14 11:47                           ` Gleb Natapov
2010-10-14 12:09                             ` Avi Kivity
2010-10-14 12:10                               ` Avi Kivity

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=20101014112843.GJ19207@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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