[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Will hap_alloc fail?


  • To: "Huang2, Wei" <Wei.Huang2@xxxxxxx>, "Tim Deegan" <Tim.Deegan@xxxxxxxxxxxxx>
  • From: Mats Petersson <mats@xxxxxxxxxxxxxxxxx>
  • Date: Thu, 12 Jul 2007 18:19:00 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 17 Jul 2007 05:07:15 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:x-mailer:date:to:from:subject:cc:in-reply-to:references:mime-version:content-type:sender:message-id; b=sPQfvizbgOnmIhoNZwPt5ssQnih3edQeZzLbKlM7LfRDo0Fsy45PB70hueghHuaRFF0BKqHm6ZVCsO3zbWdbgs/pntm2FoiaHU9El2W6vvV1ez8zCupHdBU9go38QRPyWcY3uXk6/x+JeK4XI1EZwgffLfA8o0p2H0NKZnplArY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

At 18:14 12/07/2007, Huang2, Wei wrote:
Tim Deegan wrote:
> At 11:34 -0500 on 12 Jul (1184240066), Huang2, Wei wrote:
>> How does this fix sound?
>
> I think we need somaething that crashes just the guest in question --
> this patch just replaces a probable pagefault crash with an explicit
> BUG().

Do you think domain_crash() work here? Or you want some way to propagate
error information from hap_alloc() to upper levels?

Note: I'm not speaking on behalf of ANYONE here.

I would have thought that domain_crash() is the right thing to do - there's nothing "better" that can be done elsewhere, as far as I can understand, and there's really no point in propagating an error unless there's something that can be done about it (or it can be ignored, which isn't the case in this instance), as this only leads to potential misses of the propagated error, making it harder to debug.

--
Mats


Thanks,

-Wei



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.