public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Masatake YAMATO <yamato@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH resend] kvm: embed vcpu id to dentry of vcpu anon inode
Date: Thu, 25 Jan 2018 16:36:43 +0100	[thread overview]
Message-ID: <20180125153643.GD19884@flask> (raw)
In-Reply-To: <20180119190422.6591-1-yamato@redhat.com>

2018-01-20 04:04+0900, Masatake YAMATO:
> All d-entries for vcpu have the same, "anon_inode:kvm-vcpu". That means
> it is impossible to know the mapping between fds for vcpu and vcpu
> from userland.
> 
>     # LC_ALL=C ls -l /proc/617/fd | grep vcpu
>     lrwx------. 1 qemu qemu 64 Jan  7 16:50 18 -> anon_inode:kvm-vcpu
>     lrwx------. 1 qemu qemu 64 Jan  7 16:50 19 -> anon_inode:kvm-vcpu
> 
> It is also impossible to know the mapping between vma for kvm_run
> structure and vcpu from userland.
> 
>     # LC_ALL=C grep vcpu /proc/617/maps
>     7f9d842d0000-7f9d842d3000 rw-s 00000000 00:0d 20393                      anon_inode:kvm-vcpu
>     7f9d842d3000-7f9d842d6000 rw-s 00000000 00:0d 20393                      anon_inode:kvm-vcpu
> 
> This change adds vcpu id to d-entries for vcpu. With this change
> you can get the following output:
> 
>     # LC_ALL=C ls -l /proc/617/fd | grep vcpu
>     lrwx------. 1 qemu qemu 64 Jan  7 16:50 18 -> anon_inode:kvm-vcpu:0
>     lrwx------. 1 qemu qemu 64 Jan  7 16:50 19 -> anon_inode:kvm-vcpu:1
> 
>     # LC_ALL=C grep vcpu /proc/617/maps
>     7f9d842d0000-7f9d842d3000 rw-s 00000000 00:0d 20393                      anon_inode:kvm-vcpu:0
>     7f9d842d3000-7f9d842d6000 rw-s 00000000 00:0d 20393                      anon_inode:kvm-vcpu:1
> 
> With the mappings known from the output, a tool like strace can report more details
> of qemu-kvm process activities. Here is the strace output of my local prototype:
> 
>     # ./strace -KK -f -p 617 2>&1 | grep 'KVM_RUN\| K'
>     ...
>     [pid   664] ioctl(18, KVM_RUN, 0)       = 0 (KVM_EXIT_MMIO)
>      K ready_for_interrupt_injection=1, if_flag=0, flags=0, cr8=0000000000000000, apic_base=0x000000fee00d00
>      K phys_addr=0, len=1634035803, [33, 0, 0, 0, 0, 0, 0, 0], is_write=112
>     [pid   664] ioctl(18, KVM_RUN, 0)       = 0 (KVM_EXIT_MMIO)
>      K ready_for_interrupt_injection=1, if_flag=1, flags=0, cr8=0000000000000000, apic_base=0x000000fee00d00
>      K phys_addr=0, len=1634035803, [33, 0, 0, 0, 0, 0, 0, 0], is_write=112
>     ...
> 
> Signed-off-by: Masatake YAMATO <yamato@redhat.com>
> ---

Queued, thanks.

      parent reply	other threads:[~2018-01-25 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 19:04 [PATCH resend] kvm: embed vcpu id to dentry of vcpu anon inode Masatake YAMATO
2018-01-19 19:21 ` Christian Borntraeger
2018-01-25 15:36 ` Radim Krčmář [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=20180125153643.GD19884@flask \
    --to=rkrcmar@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=yamato@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