mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Muli Ben-Yehuda <muli@il.ibm.com>,
	Yinghai Lu <Yinghai.Lu@sun.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vivek Goyal <vgoyal@in.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86-64: disable the GART before allocate aperture
Date: Fri, 22 Jun 2007 15:41:24 -0600	[thread overview]
Message-ID: <m14pkzbraz.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200706222328.21259.ak@suse.de> (Andi Kleen's message of "Fri, 22 Jun 2007 23:28:20 +0200")

Andi Kleen <ak@suse.de> writes:

> On Friday 22 June 2007 22:33, Alan Cox wrote:
>> You've got mapped live gart pages from the previous kernel. Even if you
>> disable the gart before a memset 
>
> It's probably too late then. It could also interfere with other operations.
> If anything the GART should be disabled during kexec shutdown. Perhaps we just 
> need a suitable suspend function that does that. Eric, any preferences? 

Well it would be a shutdown method not a suspend method.  The authors of
the suspend code thought sharing code with the reboot and the rmmod case
didn't make sense.

For a normal kexec into another kernel I think this makes sense.

>> you may well have the video card using 
>> gart translations and possibly live IOMMU mappings for devices using it
>> via bus mastering - and those will cause you MCE exceptions with a
>> corrupt cpu context flag (ie not nicely recoverable).
>
> We disable those machine checks on K8 because they're not fully reliable.

For the kexec on panic not shutting the hardware down if at all possible is
the ideal.  There I think we need a mode to not touch a chunk of the iommu
and reserve it for the kexec on panic kernel (or perhaps just use the
swiotlb code if we need bounce buffers at all).

Eric

  parent reply	other threads:[~2007-06-22 21:42 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 19:19 Yinghai Lu
2007-06-22 19:31 ` Muli Ben-Yehuda
2007-06-22 19:38   ` Yinghai Lu
2007-06-22 19:49   ` Yinghai Lu
2007-06-22 20:33   ` Alan Cox
2007-06-22 21:28     ` Andi Kleen
2007-06-22 21:38       ` Yinghai Lu
2007-06-22 21:41       ` Eric W. Biederman [this message]
2007-06-22 21:32     ` Eric W. Biederman
2007-06-22 21:45       ` Muli Ben-Yehuda
2007-06-22 21:59       ` Yinghai Lu
2007-06-22 22:19       ` Alan Cox
2007-06-22 22:32         ` Eric W. Biederman
2007-06-22 22:43           ` Yinghai Lu
2007-06-22 22:54             ` Alan Cox
2007-06-22 22:57               ` Yinghai Lu
2007-06-22 23:04                 ` Alan Cox
2007-06-22 23:14                   ` Eric W. Biederman
2007-06-23  0:14         ` Andi Kleen
2007-06-23  0:27           ` Yinghai Lu
2007-06-23  0:35             ` Muli Ben-Yehuda
2007-06-23  0:38             ` Andi Kleen
2007-06-23  2:34             ` [PATCH] x86-64: disable the GART in shutdown Yinghai Lu
2007-06-23 10:39               ` Muli Ben-Yehuda
2007-06-23 10:59                 ` Andi Kleen
2007-06-23 11:09                   ` Muli Ben-Yehuda
2007-06-23 11:08               ` Andi Kleen
2007-06-25  0:18                 ` Yinghai Lu
2007-06-23 16:52               ` Andrew Morton
2007-06-25  0:22                 ` Yinghai Lu
2007-06-25  2:10                   ` Muli Ben-Yehuda
2007-06-25 19:34               ` [PATCH] x86-64: disable the GART in shutdown v2 Yinghai Lu
2007-06-25 19:41                 ` Muli Ben-Yehuda
2007-06-25 19:52                   ` Yinghai Lu
2007-06-25 19:56                     ` Muli Ben-Yehuda
2007-06-25 21:48                 ` [PATCH 1/2] x86-64: disable the GART in shutdown Yinghai Lu
2007-06-25 21:49                 ` [PATCH 2/2] x86_84: move iommu declaration from proto to iommu.h Yinghai Lu
2007-06-26 11:43                   ` Muli Ben-Yehuda
2007-06-23  9:08           ` [PATCH] x86-64: disable the GART before allocate aperture Alan Cox
2007-06-23 11:12           ` Vivek Goyal
2007-06-23 13:14             ` Andi Kleen

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=m14pkzbraz.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=Yinghai.Lu@sun.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=vgoyal@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome