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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 01/04] Kexec / Kdump: Generic code
From: Horms <horms@xxxxxxxxxxxx>
Date: Wed, 18 Oct 2006 17:13:03 +0900
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: Thu, 19 Oct 2006 09:26:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C15B9331.2B43%Keir.Fraser@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>
References: <20061018010003.GC11422@xxxxxxxxxxxx> <C15B9331.2B43%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: mutt-ng/devel-r804 (Debian)
On Wed, Oct 18, 2006 at 08:15:45AM +0100, Keir Fraser wrote:
> 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.

Indeed, that is true. I do think there is some value in avoiding
guest_cpu_user_regs(), but its theoretical at best. Magnus and I will
fold the arguments as you requested.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


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