All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: quizyjones <quizy_jones@outlook.com>, Tim Deegan <tim@xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: xen panics when setting int3 traps
Date: Fri, 18 Dec 2015 15:31:18 +0000	[thread overview]
Message-ID: <567426C6.6030203@citrix.com> (raw)
In-Reply-To: <SNT152-W6866199A8E410D9F6F2D0E90E00@phx.gbl>


[-- Attachment #1.1: Type: text/plain, Size: 1125 bytes --]

On 17/12/15 01:35, quizyjones wrote:
> Sorry for the late reply, there is something wrong in network which
> makes the email not delivered successfully.
> The inject method is by using xc_map_foreign_range to map the address
> of the nested xen and memcpy the trap to the specific location. If
> there is a problem, it should be the xc_map_foreign_range function,
> can it map L1 xen's memory to dom0 of L0 xen? It might  mapping the
> memory of nested dom0 instead of the nested xen, as the error says
> that the max physical address is 0xff000000 when I tried to operate on
> memory space of xen
> <http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/asm-x86/config.h#l162> using
> xc_map_foreign_range.

You cannot simply put breakpoints in the domain, as they will be handled
by the domain itself.  As you observe, Xen gets rightfully unhappy when
it finds breapoints in its own virtual range.

You need to follow the same actions as `gdbsx` (as an example) which
registers itself as a debugger of the domain, and hooks breakpoints,
rather than letting the guest deal with them in an unexpected manor.

~Andrew

[-- Attachment #1.2: Type: text/html, Size: 2006 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-12-18 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  1:42 xen panics when setting int3 traps quizy_jones
2015-12-11  2:01 ` quizy_jones
2015-12-11  2:17   ` Konrad Rzeszutek Wilk
2015-12-11  3:13     ` quizy_jones
2015-12-11 10:20       ` Tim Deegan
2015-12-17  1:35         ` quizyjones
2015-12-18 15:31           ` Andrew Cooper [this message]
2015-12-19  4:23             ` quizyjones
2015-12-18  6:15         ` Tian, Kevin
2015-12-11  9:54 ` Andrew Cooper

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=567426C6.6030203@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=quizy_jones@outlook.com \
    --cc=tim@xen.org \
    --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.