From: Ronny.Hegewald@online.de
To: konrad.wilk@oracle.com
Cc: xen-devel@lists.xensource.com
Subject: Re: pvops dom0: no sound after boot; possibly causedby swiotlb
Date: Thu, 04 Feb 2010 01:55:40 +0100 [thread overview]
Message-ID: <17472149.3960821265244940127.JavaMail.servlet@kundenserver> (raw)
> I am curious - if you dom0 is 64-bit, does the sound card work?
Yes with 64-bit pvops-dom0 the sound works fine without any patches.
>>
>> Ooooh. I completly failed to notice that your dom0 was 32-bit.
>>
>> But having that there would make the mask always be below
>> 4GB, irregardless if the dom0 is 32 or 64-bit. Which is
>> exactly what it does on bare-metal.
><sigh> That is actually incorrect. Looking at the
>dma_alloc_coherent_mask I missed the '!' and thought it would set it
>irregardless of what the previous value was. That is not the case.
No, your first statement was correct. It would always return the same mask for 32-bit and 64-bit, because of the 32-bitness of the return-variable 'dma_mask'.
So the following patch maybe would be more appropriate?
--- arch/x86/xen/pci-swiotlb.c-org 2010-02-01 23:04:42.000000000 +0100
+++ arch/x86/xen/pci-swiotlb.c 2010-02-04 02:47:17.000000000 +0100
@@ -602,7 +602,11 @@ xen_swiotlb_alloc_coherent(struct device
ret = (void *)vstart;
if (hwdev != NULL && hwdev->coherent_dma_mask)
+#ifdef CONFIG_X86_32
+ mask = dma_alloc_coherent_mask(hwdev, flags);
+#else
mask = hwdev->coherent_dma_mask;
+#endif
else
mask = DMA_BIT_MASK(32);
next reply other threads:[~2010-02-04 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 0:55 Ronny.Hegewald [this message]
2010-02-05 16:24 ` pvops dom0: no sound after boot; possibly causedby swiotlb Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2010-02-01 20:54 Ronny.Hegewald
2010-02-01 21:52 ` Konrad Rzeszutek Wilk
2010-01-26 19:27 Ronny.Hegewald
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=17472149.3960821265244940127.JavaMail.servlet@kundenserver \
--to=ronny.hegewald@online.de \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).