From: Gordan Bobic <gordan@bobich.net>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Device Reset on Nvidia GPUs
Date: Fri, 15 Nov 2013 14:29:39 +0000 [thread overview]
Message-ID: <b12b338169a67117dca97166e2466d14@mail.shatteredsilicon.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1311151426080.4714@kaball.uk.xensource.com>
On Fri, 15 Nov 2013 14:27:21 +0000, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Fri, 15 Nov 2013, Gordan Bobic wrote:
>> I've noticed that nouveau driver has a sysfs reset implemented
>> (although I'm not sure whether it is just a stub or whether it
>> does anything).
>>
>> Now, I fully understand that this is not actually necessary,
>> based purely on empirical evidence:
>>
>> My ATI cards reliably crash the host when the domU the are passed
>> to is rebooted, and the xen-pciback driver does have the sysfs
>> reset implemented for ATI cards.
>>
>> OTOH, my (modified) Nvidia cards handle domU reboots perfectly
>> and the xen-pciback driver has no sysfs reset implementation
>> for those.
>>
>> So I'm kind of torn between:
>> 1) It's not broken so don't even think about trying to fix it.
>> 2) Since FOSS reset implementation seems to exist, it might be
>> handy to port it into the xen-pciback feature list (caveat:
>> this may impact 1), which would be embarrasing).
>>
>> Thoughts?
>
> libxl is capable of using the sysfs reset node, so there shouldn't be
> any needed for porting the reset code to pciback
Not quite - when the device is owned by xen-pciback, there is
no reset node. When it is owned by nouveau, the reset node in
sysfs is there.
Gordan
next prev parent reply other threads:[~2013-11-15 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 12:18 Device Reset on Nvidia GPUs Gordan Bobic
2013-11-15 14:27 ` Stefano Stabellini
2013-11-15 14:29 ` Gordan Bobic [this message]
2013-11-15 14:40 ` Konrad Rzeszutek Wilk
2013-11-15 14:52 ` Gordan Bobic
2013-11-25 15:17 ` Konrad Rzeszutek Wilk
2013-11-25 15:25 ` Gordan Bobic
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=b12b338169a67117dca97166e2466d14@mail.shatteredsilicon.net \
--to=gordan@bobich.net \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).