From: "H. Peter Anvin" <hpa@zytor.com>
To: Neil Horman <nhorman@redhat.com>
Cc: Simon Horman <horms@verge.net.au>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: In place kexec
Date: Thu, 29 Jul 2010 10:51:33 -0700 [thread overview]
Message-ID: <4C51BFA5.60507@zytor.com> (raw)
In-Reply-To: <20100729150640.GF31490@shamino.rdu.redhat.com>
On 07/29/2010 08:06 AM, Neil Horman wrote:
>>
>> Sorry, can we keep the discussions of kexec-on-crash and kexec-in-place
>> clearly separated, please? The qla driver issue is supposed to be
>> kexec-in-place, and it sounds like you're talking about kexec-on-crash.
>>
> No, I'm just indicating a difference between the two paths, and I'm doing so
> because we used to have simmilar dma problems in the crash path, which we
> resolved by not turning of the iommu during shutdown, which is different from
> the in-place path. Just trying to give you some thoughts about where to look
Fair enough... just wanted to flag this as a problem, because it has
already been the source of a lot of confusion.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-07-29 17:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 21:57 In place kexec H. Peter Anvin
2010-07-28 22:02 ` Eric W. Biederman
2010-07-29 13:43 ` Neil Horman
2010-07-29 15:03 ` H. Peter Anvin
2010-07-29 15:06 ` Neil Horman
2010-07-29 17:51 ` H. Peter Anvin [this message]
2010-07-29 18:06 ` Eric W. Biederman
2010-07-29 18:29 ` H. Peter Anvin
2010-07-29 19:16 ` Vivek Goyal
2010-07-29 19:51 ` Eric W. Biederman
2010-07-29 19:55 ` Randy Dunlap
2010-07-30 3:38 ` H. Peter Anvin
2010-07-30 4:41 ` Eric W. Biederman
2010-07-30 5:04 ` H. Peter Anvin
2010-07-30 16:30 ` Eric W. Biederman
2010-07-30 16:41 ` H. Peter Anvin
2010-07-30 18:36 ` Eric W. Biederman
2010-07-30 22:52 ` Andrew Vasquez
2010-07-30 23:25 ` H. Peter Anvin
2010-07-30 23:40 ` Eric W. Biederman
2010-07-30 16:53 ` David Woodhouse
2010-07-30 18:21 ` Eric W. Biederman
2010-07-30 18:34 ` Vivek Goyal
2010-07-30 18:50 ` David Woodhouse
2010-07-30 18:56 ` Vivek Goyal
2010-07-30 19:17 ` David Woodhouse
2010-07-30 19:39 ` Eric W. Biederman
2010-07-30 19:46 ` David Woodhouse
2010-07-30 20:08 ` Eric W. Biederman
2010-07-30 20:15 ` David Woodhouse
2010-07-30 21:11 ` H. Peter Anvin
2010-07-30 20:42 ` H. Peter Anvin
2010-07-30 21:18 ` Khalid Aziz
2010-07-30 21:44 ` Khalid Aziz
[not found] ` <20120425211512.GA8583@ldl.usa.hp.com>
2012-04-25 22:06 ` Vivek Goyal
2010-07-29 20:06 ` H. Peter Anvin
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=4C51BFA5.60507@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.