All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: David Henningsson <david.henningsson@canonical.com>,
	Stephen Warren <swarren@nvidia.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Russ Anderson <rja@sgi.com>
Subject: Re: [PATCH]: x86_64, audio: Fix system panic when DMA > 40 bits
Date: Thu, 02 May 2013 11:59:28 -0700	[thread overview]
Message-ID: <5182B790.6090907@sgi.com> (raw)
In-Reply-To: <5182AE68.9010905@wwwdotorg.org>



On 5/2/2013 11:20 AM, Stephen Warren wrote:
> On 05/02/2013 12:20 AM, David Henningsson wrote:
>> On 05/01/2013 09:04 PM, Mike Travis wrote:
>>> The audio driver mistakenly allows 64 bit addresses to be created for
>>> the audio driver on Nvidia GPUs.  Unfortunately, the hardware normally
>>> only supports up to 40 bits of DMA.  This can cause system panics as
>>> well as misdirected data when the address is > 40 bits as the upper
>>> part the address is truncated.
>>
>> Thanks for this patch. Stephen Warren, is this something you can
>> confirm/deny, and do you know what range of hardware this actually
>> applies to?
> 
> It's certainly plausible that the GPU's internal physical addresses are
> less than a full 64-bits, and this probably affects PCI accesses too.
> 

I haven't noticed any other problems with MMIOH accesses.  The
problem of DMA32 addresses certainly affects us though audio is
not a high priority on UV(*) except in specific applications (like
Media Servers, etc.]  Accesses to the GPU and GPGPU are much more
common.

(* http://www.sgi.com/products/servers/uv/)

      reply	other threads:[~2013-05-02 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 19:04 [PATCH]: x86_64, audio: Fix system panic when DMA > 40 bits Mike Travis
2013-05-02  6:20 ` David Henningsson
2013-05-02  6:36   ` Mike Travis
2013-05-02  8:29     ` David Henningsson
2013-05-02 16:19       ` Mike Travis
2013-05-03  9:55     ` Takashi Iwai
2013-05-02 18:20   ` Stephen Warren
2013-05-02 18:59     ` Mike Travis [this message]

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=5182B790.6090907@sgi.com \
    --to=travis@sgi.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rja@sgi.com \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.org \
    --cc=tiwai@suse.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.