| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH 00/04] Kexec / Kdump: Release 20061023 (xen-unsta
|
To: |
Magnus Damm <magnus@xxxxxxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [PATCH 00/04] Kexec / Kdump: Release 20061023 (xen-unstable-11856) |
|
From: |
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> |
|
Date: |
Wed, 25 Oct 2006 11:10:56 +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>, Horms <horms@xxxxxxxxxxxx> |
|
Delivery-date: |
Wed, 25 Oct 2006 03:11:44 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20061023090515.26706.69407.sendpatchset@localhost> |
|
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: |
Acb4HdxGGv9UgmQREdupGgAX8io7RQ== |
|
Thread-topic: |
[PATCH 00/04] Kexec / Kdump: Release 20061023 (xen-unstable-11856) |
|
User-agent: |
Microsoft-Entourage/11.2.5.060620 |
On 23/10/06 10:05, "Magnus Damm" <magnus@xxxxxxxxxxxxx> wrote:
> 20060931 - Take XIV for xen-unstable-11296 posted by Simon Horman
>
> Enjoy!
A couple of comments on this patchset:
Firstly, the new public header file is nicely laid out and commented but
it'd be nice to add some comments to the KEXEC_TYPE_* definitions explaining
what they mean. Also the same for xen_kexec_image_t (what do
indirection_page and start_address mean?). As far as possible it would be
good to have an explanation of the Xen kexec interface that stands alone and
allows independent implementation to that interface (e.g., in Solaris) with
as little need to crib from other kexec implementations as possible. So, for
example, adding a short 'story board' comment explaining the sequence of
hypercalls that would be used to set up and execute a kdump or kexec would
be useful. It would be very hard to add *too many* helpful comments. :-)
Secondly, you appear to stuff over 1000 lines of code into the patches/
directory. What is that all about? Will it go away when we move to a more
recent Linux kernel (which would be an argument to hold off on merging until
we have done that)?
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home