All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	dri-devel@lists.freedesktop.org,
	Markus Trippelsdorf <markus@trippelsdorf.de>
Subject: Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues
Date: Mon, 29 Jul 2013 11:10:31 -0700	[thread overview]
Message-ID: <87k3k9z17s.fsf@xmission.com> (raw)
In-Reply-To: <CADnq5_NpyjQ8+nC6arxM_dAjx2kDB76bGA9No0hkihjLvfbvCg@mail.gmail.com> (Alex Deucher's message of "Mon, 29 Jul 2013 14:02:26 -0400")

Alex Deucher <alexdeucher@gmail.com> writes:

> On Mon, Jul 29, 2013 at 11:50 AM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
>>
>>
>> Alex Deucher <alexdeucher@gmail.com> wrote:
>>>On Mon, Jul 29, 2013 at 10:09 AM, Markus Trippelsdorf
>>><markus@trippelsdorf.de> wrote:
>>>> On 2013.07.29 at 09:58 -0400, Alex Deucher wrote:
>>>>> On Mon, Jul 29, 2013 at 3:51 AM, Markus Trippelsdorf
>>>>> <markus@trippelsdorf.de> wrote:
>>>>> > On my test machine Xorg doesn't start anymore when I kexec into a
>>>>> > 3.11.0-rc3 kernel.
>>>>>
>>>>> With kexec, dpm doesn't get torn down properly which can result in a
>>>>> bad hardware state when the driver loads again.  Does the attached
>>>>> patch help?  It attempts to disable dpm at startup in case it wasn't
>>>>> torn down properly previously.
>>>>
>>>> dpm initialization now works, but unfortunately GPU acceleration
>>>still gets
>>>> disabled:
>>>
>>>Stupid kexec complicates things.  We need to make sure dpm is torn
>>>down before we init the rest of the GPU, but dpm needs get initialized
>>>later in the init process since it depends on certain other state from
>>>the driver.  I need to think about this for a bit.  I'm not sure of a
>>>good way to handle this.
>>
>> You might just want to implement a shutdown method that cleans things up properly.   At least as a first pass until you worry about things like kexec on panic.
>>
>> Or can you not shutdown the graphics stack on reboot because of the need to display the kernels shutdown progress?
>
> Does kexec actually call this shutdown method?  The driver implements
> appropriate clean-up measures if it's shutdown properly.

Absoltuely.  All parts of the reboot path call ->shutdown.  Including
kexec.

You don't get a device remove/hotunplug but unless this is a kexec on
panic ->shutdown is most definitely called.  Now I am talking about the
device layer/pci layer shutdown method I don't know how gpu drivers are
wired up.  GPU land was a little strange last I looked.  Hopefully it
isn't so strange that there is a method named shutdown that is not wired
up.

Eric

  reply	other threads:[~2013-07-29 18:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  7:51 Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues Markus Trippelsdorf
2013-07-29 13:58 ` Alex Deucher
2013-07-29 14:09   ` Markus Trippelsdorf
2013-07-29 14:18     ` Alex Deucher
2013-07-29 15:50       ` Eric W. Biederman
2013-07-29 18:02         ` Alex Deucher
2013-07-29 18:10           ` Eric W. Biederman [this message]
2013-07-29 19:53             ` Alex Deucher
2013-07-29 19:58               ` Markus Trippelsdorf
2013-07-30 11:27               ` Markus Trippelsdorf
2013-07-30 11:57                 ` Markus Trippelsdorf
2013-07-30 14:53                 ` Alex Deucher
2013-07-30 18:46                   ` Markus Trippelsdorf
2013-07-30 20:56                     ` Markus Trippelsdorf
2013-07-31  9:19                       ` Joshua C.
2013-07-29 16:14       ` Joshua C.
2013-07-29 16:35         ` Markus Trippelsdorf
2013-07-29 17:58         ` Alex Deucher

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=87k3k9z17s.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=markus@trippelsdorf.de \
    /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.