From: Keir Fraser <keir@xensource.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: xen-devel@lists.xensource.com
Subject: Re: Permissive devices in Xen
Date: Sun, 08 Jul 2007 11:10:12 +0100 [thread overview]
Message-ID: <C2B67694.A7EB%keir@xensource.com> (raw)
In-Reply-To: <20070708100044.GX3885@ics.muni.cz>
On 8/7/07 11:00, "Lukas Hejtmanek" <xhejtman@ics.muni.cz> wrote:
>> domU is not trusted to manage the i/o address space. We assume dom0 has set
>> up the values sanely and domU should have no reason to change them.
>
> OK, I see. But there is problem with, e.g., InfiniBand card that during
> initialization performs reset of the card. The reset destroys the PCI config
> space therefore the driver reads 16 dwords from the config space and after
> reset, it writes them back. In DomU, it obviously does not restore address
> bars and the device fails to respond via MMIO.
>
> So, I've tried to allow DomU (via pciback driver) to write also the address
> bars but in this case, I'm facing to huge SLAB corruptions. In Dom0 or non-Xen
> kernel, it works pretty well.
>
> Do you have any hints how to track it down?
This was tracked down by Alex Williamson some time ago. There is code in
drivers/xen/pciback/conf_space_capability_pm.c:pm_ctrl_write() to restore
bars after a D3->D0 transition. I guess either your kernel does not have
that fix, or the fix needs to be extended slightly to cover whatever case
you are seeing.
-- Keir
next prev parent reply other threads:[~2007-07-08 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 1:05 Permissive devices in Xen Lukas Hejtmanek
2007-07-08 9:55 ` Keir Fraser
2007-07-08 10:00 ` Lukas Hejtmanek
2007-07-08 10:10 ` Keir Fraser [this message]
2007-07-09 23:14 ` Lukas Hejtmanek
2007-07-10 8:31 ` Keir Fraser
2007-07-10 8:57 ` Lukas Hejtmanek
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=C2B67694.A7EB%keir@xensource.com \
--to=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xhejtman@ics.muni.cz \
/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.