From: Tamas K Lengyel <tamas.lengyel@zentific.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2] arm/vm_event: get/set registers
Date: Fri, 2 Sep 2016 11:37:02 -0600 [thread overview]
Message-ID: <CAErYnshW9Y7LEZv2tgVpnfwOVJAY1d_o6VoTNbJ==W1iezpR5A@mail.gmail.com> (raw)
In-Reply-To: <f0ea4cfd-ec06-d204-ecf4-94e33f2b378d@bitdefender.com>
On Tue, Aug 2, 2016 at 2:10 AM, Razvan Cojocaru
<rcojocaru@bitdefender.com> wrote:
> On 08/01/2016 08:59 PM, Tamas K Lengyel wrote:
>> Add support for getting/setting registers through vm_event on ARM. Only
>> TTB/CR/R0/R1, PC and CPSR are sent as part of a request and only PC is set
>> as part of a response. The set of registers can be expanded in the future to
>> include other registers as well if necessary.
>>
>> Signed-off-by: Tamas K Lengyel <tamas.lengyel@zentific.com>
>> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Patch ping.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-02 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 17:59 [PATCH v2] arm/vm_event: get/set registers Tamas K Lengyel
2016-08-02 8:10 ` Razvan Cojocaru
2016-09-02 17:37 ` Tamas K Lengyel [this message]
2016-09-02 17:45 ` Andrew Cooper
2016-09-02 18:40 ` Julien Grall
2016-09-02 18:47 ` Tamas K Lengyel
2016-09-02 19:10 ` Julien Grall
2016-09-02 19:19 ` Tamas K Lengyel
2016-09-05 19:45 ` Stefano Stabellini
2016-09-09 16:26 ` Tamas K Lengyel
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='CAErYnshW9Y7LEZv2tgVpnfwOVJAY1d_o6VoTNbJ==W1iezpR5A@mail.gmail.com' \
--to=tamas.lengyel@zentific.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).