This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] PoD in other (not GPLPV) drivers

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] PoD in other (not GPLPV) drivers
From: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
Date: Thu, 3 Mar 2011 11:30:53 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 03 Mar 2011 03:31:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01C55BBB@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AcvWIEDjcPpdP6eLTlqDXQDFzQWlHw==> <AEC6C66638C05B468B556EA548C1A77D01C559A4@trantor> <AANLkTim0bMXQSVmJD_SoMDkAeh8tq-UR8AJ8WksAwQFn@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C55A36@trantor> <1299146323.19262.40.camel@elijah> <AEC6C66638C05B468B556EA548C1A77D01C55BBB@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvZiYfzmq3pYtR2TiG1WQZpcZPgVwAAoO/AAAKOBeA=
Thread-topic: [Xen-devel] PoD in other (not GPLPV) drivers

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of James Harper
> Sent: 03 March 2011 10:22
> To: George Dunlap
> Cc: George Dunlap; xen devel
> Subject: RE: [Xen-devel] PoD in other (not GPLPV) drivers
> >
> > 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)
> >
> I don't know that there is a sactioned way to intercept an NMI under
> windows.


See http://msdn.microsoft.com/en-us/library/ff553116%28v=vs.85%29.aspx

> An MCE would do the trick probably. Basically I want the
> user to know that their VM crashed because it hit the PoD limit,
> rather than have no idea why it crashed. Most of the time if a user
> gets a crash I ask for a copy of /var/log/xen/qemu-dm-<domu>.log, so
> if the message appeared there then that would be fine with me too.
> I was under the impression that xen would blow the DomU up if it
> overstepped its PoD limit, but now I'm not so sure as I've seen
> windows BSoD with lots of different bug check codes when it happens.
> What should happen? I think that instant death is the only sensible
> outcome.
> James

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>