xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	xen devel <xen-devel@lists.xensource.com>
Subject: RE: PoD in other (not GPLPV) drivers
Date: Thu, 03 Mar 2011 09:58:43 +0000	[thread overview]
Message-ID: <1299146323.19262.40.camel@elijah> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01C55A36@trantor>

On Mon, 2011-02-28 at 22:20 +0000, James Harper wrote:
> Is there a way for DomU to get an interrupt when an unpopulated page is
> hit when the DomU has gone past its initial limit? That would allow me
> to at least write a message to the log and crash usefully if I can't do
> anything else about it.

At the moment there's no mechanism for this.  Doing so would be a bit
tricky, as most of the places which do gfn_to_mfn() translations aren't
designed to handle failures gracefully (although that may have changed
since some of the guest paging stuff was introduced).

If we were to do this at some point in the future, what do you think
you'd like the interface to look like?  (i.e., deliver NMI? MCE? a
different but well-known interrupt?  &c)

 -George

  reply	other threads:[~2011-03-03  9:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AcvWIEDjcPpdP6eLTlqDXQDFzQWlHw==>
2011-02-27  1:47 ` PoD in other (not GPLPV) drivers James Harper
2011-02-28 11:59   ` George Dunlap
2011-02-28 12:17     ` Paul Durrant
2011-02-28 12:28       ` James Harper
2011-02-28 13:41         ` Paul Durrant
2011-02-28 14:17           ` George Dunlap
2011-02-28 22:09             ` James Harper
2011-02-28 22:20     ` James Harper
2011-03-03  9:58       ` George Dunlap [this message]
2011-03-03 10:22         ` James Harper
2011-03-03 11:30           ` Paul Durrant

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=1299146323.19262.40.camel@elijah \
    --to=george.dunlap@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --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).