From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [BROKEN PATCH] kexec for ia64
Date: Mon, 26 Jul 2004 22:36:05 +0000 [thread overview]
Message-ID: <200407261536.05133.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200407261524.40804.jbarnes@engr.sgi.com>
On Monday, July 26, 2004 3:24 pm, Jesse Barnes wrote:
> o userspace tools need ia64 support
> o need to deal with in-flight DMA (see FIXME in machine_kexec)
After looking at it a little more, I suppose device_shutdown() should
theoretically deal with this.
Also, it would be nice if there were a Documentation/kexec.txt or something in
the full patch that describes all the pieces and what the arch dependent
functions are responsible for. Randy, do you have anything like that written
up somewhere that you could include in the next spin of the patch?
Thanks,
Jesse
next prev parent reply other threads:[~2004-07-26 22:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 22:24 [BROKEN PATCH] kexec for ia64 Jesse Barnes
2004-07-26 22:36 ` Jesse Barnes [this message]
2004-07-26 23:09 ` David Mosberger
2004-07-26 23:30 ` David Mosberger
2004-07-26 23:34 ` Jesse Barnes
2004-07-26 23:42 ` David Mosberger
2004-07-27 8:24 ` Christian Hildner
2004-07-27 14:49 ` Jesse Barnes
2004-07-27 16:50 ` Luck, Tony
2004-07-30 22:55 ` Randy.Dunlap
2004-08-04 13:07 ` Eric W. Biederman
2004-08-04 16:24 ` Jesse Barnes
2004-08-04 23:33 ` Grant Grundler
2004-08-05 2:14 ` [Fastboot] " Eric W. Biederman
2004-08-05 15:39 ` Grant Grundler
2004-08-05 16:44 ` Eric W. Biederman
2004-08-05 19:44 ` Tolentino, Matthew E
2004-08-05 21:29 ` Eric W. Biederman
2004-08-05 22:15 ` Eric W. Biederman
2004-08-05 16:45 ` Luck, Tony
2004-08-05 17:05 ` [Fastboot] " Eric W. Biederman
2004-08-05 19:18 ` Khalid Aziz
2004-08-05 18:28 ` Grant Grundler
2004-08-05 18:56 ` Eric W. Biederman
2004-08-05 21:24 ` Grant Grundler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200407261536.05133.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox