WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 01/04] Kexec / Kdump: Generic code

To: Horms <horms@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 01/04] Kexec / Kdump: Generic code
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 18 Oct 2006 08:15:45 +0100
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Kazuo Moriwaka <moriwaka@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, magnus.damm@xxxxxxxxx, Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, Magnus Damm <magnus@xxxxxxxxxxxxx>
Delivery-date: Wed, 18 Oct 2006 00:27:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061018010003.GC11422@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbyhTpXeLwo5F54EdupPAANk04WTA==
Thread-topic: [PATCH 01/04] Kexec / Kdump: Generic code
User-agent: Microsoft-Entourage/11.2.5.060620
On 18/10/06 2:00 am, "Horms" <horms@xxxxxxxxxxxx> wrote:

>> Yes please. This isn't performance critical. Folding will make the interface
>> better match other hypercalls.
> 
> The main thing that I am concerned about is, that in the
> case that dom0 panics, and we are asking the hypercall to take a dump
> for us, do we really want a copy_from guest in that path?
> It seems to me that its best to have that path as simple as possible.
> But I do argree that it comes at the expense of making the interface
> a bit unclean.

We need to assume that kernel address space hasn't been too badly
compromised, or we couldn't execute as far as making the hypercall. A failed
copy_from_guest() in the crash hypercall could simply cause you to use the
guest_cpu_user_regs() instead. So you still crash, but the crash site is now
the hypercall call site.

 -- Keir



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