From: "Michel Dänzer" <michel@daenzer.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] radeon: Use mdelay() instead of msleep() in atom_op_delay().
Date: Wed, 04 Jan 2012 11:34:45 +0100 [thread overview]
Message-ID: <1325673285.1807.492.camel@thor.local> (raw)
In-Reply-To: <20120104005226.03580b70@pyramind.ukuu.org.uk>
On Mit, 2012-01-04 at 00:52 +0000, Alan Cox wrote:
> On Tue, 03 Jan 2012 19:25:46 +0100
> Michel Dänzer <michel@daenzer.net> wrote:
> > On Die, 2012-01-03 at 18:09 +0000, Alan Cox wrote:
> > > On Tue, 3 Jan 2012 19:04:00 +0100
> > > Michel Dänzer <michel@daenzer.net> wrote:
> > >
> > > > From: Michel Dänzer <michel.daenzer@amd.com>
> > > >
> > > > It can be called from atomic context, e.g. when switching to console for panic
> > > > output.
> > >
> > > Is this only special cases like a panic - if so can it not be called in a
> > > way that distinguishes between normality and nasty cases.
> >
> > No idea, to be honest. It's an ATOM BIOS interpreter opcode, so in
> > theory it could be indirectly called from anywhere that uses ATOM BIOS.
>
> So lets stick to practice, and the real world. Screwing up everything
> else because of a crappy problem in your Atom BIOS code sucks but hey it
> happens. screwing up everything because of a theoretical concern is just
> dumb.
Thanks for the flowers, but it's not just a theoretical concern, see the
bug report.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-01-04 10:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:04 [PATCH] radeon: Use mdelay() instead of msleep() in atom_op_delay() Michel Dänzer
2012-01-03 18:09 ` Dave Airlie
2012-01-03 18:16 ` Michel Dänzer
2012-01-03 20:04 ` Daniel Vetter
2012-01-04 10:34 ` Michel Dänzer
2012-01-03 18:09 ` Alan Cox
2012-01-03 18:25 ` Michel Dänzer
2012-01-04 0:52 ` Alan Cox
2012-01-04 10:34 ` Michel Dänzer [this message]
2012-01-04 11:25 ` Alan Cox
2012-01-04 12:03 ` Dave Airlie
2012-01-04 12:20 ` Alan Cox
2012-01-04 10:33 ` [PATCH v2] radeon: Use mdelay() instead of msleep() when we can't sleep " Michel Dänzer
2012-01-04 10:54 ` Daniel Vetter
2012-01-04 11:29 ` Michel Dänzer
2012-01-04 11:44 ` Daniel Vetter
2012-01-04 11:50 ` Michel Dänzer
2012-01-04 12:09 ` Alan Cox
2012-01-04 12:49 ` Daniel Vetter
2012-01-04 13:28 ` Alan Cox
2012-01-04 13:42 ` Daniel Vetter
2012-01-04 13:47 ` Alan Cox
2012-01-04 12:58 ` Daniel Vetter
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=1325673285.1807.492.camel@thor.local \
--to=michel@daenzer.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.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