From: Michael Kapp <tquarkk@isis-it.de>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-dev <xen-devel@lists.xensource.com>,
Frank Mundinger <f.mundinger@gmx.net>
Subject: Re: xen kernel 2.6.18 bug with a d-link DFE 580TX - pci hide
Date: Sun, 26 Oct 2008 11:48:23 +0100 [thread overview]
Message-ID: <49044AF7.9030309@isis-it.de> (raw)
In-Reply-To: <C529E5B3.1E8D5%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 26/10/08 08:58, "Michael Kapp" <tquarkk@isis-it.de> wrote:
>
>>> Add swiotlb=force to your domain's kernel command line.
>> I set swiotlb=force in the domU conf, that doesn't fix it - also with
>> noirqdebug.
>
> That should be impossible since the line you are bugging on will not be
> executed if the swiotlb has been successfully enabled. Do you get a line in
> dmesg stating "Software IO TLB enabled"? If not then is CONFIG_SWIOTLB
> enabled in your kernel config (should happen by default). The file
> lib/swiotlb-xen.c should be getting built and you'll see there is code near
> the top of that file to parse swiotlb=force which sets swiotlb_force and
> should cause swiotlb_init() to do the right thing (which should get called
> via the path mem_init->pci_iommu_alloc->pci_swiotlb_init->swiotlb_init.
yeah - your right! My domU config was wrong, with swiotlb=force it's
working, thanks!
Can you tell me what this parameter is doing in detail, or where i can
find docs about it?
Regards,
Michael
next prev parent reply other threads:[~2008-10-26 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 20:05 xen kernel 2.6.18 bug with a d-link DFE 580TX - pci hide Michael Kapp
2008-10-25 23:16 ` Keir Fraser
2008-10-26 8:40 ` Michael Kapp
2008-10-26 8:35 ` Keir Fraser
2008-10-26 8:58 ` Michael Kapp
2008-10-26 9:15 ` Keir Fraser
2008-10-26 10:48 ` Michael Kapp [this message]
2008-10-26 16:55 ` Keir Fraser
2008-10-26 19:17 ` Michael Kapp
2008-10-26 21:02 ` Keir Fraser
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=49044AF7.9030309@isis-it.de \
--to=tquarkk@isis-it.de \
--cc=f.mundinger@gmx.net \
--cc=keir.fraser@eu.citrix.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 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.