xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: xen crash related to pci passthrough
Date: Thu, 27 May 2010 14:02:20 -0700	[thread overview]
Message-ID: <4BFEDDDC.3060904@goop.org> (raw)
In-Reply-To: <C8248E7F.2103%keir.fraser@eu.citrix.com>

On 05/27/2010 01:02 PM, Keir Fraser wrote:
> On 27/05/2010 20:51, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
>
>   
>>    3. attach device to PV domU
>>       dom0# xl pci-attach f13pv64 0000:03:00.0
>>    4. unbind from pciback
>>       dom0# echo 0000:03:00.0 > /sys/bus/pci/drivers/pciback/unbind
>>    5. rmmod driver in domU
>>       domU# rmmod e1000e
>>    6. Crash!
>>
>> The device in question is an Intel 82574L ethernet controller, using
>> msi-x interrupts.
>>     
> What happens if you pci-detach before unbinding from pciback? Not that Xen
> should crash of course, but a crash resulting from a mistake in detach
> ordring in dom0 would be less worrying than some alternatives.
>   

Doing things in a more sensible order (rmmod in domU, detach, unbind)
seems to work OK.  I was deliberately seeing what would happen if I
tried pulling the device out from under a domain.

    J

  reply	other threads:[~2010-05-27 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 19:51 xen crash related to pci passthrough Jeremy Fitzhardinge
2010-05-27 20:02 ` Keir Fraser
2010-05-27 21:02   ` Jeremy Fitzhardinge [this message]
2010-05-28  9:28     ` Alex Zeffertt
2010-05-28  9:52       ` 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=4BFEDDDC.3060904@goop.org \
    --to=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --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).