* How to monitoring segment registers?
@ 2009-11-11 16:19 Jun Koi
2009-11-14 13:29 ` Avi Kivity
0 siblings, 1 reply; 2+ messages in thread
From: Jun Koi @ 2009-11-11 16:19 UTC (permalink / raw)
To: kvm
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?
Many thanks,
Jun
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How to monitoring segment registers?
2009-11-11 16:19 How to monitoring segment registers? Jun Koi
@ 2009-11-14 13:29 ` Avi Kivity
0 siblings, 0 replies; 2+ messages in thread
From: Avi Kivity @ 2009-11-14 13:29 UTC (permalink / raw)
To: Jun Koi; +Cc: kvm
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-11-14 13:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-11 16:19 How to monitoring segment registers? Jun Koi
2009-11-14 13:29 ` Avi Kivity
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox