All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Wagner <f_wagner@syscomp.de>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen, IRQ-sharing and PCI passthrough
Date: Wed, 8 Jul 2009 08:35:13 +0200	[thread overview]
Message-ID: <20090708083513.774b8281@auedv3.syscomp.de> (raw)
In-Reply-To: <4A53162C02000078000091BE@vpn.id2.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1546 bytes --]

> Assuming your kernel has a call to irq_ignore_unhandled() out of
> note_interrupt(), [...]

Judging from my backtrace this seems to be the case, right?


> [...] there's nothing but using hardware's help (i.e. VT-d
> interrupt remapping) to get this addressed: The pv passthrough
> mechanism assumes that guests you assign physical devices to are well
> behaved, and your guest isn't (it fails to disable the interrupt at
> the device).

Do I understand this correctly: For safe operation of a virtual machine
using PCI passthrough and shared interrupts a well behaved operating
system in the vm is necessary. That is an OS that shuts down the mapped
devices correctly before turning off (unload kernel module).

So what am I to to in the case that someone issues a "xm destroy" on
such a vm? There is no way to cleanly shutdown in such a situation, is
there?

That's quite a risk for system stability of the host. One thoughtless
"xm destroy" and the whole host is crashed, requiring at a minimum a
cold reset or even a reinstall.


Regards
Florian

--------------

Florian Wagner
Abteilung EDV
Telefon: 0821 / 4201 - 453
Fax: 0821 / 4201 - 411
E-Mail: f_wagner@syscomp.de

Syscomp Biochemische Dienstleistungen GmbH
August-Wessels-Straße 5, 86154 Augsburg
Postfach 102506, 86015 Augsburg
Telefon: 0821 / 4201 - 0
Fax: 0821 / 417992
Web: http://www.syscomp.de
E-Mail: syscomp@syscomp.de

Geschäftsführer:
  Dr. med. Bernd Schottdorf
  Gabriele Schottdorf

Registergericht Augsburg HRB 8670

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2009-07-08  6:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  6:19 Xen, IRQ-sharing and PCI passthrough Florian Wagner
2009-07-07  7:22 ` Keir Fraser
2009-07-07  7:32 ` Jan Beulich
2009-07-07  7:39   ` Keir Fraser
2009-07-08  6:35   ` Florian Wagner [this message]
2009-07-08  7:31     ` 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=20090708083513.774b8281@auedv3.syscomp.de \
    --to=f_wagner@syscomp.de \
    --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.