From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com,
"port-xen@netbsd.org" <port-xen@netbsd.org>,
"Miguel C." <miguelmclara@gmail.com>
Subject: Re: Fwd: NetBSD xl core-dump not working... Memory fault (core dumped)
Date: Tue, 12 Nov 2013 11:09:39 +0100 [thread overview]
Message-ID: <5281FE63.2060503@citrix.com> (raw)
In-Reply-To: <1384250453.1883.37.camel@kazak.uk.xensource.com>
On 12/11/13 11:00, Ian Campbell wrote:
> On Tue, 2013-11-12 at 10:48 +0100, Roger Pau Monné wrote:
>> Yes, NetBSD privcmd maps the region lazily (it does the actual map on
>> the page fault handler for that region).
>
> Thanks for the confirmation. Would it be expected that a message would
> be logged to dom0's dmesg if something went wrong here?
By doing a quick look at current NetBSD privcmd code I'm not sure a
message is printed on all error cases, so it's possible that it just
fails silently. You might get some messages from the hypervisor if
compiled with debug=y, but I have not tried it.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-12 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52770EED.9090804@gmx.de>
2013-11-04 22:13 ` Fwd: NetBSD xl core-dump not working... Memory fault (core dumped) Mike C.
2013-11-07 10:29 ` Ian Campbell
2013-11-07 21:04 ` [Xen-devel] " Miguel C.
2013-11-08 10:29 ` Ian Campbell
2013-11-08 17:20 ` John Nemeth
2013-11-12 9:35 ` Ian Campbell
2013-11-13 21:31 ` James Harper
2013-11-12 9:48 ` [Xen-devel] " Roger Pau Monné
2013-11-12 10:00 ` Ian Campbell
2013-11-12 10:09 ` Roger Pau Monné [this message]
2013-11-13 12:36 ` Miguel C.
2013-11-13 12:39 ` Roger Pau Monné
2013-11-13 17:59 ` Miguel C.
2013-12-03 18:14 ` Mike C.
2013-12-10 8:21 ` James Harper
2013-12-10 9:27 ` [Xen-devel] " James Harper
2013-12-10 10:41 ` Andrew Cooper
2013-12-10 10:46 ` James Harper
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=5281FE63.2060503@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=miguelmclara@gmail.com \
--cc=port-xen@netbsd.org \
--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).