From: Keir Fraser <keir@xen.org>
To: Aravindh Puthiyaparambil <aravindh@virtuata.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: [PATCH] mem_event: Allow memory access listener to perform single step execution
Date: Sat, 28 May 2011 22:41:14 +0100 [thread overview]
Message-ID: <CA072A8A.2E074%keir@xen.org> (raw)
In-Reply-To: <BANLkTikGHg=3S5NXHjG2vcv+sKw1atr8PA@mail.gmail.com>
On 28/05/2011 18:48, "Aravindh Puthiyaparambil" <aravindh@virtuata.com>
wrote:
> Sorry about the build breakage. I will test the 32-bit side of things
> also in the future.
>
> I did not realize VCPU pausing was nestable. So even after the
> vcpu_unpause() in hvm_debug_op(), the VCPU will still be paused
> because of the vcpu_pause() in p2m_mem_access_check()?
Yes that's right.
-- Keir
> If that is the
> case I am fine with the combination for 4.1.1.
prev parent reply other threads:[~2011-05-28 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 3:39 [PATCH] mem_event: Allow memory access listener to perform single step execution Aravindh Puthiyaparambil
2011-05-27 8:39 ` Tim Deegan
2011-05-27 16:36 ` Aravindh Puthiyaparambil
2011-05-28 7:53 ` Keir Fraser
2011-05-28 17:48 ` Aravindh Puthiyaparambil
2011-05-28 21:41 ` Keir Fraser [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=CA072A8A.2E074%keir@xen.org \
--to=keir@xen.org \
--cc=Tim.Deegan@citrix.com \
--cc=aravindh@virtuata.com \
--cc=xen-devel@lists.xensource.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).