qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: tutu sky <ooohooo_u@hotmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] emulation details of qemu
Date: Thu, 28 Apr 2016 19:45:59 +0100	[thread overview]
Message-ID: <87h9elefmg.fsf@linaro.org> (raw)
In-Reply-To: <HE1PR05MB13084A83E58676B697183E798D650@HE1PR05MB1308.eurprd05.prod.outlook.com>


tutu sky <ooohooo_u@hotmail.com> writes:

> Thanks a lot Stefan,
> But if i want to change the content of a register during run time in
> debug mode, what should i do? is it possible at first?

Using the gdbstub sure you can change the register values when the
machine is halted.

>
> Regards.
> ________________________________________
> From: Stefan Hajnoczi <stefanha@gmail.com>
> Sent: Tuesday, April 26, 2016 9:31 AM
> To: tutu sky
> Cc: qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] emulation details of qemu
>
> On Sat, Apr 23, 2016 at 06:36:39AM +0000, tutu sky wrote:
>> I want to know that is it possible to access registers or micro-architectural part of a core/cpu in qemu during run time?
>
> Yes.  How and to what extent depends on whether you are using TCG, KVM,
> or TCI.  QEMU also has gdbstub support so you can single-step execution
> and access CPU registers.
>
> Stefan


--
Alex Bennée

  reply	other threads:[~2016-04-28 18:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23  6:36 [Qemu-devel] emulation details of qemu tutu sky
2016-04-26  9:31 ` Stefan Hajnoczi
2016-04-28 10:48   ` tutu sky
2016-04-28 18:45     ` Alex Bennée [this message]
2016-04-29 10:56       ` tutu sky
2016-04-29 12:22         ` Alex Bennée
2016-04-29 12:39           ` tutu sky
2016-04-29 15:08             ` Alex Bennée
2016-04-29 15:24               ` tutu sky
2016-04-29 18:26                 ` Alex Bennée

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=87h9elefmg.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=ooohooo_u@hotmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).