From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>,
Don Slutz <don.slutz@gmail.com>, Jan Beulich <jbeulich@suse.com>,
Wei Liu <wei.liu2@citrix.com>,
Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: Re: [PATCH 2/2] Add xen-hyp-rw
Date: Thu, 18 Jun 2015 18:05:03 +0100 [thread overview]
Message-ID: <5582FA3F.4030108@citrix.com> (raw)
In-Reply-To: <1434642932-24807-3-git-send-email-dslutz@verizon.com>
On 18/06/15 16:55, Don Slutz wrote:
> This allows reading and writing of variables in the hypervisor.
>
> for example (read case -- default 4 bytes):
>
> xen-hyp-rw /boot/System.map-xen* opt_hvm_debug_level
> opt_hvm_debug_level @ 0xffff82d080285610 is 0x0(0)
>
> Write case:
>
> xen-hyp-rw /boot/System.map-xen* opt_hvm_debug_level 4 -1
> opt_hvm_debug_level @ 0xffff82d080285610 is 0x0(0)
> opt_hvm_debug_level @ 0xffff82d080285610 set to 0xffffffff(4294967295)
>
> Signed-off-by: Don Slutz <dslutz@verizon.com>
> CC: Don Slutz <don.slutz@gmail.com>
As a crazy thought...
Would it not be easier to modify gdbsx to allow gdb to connect remotely
to the hypervisor context?
That way, any gdb-like tools could consume an appropriate xen-syms and
make changes like this.
~Andrew
next prev parent reply other threads:[~2015-06-18 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 15:55 [PATCH 0/2] Allow chnaging of external varibles in the hypervisor Don Slutz
2015-06-18 15:55 ` [PATCH 1/2] gdbsx_guestmemio: Allow it to check domain Don Slutz
2015-06-18 16:59 ` Andrew Cooper
2015-06-18 20:39 ` Don Slutz
2015-06-18 15:55 ` [PATCH 2/2] Add xen-hyp-rw Don Slutz
2015-06-18 17:05 ` Andrew Cooper [this message]
2015-06-18 20:50 ` Don Slutz
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=5582FA3F.4030108@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=don.slutz@gmail.com \
--cc=dslutz@verizon.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=mukesh.rathor@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.