On Fri, Jul 31, 2015 at 3:32 PM, Peter Maydell
wrote:
> On 31 July 2015 at 10:29, Naman patel wrote:
> > Can someone explain me what happens when a guest OS calls "invlpg" on say
> > page swap out or a context switch? What exactly is the call flow and how
> > QEMU handles this instruction?
>
> W
On 31 July 2015 at 10:29, Naman patel wrote:
> Can someone explain me what happens when a guest OS calls "invlpg" on say
> page swap out or a context switch? What exactly is the call flow and how
> QEMU handles this instruction?
When we see the instruction during translation, we emit code
which w
Thanks Alex and Peter for this useful information. Looks like the stack
information is not available for this functions in QEMU 2.0.
Can someone explain me what happens when a guest OS calls "invlpg" on say
page swap out or a context switch? What exactly is the call flow and how
QEMU handles this
Peter Maydell writes:
> On 30 July 2015 at 13:20, Naman patel wrote:
>> Hi,
>>
>> I have compiled QEMU (2.0) for x86_64 on Fedora 22 with tracing enabled
>> and the tracing option I chose was dtrace. I have this script called
>> callTrace.stp in which I try and get the Call Trace of the fu
On 30 July 2015 at 13:20, Naman patel wrote:
> Hi,
>
> I have compiled QEMU (2.0) for x86_64 on Fedora 22 with tracing enabled
> and the tracing option I chose was dtrace. I have this script called
> callTrace.stp in which I try and get the Call Trace of the function
> helper_invlpg and later
