From: Avi Kivity <avi@redhat.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: How to monitoring segment registers?
Date: Sat, 14 Nov 2009 15:29:32 +0200 [thread overview]
Message-ID: <4AFEB0BC.202@redhat.com> (raw)
In-Reply-To: <fdaac4d50911110819tba462e8j6d137e1027d933@mail.gmail.com>
On 11/11/2009 06:19 PM, Jun Koi wrote:
> Hi,
>
> I am doing some profiling for a guest VM on KVM. One of things I want
> to do is to monitor the activities of SS register.
>
> Specifically, I want to be notified whenever guest's SS changes its
> value (like when OS switches from userspace stack to kernel stack).
>
> I imagine that I need to reprogram VMCS, so I can get VMEXIT anytime
> SS changes its value.
> Is that feasible? If so, which code should I look at in kvm code?
>
Virtualization extensions don't allow trapping on segment register
changes. I recommend modifying qemu/tcg instead.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-11-14 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 16:19 How to monitoring segment registers? Jun Koi
2009-11-14 13:29 ` Avi Kivity [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=4AFEB0BC.202@redhat.com \
--to=avi@redhat.com \
--cc=junkoi2004@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox